Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/npm/cli.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--CONTRIBUTING.md2
-rw-r--r--docs/content/commands/npm-unpublish.md2
-rw-r--r--docs/content/commands/npm.md2
-rw-r--r--docs/content/using-npm/registry.md2
-rw-r--r--packages/libnpmdiff/README.md2
5 files changed, 5 insertions, 5 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 558ce2a83..ec1c51386 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -2,7 +2,7 @@
## Code of Conduct
-All interactions in the **npm** organization on GitHub are considered to be covered by our standard [Code of Conduct](https://www.npmjs.com/policies/conduct).
+All interactions in the **npm** organization on GitHub are considered to be covered by our standard [Code of Conduct](https://docs.npmjs.com/policies/conduct).
## Development
diff --git a/docs/content/commands/npm-unpublish.md b/docs/content/commands/npm-unpublish.md
index 82779ab65..b17ff4540 100644
--- a/docs/content/commands/npm-unpublish.md
+++ b/docs/content/commands/npm-unpublish.md
@@ -7,7 +7,7 @@ description: Remove a package from the registry
### Synopsis
To learn more about how the npm registry treats unpublish, see our <a
-href="https://www.npmjs.com/policies/unpublish" target="_blank"
+href="https://docs.npmjs.com/policies/unpublish" target="_blank"
rel="noopener noreferrer"> unpublish policies</a>
#### Unpublishing a single version of a package
diff --git a/docs/content/commands/npm.md b/docs/content/commands/npm.md
index 7ff1cc490..de5108706 100644
--- a/docs/content/commands/npm.md
+++ b/docs/content/commands/npm.md
@@ -31,7 +31,7 @@ Run `npm help` to get a list of available commands.
npm comes preconfigured to use npm's public registry at
https://registry.npmjs.org by default. Use of the npm public registry is
subject to terms of use available at
-https://www.npmjs.com/policies/terms.
+https://docs.npmjs.com/policies/terms.
You can configure npm to use any compatible registry you like, and even
run your own registry. Use of someone else's registry is governed by
diff --git a/docs/content/using-npm/registry.md b/docs/content/using-npm/registry.md
index c07fa7a48..3b07ab11c 100644
--- a/docs/content/using-npm/registry.md
+++ b/docs/content/using-npm/registry.md
@@ -12,7 +12,7 @@ package info.
npm is configured to use the **npm public registry** at
<https://registry.npmjs.org> by default. Use of the npm public registry is
-subject to terms of use available at <https://www.npmjs.com/policies/terms>.
+subject to terms of use available at <https://docs.npmjs.com/policies/terms>.
You can configure npm to use any compatible registry you like, and even run
your own registry. Use of someone else's registry may be governed by their
diff --git a/packages/libnpmdiff/README.md b/packages/libnpmdiff/README.md
index bc260ad15..6c60f714b 100644
--- a/packages/libnpmdiff/README.md
+++ b/packages/libnpmdiff/README.md
@@ -61,7 +61,7 @@ hesitate to jump in if you'd like to, or even ask us questions if something
isn't clear.
All participants and maintainers in this project are expected to follow the
-[npm Code of Conduct](https://www.npmjs.com/policies/conduct), and just
+[npm Code of Conduct](https://docs.npmjs.com/policies/conduct), and just
generally be excellent to each other.
Please refer to the [Changelog](CHANGELOG.md) for project history details, too.