diff --git a/docs/content/commands/npm-link.md b/docs/content/commands/npm-link.md
index a32ee08fe0c17..7c55f18c5a431 100644
--- a/docs/content/commands/npm-link.md
+++ b/docs/content/commands/npm-link.md
@@ -29,7 +29,7 @@ of the current folder.
 Note that `package-name` is taken from `package.json`,
 not from directory name.
 
-The package name can be optionally prefixed with a scope. See [`scope`](/using-npm/npm-scope).
+The package name can be optionally prefixed with a scope. See [`scope`](/using-npm/scope).
 The scope must be preceded by an @-symbol and followed by a slash.
 
 When creating tarballs for `npm publish`, the linked packages are
@@ -72,7 +72,7 @@ installation target into your project's `node_modules` folder.
 Note that in this case, you are referring to the directory name, `node-redis`,
 rather than the package name `redis`.
 
-If your linked package is scoped (see [`scope`](/using-npm/npm-scope)) your link command must include that scope, e.g.
+If your linked package is scoped (see [`scope`](/using-npm/scope)) your link command must include that scope, e.g.
 
 ```bash
 npm link @myorg/privatepackage
diff --git a/docs/content/commands/npm-logout.md b/docs/content/commands/npm-logout.md
index 69779e601f1a6..b1f344af576f3 100644
--- a/docs/content/commands/npm-logout.md
+++ b/docs/content/commands/npm-logout.md
@@ -36,7 +36,7 @@ it takes precedence.
 
 Default: The scope of your current project, if any, otherwise none.
 
-If specified, you will be logged out of the specified scope. See [`scope`](/using-npm/npm-scope).
+If specified, you will be logged out of the specified scope. See [`scope`](/using-npm/scope).
 
 ```bash
 npm logout --scope=@myco
diff --git a/docs/content/commands/npm-publish.md b/docs/content/commands/npm-publish.md
index 406a4a6c7da00..3dcdc6f3022ed 100644
--- a/docs/content/commands/npm-publish.md
+++ b/docs/content/commands/npm-publish.md
@@ -22,7 +22,7 @@ files in the package directory are included if no local `.gitignore` or
 [`developers`](/using-npm/developers) for full details on what's included in the published package, as well as details on how the package is built.
 
 By default npm will publish to the public registry. This can be overridden by
-specifying a different default registry or using a [`scope`](/using-npm/npm-scope) in the name (see [`package.json`](/configuring-npm/package-json)).
+specifying a different default registry or using a [`scope`](/using-npm/scope) in the name (see [`package.json`](/configuring-npm/package-json)).
 
 * `<folder>`:
   A folder containing a package.json file
@@ -70,9 +70,9 @@ included and packs them into a tarball to be uploaded to the registry.
 
 * [npm registry](/using-npm/registry)
 * [npm scope](/using-npm/scope)
-* [npm adduser](/commands/adduser)
-* [npm owner](/commands/owner)
-* [npm deprecate](/commands/deprecate)
-* [npm dist-tag](/commands/dist-tag)
-* [npm pack](/commands/pack)
-* [npm profile](/commands/profile)
+* [npm adduser](/commands/npm-adduser)
+* [npm owner](/commands/npm-owner)
+* [npm deprecate](/commands/npm-deprecate)
+* [npm dist-tag](/commands/npm-dist-tag)
+* [npm pack](/commands/npm-pack)
+* [npm profile](/commands/npm-profile)
diff --git a/docs/content/commands/npm-view.md b/docs/content/commands/npm-view.md
index 3404c0314335b..925196a4fe21b 100644
--- a/docs/content/commands/npm-view.md
+++ b/docs/content/commands/npm-view.md
@@ -76,7 +76,7 @@ npm view express contributors.name contributors.email
 
 "Person" fields are shown as a string if they would be shown as an
 object.  So, for example, this will show the list of npm contributors in
-the shortened string format.  (See [`package.json`](/configuring-npm/package.json) for more on this.)
+the shortened string format.  (See [`package.json`](/configuring-npm/package-json) for more on this.)
 
 ```bash
 npm view npm contributors
diff --git a/docs/content/commands/npm.md b/docs/content/commands/npm.md
index 10cc19f7dd2dd..923f4cec48f37 100644
--- a/docs/content/commands/npm.md
+++ b/docs/content/commands/npm.md
@@ -84,7 +84,7 @@ If you're using npm to develop and publish your code, check out the
 following help topics:
 
 * json:
-  Make a package.json file.  See [`package.json`](/configuring-npm/package.json).
+  Make a package.json file.  See [`package.json`](/configuring-npm/package-json).
 * link:
   For linking your current working code into Node's path, so that you
   don't have to reinstall every time you make a change.  Use
diff --git a/docs/content/configuring-npm/folders.md b/docs/content/configuring-npm/folders.md
index 3ec716f2c67fd..75e31cd733161 100644
--- a/docs/content/configuring-npm/folders.md
+++ b/docs/content/configuring-npm/folders.md
@@ -205,7 +205,7 @@ not be included in the package tarball.
 
 This allows a package maintainer to install all of their dependencies
 (and dev dependencies) locally, but only re-publish those items that
-cannot be found elsewhere.  See [`package.json`](/configuring-npm/package.json) for more information.
+cannot be found elsewhere.  See [`package.json`](/configuring-npm/package-json) for more information.
 
 ### See also