fix(docs): update npm-publish access flag info

PR-URL: #3630
Credit: @austincho
Close: #3630
Reviewed-by: @wraithgar

EDIT(@isaacs): rebased and edited to put config documentation in the
correct location.

docs/content/commands/npm-publish.md

@@ -136,6 +136,12 @@ If you want your scoped package to be publicly viewable (and installable)
 set `--access=public`. The only valid values for `access` are `public` and
 `restricted`. Unscoped packages _always_ have an access level of `public`.
 
+Note: Using the `--access` flag on the `npm publish` command will only set
+the package access level on the initial publish of the package. Any
+subsequent `npm publish` commands using the `--access` flag will not have an
+effect to the access level. To make changes to the access level after the
+initial publish use `npm access`.
+
 <!-- automatically generated, do not edit manually -->
 <!-- see lib/utils/config/definitions.js -->
 

docs/content/using-npm/config.md

@@ -156,6 +156,12 @@ If you want your scoped package to be publicly viewable (and installable)
 set `--access=public`. The only valid values for `access` are `public` and
 `restricted`. Unscoped packages _always_ have an access level of `public`.
 
+Note: Using the `--access` flag on the `npm publish` command will only set
+the package access level on the initial publish of the package. Any
+subsequent `npm publish` commands using the `--access` flag will not have an
+effect to the access level. To make changes to the access level after the
+initial publish use `npm access`.
+
 <!-- automatically generated, do not edit manually -->
 <!-- see lib/utils/config/definitions.js -->
 

lib/utils/config/definitions.js

@@ -160,6 +160,12 @@ define('access', {
     (and installable) set \`--access=public\`. The only valid values for
     \`access\` are \`public\` and \`restricted\`. Unscoped packages _always_
     have an access level of \`public\`.
+
+    Note: Using the \`--access\` flag on the \`npm publish\` command will only
+    set the package access level on the initial publish of the package. Any
+    subsequent \`npm publish\` commands using the \`--access\` flag will not
+    have an effect to the access level.  To make changes to the access level
+    after the initial publish use \`npm access\`.
   `,
   flatten,
 })