docs: add hash to "tag" config link

docs/content/commands/npm-adduser.md

@@ -27,7 +27,7 @@ Note: This command is unaware of workspaces.
 
 Create or verify a user named `<username>` in the specified registry, and
 save the credentials to the `.npmrc` file. If no registry is specified,
-the default registry will be used (see [`config`](/using-npm/config)).
+the default registry will be used (see [`registry`](/using-npm/registry)).
 
 The username, password, and email are read in from prompts.
 

docs/content/commands/npm-config.md

@@ -35,7 +35,7 @@ variables, `npmrc` files, and in some cases, the `package.json` file.
 See [npmrc](/configuring-npm/npmrc) for more information about the npmrc
 files.
 
-See [config(7)](/using-npm/config) for a more thorough explanation of the
+See [config](/using-npm/config) for a more thorough explanation of the
 mechanisms involved, and a full list of config options available.
 
 The `npm config` command can be used to update and edit the contents

docs/content/commands/npm-install.md

@@ -127,7 +127,7 @@ into a tarball (b).
 * `npm install [<@scope>/]<name>`:
 
     Do a `<name>@<tag>` install, where `<tag>` is the "tag" config. (See
-    [`config`](/using-npm/config). The config's default value is `latest`.)
+    [`config`](/using-npm/config#tag). The config's default value is `latest`.)
 
     In most cases, this will install the version of the modules tagged as
     `latest` on the npm registry.

docs/content/using-npm/package-spec.md

@@ -101,6 +101,6 @@ Examples:
 
 ### See also
 
-[npm-package-arg](https://npm.im/npm-package-arg)
-[scope](/using-npm/scope)
-[config](/using-npm/config)
+* [npm-package-arg](https://npm.im/npm-package-arg)
+* [scope](/using-npm/scope)
+* [config](/using-npm/config)