chore: Guard markdown blocks

perl -pi -e 's/^(\`\`\`[a-z]+)/$1\n/'

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>

Author: jsoref

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

@@ -35,6 +35,7 @@ To ensure the integrity of packages you download from the public npm registry, o
 Registry signatures can be verified using the following `audit` command:
 
 ```bash
+
 $ npm audit signatures
 ```
 
@@ -47,6 +48,7 @@ The npm CLI supports registry signatures and signing keys provided by any regist
 1. Signatures are provided in the package's `packument` in each published version within the `dist` object:
 
 ```json
+
 "dist":{
   "..omitted..": "..omitted..",
   "signatures": [{
@@ -153,48 +155,56 @@ If vulnerabilities were found the exit code will depend on the
 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:
 
 ```bash
+
 $ npm audit fix --package-lock-only
 ```
 
 Skip updating `devDependencies`:
 
 ```bash
+
 $ npm audit fix --only=prod
 ```
 
 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:
 
 ```bash
+
 $ npm audit fix --dry-run --json
 ```
 
 Scan your project for vulnerabilities and just show the details, without fixing anything:
 
 ```bash
+
 $ npm audit
 ```
 
 Get the detailed audit report in JSON format:
 
 ```bash
+
 $ npm audit --json
 ```
 
 Fail an audit only if the results include a vulnerability with a level of moderate or higher:
 
 ```bash
+
 $ npm audit --audit-level=moderate
 ```
 

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

@@ -38,6 +38,7 @@ An easy way to do this is to run, for example,
 Make sure you have a package-lock and an up-to-date install:
 
 ```bash
+
 $ cd ./my/npm/project
 $ npm install
 added 154 packages in 10s
@@ -47,13 +48,15 @@ $ ls | grep package-lock
 Run `npm ci` in that project
 
 ```bash
+
 $ npm ci
 added 154 packages in 5s
 ```
 
 Configure Travis CI to build using `npm ci` instead of `npm install`:
 
 ```bash
+
 # .travis.yml
 install:
 - npm ci

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

@@ -16,6 +16,7 @@ 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
 ```

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

@@ -25,6 +25,7 @@ Config supports the following sub-commands:
 #### set
 
 ```bash
+
 npm config set key=value [key=value...]
 npm set key=value [key=value...]
 ```
@@ -39,6 +40,7 @@ Note: for backwards compatibility, `npm config set key value` is supported as an
 #### get
 
 ```bash
+
 npm config get [key ...]
 npm get [key ...]
 ```
@@ -52,6 +54,7 @@ If no keys are provided, then this command behaves the same as `npm config list`
 #### list
 
 ```bash
+
 npm config list
 ```
 
@@ -63,6 +66,7 @@ to show the settings in json format.
 #### delete
 
 ```bash
+
 npm config delete key [key ...]
 ```
 
@@ -71,6 +75,7 @@ Deletes the specified keys from all configuration files.
 #### edit
 
 ```bash
+
 npm config edit
 ```
 
@@ -80,6 +85,7 @@ Opens the config file in an editor.
 #### fix
 
 ```bash
+
 npm config fix
 ```
 

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

@@ -25,6 +25,7 @@ a
 In this case, `npm dedupe` will transform the tree to:
 
 ```bash
+
 a
 +-- b
 +-- d

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

@@ -15,6 +15,7 @@ This command will update the npm registry entry for a package, providing a depre
 It works on [version ranges](https://semver.npmjs.com/) as well as specific versions, so you can do something like this:
 
 ```bash
+
 npm deprecate my-thing@"< 0.2.3" "critical bug fixed in v0.2.3"
 ```
 
@@ -23,6 +24,7 @@ include prerelease versions.
  For example:
 
 ```bash
+
 npm deprecate my-thing@1.x "1.x is no longer supported"
 ```
 

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

@@ -32,12 +32,14 @@ This is the default action if none is specified.
 A tag can be used when installing packages as a reference to a version instead of using a specific version number:
 
 ```bash
+
 npm install <name>@<tag>
 ```
 
 When installing dependencies, a preferred tagged version may be specified:
 
 ```bash
+
 npm install --tag <tag>
 ```
 

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

@@ -19,6 +19,7 @@ The package spec can also refer to a folder within `./node_modules`
 For example, running `npm explain glob` within npm's source tree will show:
 
 ```bash
+
 glob@7.1.6
 node_modules/glob
   glob@"^7.1.4" from the root project
@@ -36,6 +37,7 @@ To explain just the package residing at a specific folder, pass that as the argu
  This can be useful when trying to figure out exactly why a given dependency is being duplicated to satisfy conflicting version requirements within the project.
 
 ```bash
+
 $ npm explain node_modules/nyc/node_modules/find-up
 find-up@3.0.0 dev
 node_modules/nyc/node_modules/find-up

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

@@ -17,6 +17,7 @@ If a command is specified, then it is run in the subshell, which then immediatel
 This is particularly handy in the case of git submodules in the `node_modules` folder:
 
 ```bash
+
 npm explore some-dependency -- git pull origin master
 ```
 

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

@@ -31,6 +31,7 @@ It's possible to filter the results to only include a single workspace and its d
 Here's an example running `npm fund` in a project with a configured workspace `a`:
 
 ```bash
+
 $ npm fund
 test-workspaces-fund@1.0.0
 +-- https://example.com/a
@@ -46,6 +47,7 @@ test-workspaces-fund@1.0.0
 And here is an example of the expected result when filtering only by a specific workspace `a` in the same project:
 
 ```bash
+
 $ npm fund -w a
 test-workspaces-fund@1.0.0
 `-- https://example.com/a