doc: s/npm-json(1)/package.json(5)/g

14 files changed, 16 insertions, 16 deletions

diff --git a/doc/api/npm-init.md b/doc/api/npm-init.md
index 5afc11b3b..9b75bf791 100644
--- a/doc/api/npm-init.md
+++ b/doc/api/npm-init.md
@@ -26,4 +26,4 @@ then go ahead and use this programmatically.
 
 ## SEE ALSO
 
-npm-json(1)
+package.json(5)
diff --git a/doc/cli/npm-bugs.md b/doc/cli/npm-bugs.md
index 45ee84b58..d5b8e7f75 100644
--- a/doc/cli/npm-bugs.md
+++ b/doc/cli/npm-bugs.md
@@ -35,4 +35,4 @@ The base URL of the npm package registry.
 * npm-publish(1)
 * npm-registry(1)
 * npm-config(1)
-* npm-json(1)
+* package.json(5)
diff --git a/doc/cli/npm-build.md b/doc/cli/npm-build.md
index 978f4a6d6..ee183c199 100644
--- a/doc/cli/npm-build.md
+++ b/doc/cli/npm-build.md
@@ -19,4 +19,4 @@ It should generally not be called directly.
 * npm-install(1)
 * npm-link(1)
 * npm-scripts(1)
-* npm-json(1)
+* package.json(5)
diff --git a/doc/cli/npm-docs.md b/doc/cli/npm-docs.md
index 28fa49193..634ed4030 100644
--- a/doc/cli/npm-docs.md
+++ b/doc/cli/npm-docs.md
@@ -35,4 +35,4 @@ The base URL of the npm package registry.
 * npm-publish(1)
 * npm-registry(1)
 * npm-config(1)
-* npm-json(1)
+* package.json(5)
diff --git a/doc/cli/npm-help.md b/doc/cli/npm-help.md
index b51b0f164..1ab88ad39 100644
--- a/doc/cli/npm-help.md
+++ b/doc/cli/npm-help.md
@@ -33,6 +33,6 @@ Set to `"browser"` to view html help content in the default web browser.
 * npm-faq(1)
 * npm-folders(1)
 * npm-config(1)
-* npm-json(1)
+* package.json(5)
 * npm-help-search(1)
 * npm-index(1)
diff --git a/doc/cli/npm-init.md b/doc/cli/npm-init.md
index d036f924d..bd63a8879 100644
--- a/doc/cli/npm-init.md
+++ b/doc/cli/npm-init.md
@@ -21,5 +21,5 @@ without a really good reason to do so.
 ## SEE ALSO
 
 * <https://github.com/isaacs/init-package-json>
-* npm-json(1)
+* package.json(5)
 * npm-version(1)
diff --git a/doc/cli/npm-install.md b/doc/cli/npm-install.md
index 44885f318..fc8ab31e3 100644
--- a/doc/cli/npm-install.md
+++ b/doc/cli/npm-install.md
@@ -121,7 +121,7 @@ after packing it up into a tarball (b).
 * `npm install <name>@<version range>`:
 
     Install a version of the package matching the specified version range.  This
-    will follow the same rules for resolving dependencies described in `npm-json(1)`.
+    will follow the same rules for resolving dependencies described in `package.json(5)`.
 
     Note that most version ranges must be put in quotes so that your shell will
     treat it as a single argument.
diff --git a/doc/cli/npm-link.md b/doc/cli/npm-link.md
index 4e4ef799b..d113726d5 100644
--- a/doc/cli/npm-link.md
+++ b/doc/cli/npm-link.md
@@ -54,7 +54,7 @@ installation target into your project's `node_modules` folder.
 
 * npm-developers(1)
 * npm-faq(1)
-* npm-json(1)
+* package.json(5)
 * npm-install(1)
 * npm-folders(1)
 * npm-config(1)
diff --git a/doc/cli/npm-shrinkwrap.md b/doc/cli/npm-shrinkwrap.md
index f0b83d50d..0ecf64466 100644
--- a/doc/cli/npm-shrinkwrap.md
+++ b/doc/cli/npm-shrinkwrap.md
@@ -181,5 +181,5 @@ contents rather than versions.
 ## SEE ALSO
 
 * npm-install(1)
-* npm-json(1)
+* package.json(5)
 * npm-list(1)
diff --git a/doc/cli/npm-submodule.md b/doc/cli/npm-submodule.md
index 13ab1edd9..7f0fbfc9f 100644
--- a/doc/cli/npm-submodule.md
+++ b/doc/cli/npm-submodule.md
@@ -24,5 +24,5 @@ dependencies into the submodule folder.
 
 ## SEE ALSO
 
-* npm-json(1)
+* package.json(5)
 * git help submodule
diff --git a/doc/cli/npm-version.md b/doc/cli/npm-version.md
index 74d938d6b..a874ef3c4 100644
--- a/doc/cli/npm-version.md
+++ b/doc/cli/npm-version.md
@@ -41,5 +41,5 @@ in your git config for this to work properly.  For example:
 ## SEE ALSO
 
 * npm-init(1)
-* npm-json(1)
+* package.json(5)
 * npm-semver(1)
diff --git a/doc/cli/npm-view.md b/doc/cli/npm-view.md
index 07836a5ef..b88f0a521 100644
--- a/doc/cli/npm-view.md
+++ b/doc/cli/npm-view.md
@@ -55,7 +55,7 @@ can do this:
 
 "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 `npm-json(1)` for more on this.)
+the shortened string format.  (See `package.json(5)` for more on this.)
 
     npm view npm contributors
 
diff --git a/doc/cli/npm.md b/doc/cli/npm.md
index a325fdf2e..b5b4758c2 100644
--- a/doc/cli/npm.md
+++ b/doc/cli/npm.md
@@ -33,7 +33,7 @@ Use `npm ls` to show everything you've installed.
 
 ## DIRECTORIES
 
-See `npm-folders(1)` to learn about where npm puts stuff.
+See `npm-folders(7)` to learn about where npm puts stuff.
 
 In particular, npm has two modes of operation:
 
@@ -54,7 +54,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 `npm-json(1)`.
+  Make a package.json file.  See `package.json(5)`.
 * 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
@@ -148,7 +148,7 @@ See npm-changelog(1)
 * npm-help(1)
 * npm-faq(1)
 * README
-* npm-json(1)
+* package.json(5)
 * npm-install(1)
 * npm-config(1)
 * npm-index(1)
diff --git a/doc/misc/npm-registry.md b/doc/misc/npm-registry.md
index 484b07945..e389bdac6 100644
--- a/doc/misc/npm-registry.md
+++ b/doc/misc/npm-registry.md
@@ -42,7 +42,7 @@ published at all, or
 `"publishConfig":{"registry":"http://my-internal-registry.local"}`
 to force it to be published only to your internal registry.
 
-See `npm-json(1)` for more info on what goes in the package.json file.
+See `package.json(5)` for more info on what goes in the package.json file.
 
 ## Will you replicate from my registry into the public one?