Fix Vale issues for ./ci/unit_test_reports.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.
14:15:gitlab.FutureTense:Avoid using future tense: will verify. Use present tense instead.
16:28:gitlab.FutureTense:Avoid using future tense: will have. Use present tense instead.
19:65:gitlab.FutureTense:Avoid using future tense: will display. Use present tense instead.
52:29:gitlab.FutureTense:Avoid using future tense: will just. Use present tense instead.
62:25:gitlab.FutureTense:Avoid using future tense: will show. Use present tense instead.
63:34:gitlab.FutureTense:Avoid using future tense: will open. Use present tense instead.
118:24:gitlab.FutureTense:Avoid using future tense: will be. Use present tense instead.
140:52:gitlab.FutureTense:Avoid using future tense: will generate. Use present tense instead.
201:5:gitlab.FutureTense:Avoid using future tense: will be. Use present tense instead.
202:1:gitlab.FutureTense:Avoid using future tense: will then. Use present tense instead.
230:6:gitlab.Acronyms:NET has no definition.
316:81:gitlab.FutureTense:Avoid using future tense: will display. Use present tense instead.
343:102:gitlab.FutureTense:Avoid using future tense: will be. Use present tense instead.
Edited by Suzanne Selhorn