From 199e0066f562a63613fc65a5cbb18eea89bdabdf Mon Sep 17 00:00:00 2001
From: Rhys Arkins <rhys@arkins.net>
Date: Mon, 23 Jul 2018 13:33:41 +0200
Subject: [PATCH] docs: fix up private module headings

---
 website/docs/private-modules.md | 18 ++++++++++--------
 1 file changed, 10 insertions(+), 8 deletions(-)

diff --git a/website/docs/private-modules.md b/website/docs/private-modules.md
index 13e8333fe4..faf25331c9 100644
--- a/website/docs/private-modules.md
+++ b/website/docs/private-modules.md
@@ -11,7 +11,7 @@ Private npm modules are used at two times during Renovate's process.
 
 #### 1. Module lookup
 
-If a private npm module is listed as a dependency in a `package.json`, then Renovate will attempt to keep it up-to-date by querying the npm registry like it would for any other package. Hence, by default a private package lookup will fail, because of lack of credentials. This means it won't be "renovated" and its version will remain unchanged, unless you update it manually. These failures don't affect Renovate's ability to look up *other* modules in the same package file.
+If a private npm module is listed as a dependency in a `package.json`, then Renovate will attempt to keep it up-to-date by querying the npm registry like it would for any other package. Hence, by default a private package lookup will fail, because of lack of credentials. This means it won't be "renovated" and its version will remain unchanged, unless you update it manually. These failures don't affect Renovate's ability to look up _other_ modules in the same package file.
 
 Assuming the private module lookup succeeds (solutions for that are described later in this document) then private module versions will be kept up-to-date like public modules are.
 
@@ -31,17 +31,19 @@ The recommended approaches for private module authentication are:
 
 **If you are using a private registry**: Add an unencrypted `npmrc` plus an encrypted `npmToken` in config
 
-#### Add/authenticate the "renovate" npm user to your private npm modules
+All the various approaches are described below:
+
+### Add/authenticate the "renovate" npm user to your private npm modules
 
 The Renovate app itself runs with credentials for the "renovate" user on npm. Therefore, a simple solution to enabling private modules is to treat Renovate as another account on your team and add the npm user "renovate" to the necessary projects that Renovate needs to access. Renovate will then use its own npm authentication if it finds none configured in your repository.
 
-#### Commit .npmrc file into repository
+### Commit .npmrc file into repository
 
 One approach that many projects use for private repositories is to simply check in an authenticated `.npmrc` or `.yarnrc` into the repository that is then shared between all developers. Therefore anyone running `npm install` or `yarn install` from the project root will be automatically authenticated with npm without having to distribute npm logins to every developer and make sure they've run `npm login` first before installing.
 
 The good news is that this works for Renovate too. If Renovate detects a `.npmrc` or `.yarnrc` file then it will use it for its install.
 
-#### Add npmrc string to Renovate config
+### Add npmrc string to Renovate config
 
 The above solution maybe have a downside that all users of the repository (e.g. developers) will also use any `.npmrc` that is checked into the repository, instead of their own one in `~/.npmrc`. To avoid this, you can instead add your `.npmrc` authentication line to your Renovate config under the field `npmrc`. e.g. a `renovate.json` might look like this:
 
@@ -52,9 +54,9 @@ The above solution maybe have a downside that all users of the repository (e.g.
 }
 ```
 
-If configured like this, Renovate will use this to authenticate with npm.
+If configured like this, Renovate will use this to authenticate with npm and will ignore any `.npmrc` files(s) it finds checked into the repository.
 
-#### Add npmToken to Renovate config
+### Add npmToken to Renovate config
 
 If you are using the main npmjs registry then you can configure just the npmToken instead:
 
@@ -64,7 +66,7 @@ If you are using the main npmjs registry then you can configure just the npmToke
 }
 ```
 
-#### Add an encrypted npm token to Renovate config
+### Add an encrypted npm token to Renovate config
 
 If you don't wish for all users of the repository to be able to see the unencrypted token, you can encrypt it with Renovate's public key instead, so that only Renovate can decrypt it.
 
@@ -105,7 +107,7 @@ Renovate will then use the following logic:
 2.  If an `npmrc` string is present and contains `${NPM_TOKEN}` then that placeholder will be replaced with the decrypted token
 3.  If an `npmrc` string is present but doesn't contain `${NPM_TOKEN}` then the file will have `_authToken=<token>` appended to it
 
-#### Encrypted entire .npmrc file into config
+### Encrypted entire .npmrc file into config
 
 Example:
 
-- 
GitLab