chore(docs): fix styling issues on docs website

.gitignore

@@ -12,7 +12,6 @@ npm-debug.log
 /docs/.cache/
 /docs/node_modules/
 /man/
-/doc/*/npm-index.md
 /npmrc
 /release/
 /npm-*.tgz
@@ -25,3 +24,4 @@ npm-debug.log
 .nyc_output
 /test/npm_cache*
 /node_modules/.cache
+.DS_Store

docs/content/cli-commands/npm-access.md

@@ -4,7 +4,7 @@ title: npm-access
 description: Set access level on published packages
 ---
 
-# npm-access 
+# npm-access(1)
 
 ## Set access level on published packages
 

docs/content/cli-commands/npm-adduser.md

@@ -4,7 +4,7 @@ title: npm-adduser
 description: Set access level on published packages
 ---
 
-# npm-adduser
+# npm-adduser(1)
 
 ## Add a registry user account
 
@@ -20,7 +20,7 @@ aliases: login, add-user
 
 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 [`npm-config`](npm-config)).
+the default registry will be used (see [`config`](/using-npm/config)).
 
 The username, password, and email are read in from prompts.
 
@@ -43,14 +43,14 @@ Default: https://registry.npmjs.org/
 
 The base URL of the npm package registry. If `scope` is also specified,
 this registry will only be used for packages with that scope. `scope` defaults
-to the scope of the project directory you're currently in, if any. See [`npm-scope`](/docs/using-npm/scope).
+to the scope of the project directory you're currently in, if any. See [`scope`](/using-npm/scope).
 
 #### scope
 
 Default: none
 
 If specified, the user and login credentials given will be associated
-with the specified scope. See [`npm-scope`](/docs/using-npm/scope). You can use both at the same time,
+with the specified scope. See [`scope`](/using-npm/scope). You can use both at the same time,
 e.g.
 
 ```bash
@@ -75,9 +75,7 @@ registries. Can be used with `--registry` and / or `--scope`, e.g.
 This will ensure that all requests to that registry (including for tarballs)
 include an authorization header. This setting may be necessary for use with
 private registries where metadata and package tarballs are stored on hosts with
-different hostnames. See `always-auth` in [`npm-config`](/docs/using-npm/config) for more details on
-always-auth. Registry-specific configuration of `always-auth` takes precedence
-over any global configuration.
+different hostnames. See `always-auth` in [`config`](/using-npm/config) for more details on always-auth. Registry-specific configuration of `always-auth` takes precedence over any global configuration.
 
 #### auth-type
 

docs/content/cli-commands/npm-audit.md

@@ -4,7 +4,7 @@ title: npm-audit
 description: Run a security audit
 ---
 
-# npm-audit
+# npm-audit(1)
 
 ## Run a security audit
 

docs/content/cli-commands/npm-bin.md

@@ -4,7 +4,7 @@ title: npm-bin
 description: Display npm bin folder
 ---
 
-# npm-bin
+# npm-bin(1)
 
 ## Display npm bin folder
 

docs/content/cli-commands/npm-bugs.md

@@ -4,7 +4,7 @@ title: npm-bugs
 description: Bugs for a package in a web browser maybe
 ---
 
-# npm-bugs
+# npm-bugs(1)
 
 ## Bugs for a package in a web browser maybe
 

docs/content/cli-commands/npm-build.md

@@ -4,7 +4,7 @@ title: npm-build
 description: Build a package
 ---
 
-# npm-build
+# npm-build(1)
 
 ## Build a package
 

docs/content/cli-commands/npm-bundle.md

@@ -4,7 +4,7 @@ title: npm-bundle
 description: REMOVED
 ---
 
-# npm-bundle
+# npm-bundle(1)
 
 ## REMOVED
 

docs/content/cli-commands/npm-cache.md

@@ -4,7 +4,7 @@ title: npm-cache
 description: Manipulates packages cache
 ---
 
-# npm-cache
+# npm-cache(1)
 
 ## Manipulates packages cache
 

docs/content/cli-commands/npm-ci.md

@@ -4,7 +4,7 @@ title: npm-ci
 description: Install a project with a clean slate
 ---
 
-# npm-ci
+# npm-ci(1)
 
 ## Install a project with a clean slate
 
@@ -45,7 +45,7 @@ cache:
 
 ### Description
 
-This command is similar to [`npm-install`](npm-install), except it's meant to be used in
+This command is similar to [`npm install`](/cli-commands/npm-install), except it's meant to be used in
 automated environments such as test platforms, continuous integration, and
 deployment -- or any situation where you want to make sure you're doing a clean
 install of your dependencies. It can be significantly faster than a regular npm

docs/content/cli-commands/npm-completion.md

@@ -4,7 +4,7 @@ title: npm-completion
 description: Tab Completion for npm
 ---
 
-# npm-completion
+# npm-completion(1)
 
 ## Tab Completion for npm
 

docs/content/cli-commands/npm-config.md

@@ -4,7 +4,7 @@ title: npm-config
 description: Manage the npm configuration files
 ---
 
-# npm-config
+# npm-config(1)
 
 ## Manage the npm configuration files
 
@@ -26,9 +26,9 @@ aliases: c
 npm gets its config settings from the command line, environment
 variables, `npmrc` files, and in some cases, the `package.json` file.
 
-See [npmrc](/docs/configuring-npm/npmrc) for more information about the npmrc files.
+See [npmrc](/configuring-npm/npmrc) for more information about the npmrc files.
 
-See [config](/docs/using-npm/config) for a more thorough discussion of the mechanisms
+See [config](/using-npm/config) for a more thorough discussion of the mechanisms
 involved.
 
 The `npm config` command can be used to update and edit the contents

docs/content/cli-commands/npm-dedupe.md

@@ -4,7 +4,7 @@ title: npm-dedupe
 description: Reduce duplication
 ---
 
-# npm-dedupe
+# npm-dedupe(1)
 
 ## Reduce duplication
 
@@ -32,7 +32,7 @@ a
     `-- c@1.0.10
 ```
 
-In this case, `npm-dedupe` will transform the tree to:
+In this case, `npm dedupe` will transform the tree to:
 
 ```bash
 a

docs/content/cli-commands/npm-deprecate.md

@@ -3,7 +3,7 @@ section: cli-commands
 title: npm-deprecate
 description: Deprecate a version of a package
 ---
-# npm-deprecate
+# npm-deprecate(1)
 
 ## Deprecate a version of a package
 

docs/content/cli-commands/npm-dist-tag.md

@@ -4,7 +4,7 @@ title: npm-dist-tag
 description: Modify package distribution tags
 ---
 
-# npm-dist-tag
+# npm-dist-tag(1)
 
 ## Modify package distribution tags
 

docs/content/cli-commands/npm-docs.md

@@ -4,11 +4,10 @@ title: npm-docs
 description: Docs for a package in a web browser maybe
 ---
 
-# npm-docs 
+# npm-docs(1) 
 
 ## Docs for a package in a web browser maybe
 
-
 ### Synopsis
 
 ```bash

docs/content/cli-commands/npm-doctor.md

@@ -4,7 +4,7 @@ title: npm-doctor
 description: Check your environments
 ---
 
-# npm-doctor
+# npm-doctor(1)
 
 ## Check your environments
 

docs/content/cli-commands/npm-edit.md

@@ -4,7 +4,7 @@ title: npm-edit
 description: Edit an installed package
 ---
 
-# npm-edit
+# npm-edit(1)
 
 ## Edit an installed package
 

docs/content/cli-commands/npm-explore.md

@@ -4,9 +4,9 @@ title: npm-explore
 description: Browse an installed package
 ---
 
-# npm-explore
+# npm-explore(1)
 
-## description: Browse an installed package
+## Browse an installed package
 
 ### Synopsis
 

docs/content/cli-commands/npm-fund.md

@@ -4,7 +4,7 @@ title: npm-fund
 description: Retrieve funding information
 ---
 
-# npm-fund
+# npm-fund(1)
 
 ## Retrieve funding information
 
@@ -53,8 +53,8 @@ Set it to `false` in order to use all-ansi output.
 
 ## See Also
 
-* [npm-docs](/cli-commands/npm-docs)
-* [npm-config](/cli-commands/npm-config)
-* [npm-install](/cli-commands/npm-install)
-* [npm-ls](/cli-commands/npm-ls)
+* [npm docs](/cli-commands/npm-docs)
+* [npm config](/cli-commands/npm-config)
+* [npm install](/cli-commands/npm-install)
+* [npm ls](/cli-commands/npm-ls)
 

docs/content/cli-commands/npm-help-search.md

@@ -4,7 +4,7 @@ title: npm-help-search
 description: Search npm help documentation
 ---
 
-# npm-help-search
+# npm-help-search(1)
 
 ## Search npm help documentation
 

docs/content/cli-commands/npm-help.md

@@ -4,7 +4,7 @@ title: npm-help
 description: Get help on npm
 ---
 
-# npm-help
+# npm-help(1)
 
 ## Get help on npm
 

docs/content/cli-commands/npm-hook.md

@@ -4,7 +4,7 @@ title: npm-hook
 description: Manage registry hooks
 ---
 
-# npm-hook
+# npm-hook(1)
 
 ## Manage registry hooks
 
@@ -56,8 +56,7 @@ $ npm hook rm id-deadbeef
 
 ### Description
 
-Allows you to manage [npm
-hooks](https://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm),
+Allows you to manage [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

docs/content/cli-commands/npm-init.md

@@ -4,7 +4,7 @@ title: npm-init
 description: create a package.json file
 ---
 
-# npm-init
+# npm-init(1)
 
 ## create a package.json file
 

docs/content/cli-commands/npm-install-ci-test.md

@@ -4,7 +4,7 @@ title: npm-install-ci-test
 description: Install a project with a clean slate and run tests
 ---
 
-# npm install-ci-test
+# npm install-ci-test(1)
 
 ## Install a project with a clean slate and run tests
 

docs/content/cli-commands/npm-install-test.md

@@ -4,7 +4,7 @@ title: npm-install-test
 description: Install package(s) and run tests
 ---
 
-# npm install-test
+# npm install-test(1)
 
 ## Install package(s) and run tests