chore: Unwrap markdown docs

Signed-off-by: Josh Soref <[email protected]>

Author: jsoref

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

@@ -10,16 +10,13 @@ description: Add a registry user account
 
 ### Description
 
-Create a new user in the specified registry, and save the credentials to
-the `.npmrc` file.
-If no registry is specified, the default registry
-will be used (see [`registry`](/using-npm/registry)).
+Create a new user in the specified registry, and save the credentials to the `.npmrc` file.
+If no registry is specified, the default registry will be used (see [`registry`](/using-npm/registry)).
 
 When you run `npm adduser`, the CLI automatically generates a legacy token of `publish` type.
 For more information, see [About legacy tokens](/about-access-tokens#about-legacy-tokens).
 
-When using `legacy` for your `auth-type`, the username, password, and
-email are read in from prompts.
+When using `legacy` for your `auth-type`, the username, password, and email are read in from prompts.
 
 ### Configuration
 

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

@@ -10,38 +10,23 @@ description: Run a security audit
 
 ### Description
 
-The audit command submits a description of the dependencies configured in
-your project to your default registry and asks for a report of known
-vulnerabilities.
- If any vulnerabilities are found, then the impact and
-appropriate remediation will be calculated.
- If the `fix` argument is
-provided, then remediations will be applied to the package tree.
+The audit command submits a description of the dependencies configured in your project to your default registry and asks for a report of known vulnerabilities.
+If any vulnerabilities are found, then the impact and appropriate remediation will be calculated.
+If the `fix` argument is provided, then remediations will be applied to the package tree.
 
 The command will exit with a 0 exit code if no vulnerabilities were found.
 
-Note that some vulnerabilities cannot be fixed automatically and will
-require manual intervention or review.
- Also note that since `npm audit
-fix` runs a full-fledged `npm install` under the hood, all configs that
-apply to the installer will also apply to `npm install` -- so things like
-`npm audit fix --package-lock-only` will work as expected.
-
-By default, the audit command will exit with a non-zero code if any
-vulnerability is found.
-It may be useful in CI environments to include the
-`--audit-level` parameter to specify the minimum vulnerability level that
-will cause the command to fail.
-This option does not filter the report
-output, it simply changes the command's failure threshold.
+Note that some vulnerabilities cannot be fixed automatically and will require manual intervention or review.
+Also note that since `npm audit fix` runs a full-fledged `npm install` under the hood, all configs that apply to the installer will also apply to `npm install` -- so things like `npm audit fix --package-lock-only` will work as expected.
+
+By default, the audit command will exit with a non-zero code if any vulnerability is found.
+It may be useful in CI environments to include the `--audit-level` parameter to specify the minimum vulnerability level that will cause the command to fail.
+This option does not filter the report output, it simply changes the command's failure threshold.
 
 ### Package lock
 
-By default npm requires a package-lock or shrinkwrap in order to run the
-audit.
- You can bypass the package lock with `--no-package-lock` but be
-aware the results may be different with every run, since npm will
-re-build the dependency tree each time.
+By default npm requires a package-lock or shrinkwrap in order to run the audit.
+You can bypass the package lock with `--no-package-lock` but be aware the results may be different with every run, since npm will re-build the dependency tree each time.
 
 ### Audit Signatures
 
@@ -53,14 +38,9 @@ Registry signatures can be verified using the following `audit` command:
 $ npm audit signatures
 ```
 
-The `audit signatures` command will also verify the provenance attestations of
-downloaded packages.
-Because provenance attestations are such a new feature,
-security features may be added to (or changed in) the attestation format over
-time.
-To ensure that you're always able to verify attestation signatures check
-that you're running the latest version of the npm CLI. Please note this often
-means updating npm beyond the version that ships with Node.js.
+The `audit signatures` command will also verify the provenance attestations of downloaded packages.
+Because provenance attestations are such a new feature, security features may be added to (or changed in) the attestation format over time.
+To ensure that you're always able to verify attestation signatures check that you're running the latest version of the npm CLI. Please note this often means updating npm beyond the version that ships with Node.js.
 
 The npm CLI supports registry signatures and signing keys provided by any registry if the following conventions are followed:
 
@@ -106,44 +86,29 @@ See this [example key's response from the public npm registry](https://registry.
 
 ### Audit Endpoints
 
-There are two audit endpoints that npm may use to fetch vulnerability
-information: the `Bulk Advisory` endpoint and the `Quick Audit` endpoint.
+There are two audit endpoints that npm may use to fetch vulnerability information: the `Bulk Advisory` endpoint and the `Quick Audit` endpoint.
 
 #### Bulk Advisory Endpoint
 
-As of version 7, npm uses the much faster `Bulk Advisory` endpoint to
-optimize the speed of calculating audit results.
+As of version 7, npm uses the much faster `Bulk Advisory` endpoint to optimize the speed of calculating audit results.
 
-npm will generate a JSON payload with the name and list of versions of each
-package in the tree, and POST it to the default configured registry at
-the path `/-/npm/v1/security/advisories/bulk`.
+npm will generate a JSON payload with the name and list of versions of each package in the tree, and POST it to the default configured registry at the path `/-/npm/v1/security/advisories/bulk`.
 
-Any packages in the tree that do not have a `version` field in their
-package.json file will be ignored.
- If any `--omit` options are specified
-(either via the [`--omit` config](/using-npm/config#omit), or one of the
-shorthands such as `--production`, `--only=dev`, and so on), then packages will
-be omitted from the submitted payload as appropriate.
+Any packages in the tree that do not have a `version` field in their package.json file will be ignored.
+If any `--omit` options are specified (either via the [`--omit` config](/using-npm/config#omit), or one of the shorthands such as `--production`, `--only=dev`, and so on), then packages will be omitted from the submitted payload as appropriate.
 
-If the registry responds with an error, or with an invalid response, then
-npm will attempt to load advisory data from the `Quick Audit` endpoint.
+If the registry responds with an error, or with an invalid response, then npm will attempt to load advisory data from the `Quick Audit` endpoint.
 
-The expected result will contain a set of advisory objects for each
-dependency that matches the advisory range.
- Each advisory object contains
-a `name`, `url`, `id`, `severity`, `vulnerable_versions`, and `title`.
+The expected result will contain a set of advisory objects for each dependency that matches the advisory range.
+Each advisory object contains a `name`, `url`, `id`, `severity`, `vulnerable_versions`, and `title`.
 
-npm then uses these advisory objects to calculate vulnerabilities and
-meta-vulnerabilities of the dependencies within the tree.
+npm then uses these advisory objects to calculate vulnerabilities and meta-vulnerabilities of the dependencies within the tree.
 
 #### Quick Audit Endpoint
 
-If the `Bulk Advisory` endpoint returns an error, or invalid data, npm will
-attempt to load advisory data from the `Quick Audit` endpoint, which is
-considerably slower in most cases.
+If the `Bulk Advisory` endpoint returns an error, or invalid data, npm will attempt to load advisory data from the `Quick Audit` endpoint, which is considerably slower in most cases.
 
-The full package tree as found in `package-lock.json` is submitted, along
-with the following pieces of additional metadata:
+The full package tree as found in `package-lock.json` is submitted, along with the following pieces of additional metadata:
 
 * `npm_version`
 * `node_version`
@@ -156,67 +121,42 @@ Omitted dependency types are skipped when generating the report.
 
 #### Scrubbing
 
-Out of an abundance of caution, npm versions 5 and 6 would "scrub" any
-packages from the submitted report if their name contained a `/` character,
-so as to avoid leaking the names of potentially private packages or git
-URLs.
+Out of an abundance of caution, npm versions 5 and 6 would "scrub" any packages from the submitted report if their name contained a `/` character, so as to avoid leaking the names of potentially private packages or git URLs.
 
-However, in practice, this resulted in audits often failing to properly
-detect meta-vulnerabilities, because the tree would appear to be invalid
-due to missing dependencies, and prevented the detection of vulnerabilities
-in package trees that used git dependencies or private modules.
+However, in practice, this resulted in audits often failing to properly detect meta-vulnerabilities, because the tree would appear to be invalid due to missing dependencies, and prevented the detection of vulnerabilities in package trees that used git dependencies or private modules.
 
 This scrubbing has been removed from npm as of version 7.
 
 #### Calculating Meta-Vulnerabilities and Remediations
 
-npm uses the
-[`@npmcli/metavuln-calculator`](http://npm.im/@npmcli/metavuln-calculator)
-module to turn a set of security advisories into a set of "vulnerability"
-objects.
- A "meta-vulnerability" is a dependency that is vulnerable by
-virtue of dependence on vulnerable versions of a vulnerable package.
+npm uses the [`@npmcli/metavuln-calculator`](http://npm.im/@npmcli/metavuln-calculator) module to turn a set of security advisories into a set of "vulnerability" objects.
+A "meta-vulnerability" is a dependency that is vulnerable by virtue of dependence on vulnerable versions of a vulnerable package.
 
-For example, if the package `foo` is vulnerable in the range `>=1.0.2
-<2.0.0`, and the package `bar` depends on `foo@^1.1.0`, then that version
-of `bar` can only be installed by installing a vulnerable version of `foo`.
+For example, if the package `foo` is vulnerable in the range `>=1.0.2 <2.0.0`, and the package `bar` depends on `foo@^1.1.0`, then that version of `bar` can only be installed by installing a vulnerable version of `foo`.
 In this case, `bar` is a "metavulnerability".
 
-Once metavulnerabilities for a given package are calculated, they are
-cached in the `~/.npm` folder and only re-evaluated if the advisory range
-changes, or a new version of the package is published (in which case, the
-new version is checked for metavulnerable status as well).
+Once metavulnerabilities for a given package are calculated, they are cached in the `~/.npm` folder and only re-evaluated if the advisory range changes, or a new version of the package is published (in which case, the new version is checked for metavulnerable status as well).
 
-If the chain of metavulnerabilities extends all the way to the root
-project, and it cannot be updated without changing its dependency ranges,
-then `npm audit fix` will require the `--force` option to apply the
-remediation.
- If remediations do not require changes to the dependency
-ranges, then all vulnerable packages will be updated to a version that does
-not have an advisory or metavulnerability posted against it.
+If the chain of metavulnerabilities extends all the way to the root project, and it cannot be updated without changing its dependency ranges, then `npm audit fix` will require the `--force` option to apply the remediation.
+If remediations do not require changes to the dependency ranges, then all vulnerable packages will be updated to a version that does not have an advisory or metavulnerability posted against it.
 
 ### Exit Code
 
-The `npm audit` command will exit with a 0 exit code if no vulnerabilities
-were found.
- The `npm audit fix` command will exit with 0 exit code if no
-vulnerabilities are found _or_ if the remediation is able to successfully
-fix all vulnerabilities.
+The `npm audit` command will exit with a 0 exit code if no vulnerabilities were found.
+The `npm audit fix` command will exit with 0 exit code if no vulnerabilities are found _or_ if the remediation is able to successfully fix all vulnerabilities.
 
 If vulnerabilities were found the exit code will depend on the
 [`audit-level` config](/using-npm/config#audit-level).
 
 ### Examples
 
-Scan your project for vulnerabilities and automatically install any compatible
-updates to vulnerable dependencies:
+Scan your project for vulnerabilities and automatically install any compatible updates to vulnerable dependencies:
 
 ```bash
 $ npm audit fix
 ```
 
-Run `audit fix` without modifying `node_modules`, but still updating the
-pkglock:
+Run `audit fix` without modifying `node_modules`, but still updating the pkglock:
 
 ```bash
 $ npm audit fix --package-lock-only
@@ -228,22 +168,19 @@ Skip updating `devDependencies`:
 $ npm audit fix --only=prod
 ```
 
-Have `audit fix` install SemVer-major updates to toplevel dependencies, not
-just SemVer-compatible ones:
+Have `audit fix` install SemVer-major updates to toplevel dependencies, not just SemVer-compatible ones:
 
 ```bash
 $ npm audit fix --force
 ```
 
-Do a dry run to get an idea of what `audit fix` will do, and _also_ output
-install information in JSON format:
+Do a dry run to get an idea of what `audit fix` will do, and _also_ output install information in JSON format:
 
 ```bash
 $ npm audit fix --dry-run --json
 ```
 
-Scan your project for vulnerabilities and just show the details, without
-fixing anything:
+Scan your project for vulnerabilities and just show the details, without fixing anything:
 
 ```bash
 $ npm audit

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

@@ -10,12 +10,8 @@ description: Report bugs for a package in a web browser
 
 ### Description
 
-This command tries to guess at the likely location of a package's bug
-tracker URL or the `mailto` URL of the support email, and then tries to
-open it using the [`--browser` config](/using-npm/config#browser) param.
-If no
-package name is provided, it will search for a `package.json` in the current
-folder and use the `name` property.
+This command tries to guess at the likely location of a package's bug tracker URL or the `mailto` URL of the support email, and then tries to open it using the [`--browser` config](/using-npm/config#browser) param.
+If no package name is provided, it will search for a `package.json` in the current folder and use the `name` property.
 
 ### Configuration
 

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

@@ -61,8 +61,7 @@ The npm cache is strictly a cache: it should not be relied upon as a persistent
 npm makes no guarantee that a previously-cached piece of data will be available later, and will automatically delete corrupted contents.
 The primary guarantee that the cache makes is that, if it does return data, that data will be exactly the data that was inserted.
 
-To run an offline verification of existing cache contents, use `npm cache
-verify`.
+To run an offline verification of existing cache contents, use `npm cache verify`.
 
 ### Configuration
 

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

@@ -10,10 +10,8 @@ description: Clean install a project
 
 ### Description
 
-This command is similar to [`npm install`](/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.
+This command is similar to [`npm install`](/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.
 
 The main differences between using `npm install` and `npm ci` are:
 
@@ -30,10 +28,8 @@ The main differences between using `npm install` and `npm ci` are:
 
 NOTE: If you create your `package-lock.json` file by running `npm install`
 with flags that can affect the shape of your dependency tree, such as
-`--legacy-peer-deps` or `--install-links`, you _must_ provide the same
-flags to `npm ci` or you are likely to encounter errors.
-An easy way to do
-this is to run, for example,
+`--legacy-peer-deps` or `--install-links`, you _must_ provide the same flags to `npm ci` or you are likely to encounter errors.
+An easy way to do this is to run, for example,
 `npm config set legacy-peer-deps=true --location=project` and commit the
 `.npmrc` file to your repo.
 

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

@@ -12,25 +12,19 @@ description: Tab Completion for npm
 
 Enables tab-completion in all npm commands.
 
-The synopsis above
-loads the completions into your current shell.
- Adding it to
-your ~/.bashrc or ~/.zshrc will make the completions available
-everywhere:
+The synopsis above loads the completions into your current shell.
+ Adding it to your ~/.bashrc or ~/.zshrc will make the completions available everywhere:
 
 ```bash
 npm completion >> ~/.bashrc
 npm completion >> ~/.zshrc
 ```
 
-You may of course also pipe the output of `npm completion` to a file
-such as `/usr/local/etc/bash_completion.d/npm` or 
+You may of course also pipe the output of `npm completion` to a file such as `/usr/local/etc/bash_completion.d/npm` or 
 `/etc/bash_completion.d/npm` if you have a system that will read 
 that file for you.
 
-When `COMP_CWORD`, `COMP_LINE`, and `COMP_POINT` are defined in the
-environment, `npm completion` acts in "plumbing mode", and outputs
-completions based on the arguments.
+When `COMP_CWORD`, `COMP_LINE`, and `COMP_POINT` are defined in the environment, `npm completion` acts in "plumbing mode", and outputs completions based on the arguments.
 
 ### See Also