Fix Vale issues for ./user/project/merge_requests/test_coverage_visualization.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 in each issue 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.
(Note: Please make sure your merge request title is fewer than 75 characters, starts with a capital letter, and does not end in a period. Thanks!)
26:8:gitlab.FutureTense:Avoid using future tense: will then. Use present tense instead.
44:32:gitlab.FutureTense:Avoid using future tense: will be. Use present tense instead.
45:57:gitlab.FutureTense:Avoid using future tense: will be. Use present tense instead.
51:32:gitlab.FutureTense:Avoid using future tense: will provide. Use present tense instead.
72:98:gitlab.FutureTense:Avoid using future tense: will attempt. Use present tense instead.
96:12:gitlab.FutureTense:Avoid using future tense: will extract. Use present tense instead.
99:94:gitlab.FutureTense:Avoid using future tense: will take. Use present tense instead.
102:38:gitlab.FutureTense:Avoid using future tense: will attempt. Use present tense instead.
102:213:gitlab.FutureTense:Avoid using future tense: will not. Use present tense instead.
105:138:gitlab.FutureTense:Avoid using future tense: will be. Use present tense instead.
105:207:gitlab.FutureTense:Avoid using future tense: will assume. Use present tense instead.
Edited by Suzanne Selhorn