Docs: Fix Vale issues with the NPM Registry topic
Problem to solve
The Vale linter is used to support grammar linting in GitLab documentation. As Vale was implemented after many of the GitLab documents were written, we have many documentation pages that do not meet the linting standards created by the GitLab Technical Writing team for Vale.
Further details
As an example, here's the output from a Vale test on the NPM Registry topic, which is in the docs here.
You don't need to fix all of these issues; fix as many as you can.
The first number is the line number in the doc file where you can find the issue.
26:39 warning Avoid using future tense: gitlab.FutureTense
"will be"
40:14 warning Avoid using future tense: gitlab.FutureTense
"will cover"
97:6 warning Avoid using future tense: gitlab.FutureTense
"will take"
103:42 warning Avoid using future tense: gitlab.FutureTense
"will need"
109:13 warning Avoid using future tense: gitlab.FutureTense
"will need"
114:301 warning Avoid using future tense: gitlab.FutureTense
"won't be"
172:11 warning Avoid using future tense: gitlab.FutureTense
"will inherit"
184:12 warning Avoid using future tense: gitlab.FutureTense
"will be"
210:20 warning Avoid using future tense: gitlab.FutureTense
"will receive"
246:30 warning Avoid using future tense: gitlab.FutureTense
"will not"
249:79 warning Avoid using future tense: gitlab.FutureTense
"will be"
257:58 warning Avoid using future tense: gitlab.FutureTense
"will need"
264:5 warning Avoid using future tense: gitlab.FutureTense
"will need"
266:11 warning Avoid using future tense: gitlab.FutureTense
"will need"
285:86 warning Avoid using future tense: gitlab.FutureTense
"will be"
371:248 warning Avoid using future tense: gitlab.FutureTense
"you'll need"