move section

Author: Rami Bououni

docs/artifacts/npm/npmrc.md

@@ -230,7 +230,7 @@ The following steps guide you through setting up the project-level configuration
     ```
 
 > [!NOTE]
-> For Debian, Ubuntu, and other community or entreprise distributions such as Fedora or Redhat make sure you've installed the prerequisites from the [NodeSource distributions repository](https://github.com/nodesource/distributions).
+> For Debian, Ubuntu, and other community or enterprise distributions such as Fedora or Redhat make sure you've installed the prerequisites from the [NodeSource distributions repository](https://github.com/nodesource/distributions).
 
 ### Setup credentials
 
@@ -279,58 +279,10 @@ The following steps guide you through setting up the project-level configuration
 > [!TIP]
 > Using multiple registries in *.npmrc* files is supported with [scopes](..//npm/scopes.md) and [upstream sources](../concepts/upstream-sources.md).
 
-::: moniker range="azure-devops"   
-
-## Troubleshoot
-
-#### vsts-npm-auth is not recognized
-
-This error indicates that the npm modules folder hasn't been added to your path. Rerun the Node.js setup and make sure to select the `Add to PATH` option. Alternatively, you can add the npm modules folder to your path by modifying the PATH variable to `%APPDATA%\npm` in Command Prompt or `$env:APPDATA\npm` in PowerShell.
-
-:::image type="content" source="./media/node-setup.png" alt-text="A Screenshot showing how to set up node.js.":::  
-
-#### Unable to authenticate
-
-- Error: *code E401 npm ERR! Unable to authenticate*: -> Run the `vsts-npm-auth` command with **-F** flag to reauthenticate:
-
-    ```
-    vsts-npm-auth -config .npmrc -F
-    ```
-
-#### Reset vsts-npm-auth
-
-Follow these steps to reset your vsts-npm-auth credentials:
-
-1. Uninstall vsts-npm-auth:
-
-    ```
-    npm uninstall -g vsts-npm-auth
-    ```
-
-1. Clear your npm cache:
-
-    ```
-    npm cache clean --force
-    ```
-
-1. Delete your *.npmrc* file.
-
-1. Reinstall vsts-npm-auth:
-
-    ```
-    npm install -g vsts-npm-auth --registry https://registry.npmjs.com --always-auth false
-    ```
-
-#### Unable to publish
-
-If you encounter a 403 error, it may indicate a name conflict. In Azure Artifacts, packages are immutable, meaning that once you publish a package to your feed, its version number is permanently reserved. Even if you delete it, you can't publish a new package with the same version number. To address this issue, update the package version in your *package.json* file, and then try again.
-
-::: moniker-end
-
 ## Related content
 
-- [Publish npm packages (CLI)](./publish.md)
+- [Publish npm packages (CLI)](publish.md)
 
-- [Publish npm packages (YAML/Classic)](../../pipelines/artifacts/npm.md)
+- [Restore npm packages](restore-npm-packages.md)
 
-- [Use packages from npmjs.com](./upstream-sources.md)
+- [Publish npm packages with Azure Pipelines (YAML/Classic)](../../pipelines/artifacts/npm.md)