8 files changed, 35 insertions, 18 deletions
diff --git a/deps/npm/doc/cli/npm-hook.md b/deps/npm/doc/cli/npm-hook.md
index 34deecaf92..5192872425 100644
--- a/deps/npm/doc/cli/npm-hook.md
+++ b/deps/npm/doc/cli/npm-hook.md
@@ -48,7 +48,7 @@ $ npm hook rm id-deadbeef
 ## DESCRIPTION
 
 Allows you to manage [npm
-hooks](http://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm),
+hooks](https://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm),
 including adding, removing, listing, and updating.
 
 Hooks allow you to configure URL endpoints that will be notified whenever a
@@ -69,4 +69,4 @@ request came from your own configured hook.
 
 ## SEE ALSO
 
-* ["Introducing Hooks" blog post](http://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm)
+* ["Introducing Hooks" blog post](https://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm)
diff --git a/deps/npm/doc/cli/npm-pack.md b/deps/npm/doc/cli/npm-pack.md
index f44f5e3620..807663ac21 100644
--- a/deps/npm/doc/cli/npm-pack.md
+++ b/deps/npm/doc/cli/npm-pack.md
@@ -3,7 +3,7 @@ npm-pack(1) -- Create a tarball from a package
 
 ## SYNOPSIS
 
-    npm pack [[<@scope>/]<pkg>...]
+    npm pack [[<@scope>/]<pkg>...] [--dry-run]
 
 ## DESCRIPTION
 
@@ -18,6 +18,9 @@ overwritten the second time.
 
 If no arguments are supplied, then npm packs the current package folder.
 
+The `--dry-run` argument will do everything that pack usually does without
+actually packing anything. Reports on what would have gone into the tarball.
+
 ## SEE ALSO
 
 * npm-cache(1)
diff --git a/deps/npm/doc/cli/npm-publish.md b/deps/npm/doc/cli/npm-publish.md
index 7e173ec00a..a317ff45e1 100644
--- a/deps/npm/doc/cli/npm-publish.md
+++ b/deps/npm/doc/cli/npm-publish.md
@@ -4,7 +4,7 @@ npm-publish(1) -- Publish a package
 
 ## SYNOPSIS
 
-    npm publish [<tarball>|<folder>] [--tag <tag>] [--access <public|restricted>] [--otp otpcode]
+    npm publish [<tarball>|<folder>] [--tag <tag>] [--access <public|restricted>] [--otp otpcode] [--dry-run]
 
     Publishes '.' if no argument supplied
     Sets tag 'latest' if no --tag specified
@@ -46,6 +46,10 @@ specifying a different default registry or using a `npm-scope(7)` in the name
   then you can provide a code from your authenticator with this. If you
   don't include this and you're running from a TTY then you'll be prompted.
 
+* `[--dry-run]`
+  Does everything publish would do except actually publishing to the registry.
+  Reports the details of what would have been published.
+
 Fails if the package name and version combination already exists in
 the specified registry.
 
@@ -57,9 +61,8 @@ As of `npm@5`, both a sha1sum and an integrity field with a sha512sum of the
 tarball will be submitted to the registry during publication. Subsequent
 installs will use the strongest supported algorithm to verify downloads.
 
-For a "dry run" that does everything except actually publishing to the
-registry, see `npm-pack(1)`, which figures out the files to be included and
-packs them into a tarball to be uploaded to the registry.
+Similar to `--dry-run` see `npm-pack(1)`, which figures out the files to be
+included and packs them into a tarball to be uploaded to the registry.
 
 ## SEE ALSO
 
diff --git a/deps/npm/doc/cli/npm-run-script.md b/deps/npm/doc/cli/npm-run-script.md
index dc2c93ef94..18c5736604 100644
--- a/deps/npm/doc/cli/npm-run-script.md
+++ b/deps/npm/doc/cli/npm-run-script.md
@@ -15,9 +15,9 @@ used by the test, start, restart, and stop commands, but can be called
 directly, as well. When the scripts in the package are printed out, they're
 separated into lifecycle (test, start, restart) and directly-run scripts.
 
-As of [`npm@2.0.0`](http://blog.npmjs.org/post/98131109725/npm-2-0-0), you can
+As of [`npm@2.0.0`](https://blog.npmjs.org/post/98131109725/npm-2-0-0), you can
 use custom arguments when executing scripts. The special option `--` is used by
-[getopt](http://goo.gl/KxMmtG) to delimit the end of the options. npm will pass
+[getopt](https://goo.gl/KxMmtG) to delimit the end of the options. npm will pass
 all the arguments after the `--` directly to your script:
 
     npm run test -- --grep="pattern"
diff --git a/deps/npm/doc/cli/npm-start.md b/deps/npm/doc/cli/npm-start.md
index 94c468c296..e43f021499 100644
--- a/deps/npm/doc/cli/npm-start.md
+++ b/deps/npm/doc/cli/npm-start.md
@@ -11,7 +11,7 @@ This runs an arbitrary command specified in the package's `"start"` property of
 its `"scripts"` object. If no `"start"` property is specified on the
 `"scripts"` object, it will run `node server.js`.
 
-As of [`npm@2.0.0`](http://blog.npmjs.org/post/98131109725/npm-2-0-0), you can
+As of [`npm@2.0.0`](https://blog.npmjs.org/post/98131109725/npm-2-0-0), you can
 use custom arguments when executing scripts. Refer to npm-run-script(1) for
 more details.
 
diff --git a/deps/npm/doc/cli/npm-unpublish.md b/deps/npm/doc/cli/npm-unpublish.md
index 57df24d1a0..b5b02154e9 100644
--- a/deps/npm/doc/cli/npm-unpublish.md
+++ b/deps/npm/doc/cli/npm-unpublish.md
@@ -24,14 +24,15 @@ If no version is specified, or if all versions are removed then
 the root package entry is removed from the registry entirely.
 
 Even if a package version is unpublished, that specific name and
-version combination can never be reused.  In order to publish the
-package again, a new version number must be used.
+version combination can never be reused. In order to publish the
+package again, a new version number must be used. Additionally,
+new versions of packages with every version unpublished may not
+be republished until 24 hours have passed.
 
 With the default registry (`registry.npmjs.org`), unpublish is
-only allowed with versions published in the last 72 hours.  Similarly,
-new versions of unpublished packages may not be republished until 72 hours
-have passed. If you are trying to unpublish a version published longer
-ago than that, contact support@npmjs.com.
+only allowed with versions published in the last 72 hours. If you
+are trying to unpublish a version published longer ago than that,
+contact support@npmjs.com.
 
 The scope is optional and follows the usual rules for `npm-scope(7)`.
 
diff --git a/deps/npm/doc/cli/npm-version.md b/deps/npm/doc/cli/npm-version.md
index f1a9bfccda..4cbc51eddd 100644
--- a/deps/npm/doc/cli/npm-version.md
+++ b/deps/npm/doc/cli/npm-version.md
@@ -3,7 +3,7 @@ npm-version(1) -- Bump a package version
 
 ## SYNOPSIS
 
-    npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease | from-git]
+    npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease [--preid=<prerelease-id>] | from-git]
 
     'npm [-v | --version]' to print npm version
     'npm view <pkg> version' to view a package's published version
diff --git a/deps/npm/doc/cli/npm.md b/deps/npm/doc/cli/npm.md
index 82f78a0f9b..32384547bc 100644
--- a/deps/npm/doc/cli/npm.md
+++ b/deps/npm/doc/cli/npm.md
@@ -21,6 +21,16 @@ programs.
 
 Run `npm help` to get a list of available commands.
 
+## IMPORTANT
+
+npm is configured to use npm, Inc.'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.
+
+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
+terms of use.
+
 ## INTRODUCTION
 
 You probably got npm because you want to install stuff.
@@ -140,7 +150,7 @@ reproduction to report.
 
 [Isaac Z. Schlueter](http://blog.izs.me/) ::
 [isaacs](https://github.com/isaacs/) ::
-[@izs](http://twitter.com/izs) ::
+[@izs](https://twitter.com/izs) ::
 <i@izs.me>
 
 ## SEE ALSO