Apply suggestions from code review
Co-authored-by: Chris Fuentes <chris@chrisf.io>
Edward Thomson committed
Aug 18, 2021 at 14:48 UTC
e517d3c4428e6406600b65dc23ed25b3570a96ed
3 files changed
+6
-6
content/organizations/creating-and-managing-organizations/deleting-an-organization.mdx
+2
-2
@@ -8,7 +8,7 @@ import shared from '../../../src/shared.js'
8
An organization administrator can delete the organization; packages in
9
the organization will also [be deleted](/unpublishing-packages-from-the-registry) if they fulfill the
10
[requirements to unpublish packages](/policies/unpublish). Packages that
11
-cannot be deleted will be
11
+cannot be deleted can be
12
[deprecated](/deprecating-and-undeprecating-packages-or-package-versions)
13
instead.
14
@@ -30,7 +30,7 @@ instead.
30
5. Under "delete organization", click <strong>Delete</strong>.
31
<Screenshot src="/organizations/creating-and-managing-organizations/org-delete-button.png" alt="Screenshot of org delete button" />
32
33
-6. You will be given an overview of the packages in your organization and what will happen to them when your organization is deleted. Packages that [can be unpublished](/unpublishing-packages-from-the-registry) will be deleted; packages that cannot be deleted will be [deprecated](/deprecating-and-undeprecating-packages-or-package-versions).
33
+6. You will be given an overview of the packages in your organization and what will happen to them when your organization is deleted. Packages that [can be unpublished](/unpublishing-packages-from-the-registry) will be deleted.
34
35
If you are sure that you want to continue, enter your organization name and click <strong>Delete this organization</strong>.
36
content/packages-and-modules/updating-and-managing-your-published-packages/deprecating-and-undeprecating-packages-or-package-versions.mdx
+3
-3
@@ -16,12 +16,12 @@ A deprecation warning or message can say anything. You may wish to include a mes
16
## Deprecating an entire package
17
18
Deprecating an entire package will remove it from search results on the
19
-npm website, and a deprecation message will also be displayed on the
19
+npm website and a deprecation message will also be displayed on the
20
package page.
21
22
<Screenshot src="/packages-and-modules/updating-and-managing-your-published-packages/deprecate-package.png" alt="Screenshot of package deprecation" />
23
24
-Deprecating a package is an alternative to unpublishing a package if
24
+Deprecating a package is an alternative to deleting a package if
25
your package does not meet the
26
[unpublishing requirements](/policies/unpublish).
27
@@ -31,7 +31,7 @@ your package does not meet the
31
32
<>{shared["user-login"].image}</>
33
34
-2. Navigate to the package page for the package you want to unpublish, replacing `<your-package-name>` with the name of your package:
34
+2. Navigate to the package page for the package you want to deprecate, replacing `<your-package-name>` with the name of your package:
35
`https://www.npmjs.com/package/<your-package-name>`.
36
37
3. Click **Settings**.
content/packages-and-modules/updating-and-managing-your-published-packages/unpublishing-packages-from-the-registry.mdx
+1
-1
@@ -74,7 +74,7 @@ If you have [two-factor authentication][two-factor-auth] enabled for writes, you
74
75
## Unpublishing a single version of a package
76
77
-If you want to remove a single version of a package, you can unpublish one version without affecting the others. This will delete only that version from the registry and it will be unable to be installed.
77
+If you want to remove a single version of a package, you can unpublish one version without affecting the others. This will delete only that version from the registry and it will be unable to be installed. This option is only available via the npm CLI.
78
79
### Using the command line
80