chore(docs): update unpublish docs with both commands, removing policy info from cli docs, and added reference to unpublish policy docs

docs/content/cli-commands/npm-unpublish.md

@@ -10,19 +10,21 @@ description: Remove a package from the registry
 
 ### Synopsis
 
+#### Unpublishing a single version of a package
+
 ```bash
-npm unpublish [<@scope>/]<pkg>[@<version>]
+npm unpublish <package-name>@<version>
 ```
 
-### Warning
+#### Unpublishing an entire package
 
-**It is generally considered bad behavior to remove versions of a library
-that others are depending on!**
+```bash
+npm unpublish <package-name> -f
+```
 
-Consider using the `deprecate` command
-instead, if your intent is to encourage users to upgrade.
+### Warning
 
-There is plenty of room on the registry.
+Consider using the `deprecate` command instead, if your intent is to encourage users to upgrade, or if you no longer want to maintain a package.
 
 ### Description
 
@@ -34,16 +36,10 @@ the root package entry is removed from the registry entirely.
 
 Even if a package version is unpublished, that specific name and
 version combination can never be reused. In order to publish the
-package again, a new version number must be used. Additionally,
-new versions of packages with every version unpublished may not
-be republished until 24 hours have passed.
+package again, a new version number must be used. If you unpublish the entire package, you may not publish any new versions of that package until 24 hours have passed.
 
-With the default registry (`registry.npmjs.org`), unpublish is
-only allowed with versions published in the last 72 hours. If you
-are trying to unpublish a version published longer ago than that,
-contact [email protected].
+To learn more about how unpublish is treated on the npm registry, see our <a href="https://www.npmjs.com/policies/unpublish" target="_blank" rel="noopener noreferrer"> unpublish policies</a>. 
 
-The scope is optional and follows the usual rules for [`scope`](/using-npm/scope).
 
 ### See Also