Fix Vale issues for ./administration/operations/ssh_certificates.md
The following issues occurred when we ran a linting tool called Vale against this topic. To fix the issues, open a merge request for the markdown file, which you'll find in the /doc directory. The first number on each line indicates the line number.
If you feel any of these warnings are incorrect, feel free to create an issue with the tw-test
label so we can improve our Vale tests.
113:5:gitlab.FutureTense:Avoid using future tense: will need. Use present tense instead.
116:17:gitlab.FutureTense:Avoid using future tense: going to be. Use present tense instead.
125:54:gitlab.FutureTense:Avoid using future tense: will be. Use present tense instead.
133:39:gitlab.FutureTense:Avoid using future tense: will enforce. Use present tense instead.
137:42:gitlab.FutureTense:Avoid using future tense: it'll just. Use present tense instead.
143:68:gitlab.FutureTense:Avoid using future tense: will still. Use present tense instead.
147:32:gitlab.FutureTense:Avoid using future tense: will fall. Use present tense instead.
152:33:gitlab.FutureTense:Avoid using future tense: you'll be. Use present tense instead.
157:14:gitlab.FutureTense:Avoid using future tense: will use. Use present tense instead.
158:38:gitlab.FutureTense:Avoid using future tense: will fall. Use present tense instead.
170:50:gitlab.LatinTerms:Use for example instead of e.g., but consider rewriting the sentence.
177:19:gitlab.FutureTense:Avoid using future tense: will show. Use present tense instead.
177:36:gitlab.FutureTense:Avoid using future tense: won't be. Use present tense instead.