Update Unpublish Requirement Link

npm · Sep 5, 2023 · 2f71750 · 2f71750
1 parent 8816df0
commit 2f71750
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/...nd-managing-your-published-packages/unpublishing-packages-from-the-registry.mdx b/...nd-managing-your-published-packages/unpublishing-packages-from-the-registry.mdx
@@ -17,7 +17,7 @@ These criteria are set to avoid damaging the JavaScript package ecosystem.  If y
 
 If you want to completely remove all versions of a package from the registry, you can unpublish it completely.  This will delete it from the registry and it will be unable to be installed.
 
-To unpublish a package, you must meet the requirements of the [package unpublishing rules](#how-to-unpublish).
+To unpublish a package, you must meet the requirements of the [package unpublishing rules][unpublish].
 
 ### Using the website
 
@@ -43,7 +43,7 @@ To unpublish a package, you must meet the requirements of the [package unpublish
 
     <Note>
 
-    **Note:** If you cannot delete the package because it does not meet the [unpublishing requirements](#how-to-unpublish), then the delete package option will not be available.  Instead, you will be prompted to [deprecate the package](/deprecating-and-undeprecating-packages-or-package-versions#deprecating-a-package-from-the-website).
+    **Note:** If you cannot delete the package because it does not meet the [unpublishing requirements][unpublish], then the delete package option will not be available.  Instead, you will be prompted to [deprecate the package](/deprecating-and-undeprecating-packages-or-package-versions#deprecating-a-package-from-the-website).
 
     </Note>