Improve Container Registry Admin doc based on Vale warnings
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
Here's the output from a Vale test on the container_registry.md file. This file lives here in the documentation.
80:76 warning Avoid using future tense: gitlab.FutureTense
"will not"
125:17 warning Avoid using future tense: gitlab.FutureTense
"will be"
183:58 warning Avoid using future tense: gitlab.FutureTense
"will need"
275:47 warning Avoid using future tense: gitlab.FutureTense
"will be"
311:27 warning If possible, use "file system" gitlab.SubstitutionWarning
instead of "filesystem".
318:3 warning If possible, use "file system" gitlab.SubstitutionWarning
instead of "filesystem".
318:41 warning If possible, use "file system" gitlab.SubstitutionWarning
instead of "filesystem".
330:9 warning If possible, use "file system" gitlab.SubstitutionWarning
instead of "filesystem".
332:41 warning If possible, use "file system" gitlab.SubstitutionWarning
instead of "filesystem".
380:1 warning If possible, use "file system" gitlab.SubstitutionWarning
instead of "filesystem".
439:18 warning If possible, use gitlab.SubstitutionWarning
"administrator" instead of
"admin".
471:35 warning Avoid using future tense: gitlab.FutureTense
"going to perform"
478:61 warning Avoid using future tense: gitlab.FutureTense
"will delete"
548:69 warning Avoid using future tense: gitlab.FutureTense
"will be"
607:42 warning Avoid using future tense: gitlab.FutureTense
"will need"
750:16 warning Avoid using future tense: gitlab.FutureTense
"will be"
766:24 warning Avoid using future tense: gitlab.FutureTense
"will be"
810:14 warning Avoid using future tense: gitlab.FutureTense
"will take"
855:5 warning Avoid using future tense: gitlab.FutureTense
"will be"
855:63 warning Avoid using future tense: gitlab.FutureTense
"will not"
884:9 warning Avoid using future tense: gitlab.FutureTense
"will set"
896:9 warning Avoid using future tense: gitlab.FutureTense
"will start"
923:54 warning Avoid using future tense: gitlab.FutureTense
"will run"
999:53 warning If possible, use gitlab.SubstitutionWarning
"administrator" instead of
"Admin".
1141:4 warning Avoid using future tense: gitlab.FutureTense
"will use"
1213:6 warning Avoid using future tense: gitlab.FutureTense
"will run"
1219:40 warning Avoid using future tense: gitlab.FutureTense
"will see"
1234:6 warning Avoid using future tense: gitlab.FutureTense
"will launch"
1259:48 warning Avoid using future tense: gitlab.FutureTense
"will go" 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.
Additional notes
We appreciate any help you can provide. If you cannot resolve some of the issues, that is OK, your contributions are still appreciated. And thank you!