Improve documentation for editing files at the command line
Unless you're a Tichtov student, please do not take this issue, or create an MR for it.
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 gitlab-basics/command-line-commands.md file:
doc/gitlab-basics/command-line-commands.md
10:72 warning Avoid using future tense: gitlab.FutureTense
"will need"
17:11 warning Avoid using future tense: gitlab.FutureTense
"will need"
60:1 suggestion Use "it's" instead of "It is", gitlab.ContractionsKeep
for a friendly, informal tone.
99:1 warning Avoid using future tense: gitlab.FutureTense
"will likely"
111:4 suggestion Use "you're" instead of "you gitlab.ContractionsKeep
are", for a friendly, informal
tone.
112:1 warning Avoid using future tense: gitlab.FutureTense
"will help"
Each of these messages point to a specific line:column in the noted file.
Proposal
Consider each error message, and see if you can rewrite the noted file with a solution.
Who can address the issue
Anyone with an understanding of basic written US English. Ideally, that person should also have some domain expertise in the subject area.
Additional notes
We appreciate any help that you can provide. If you cannot resolve some of the issues, that is OK, your contributions are still appreciated. And thank you!