Fix Vale issues for development/uploads/working_with_uploads.md
👋
Hi community contributors! Do you want to work on this issue?
-
If the issue is unassigned, in a comment, type
@docs-hackathon I would like to work on this issue
and a writer will assign it to you.To be fair to others, do not ask for more than three issues at a time.
-
If the issue is assigned to someone already, choose another issue. Do not open a merge request for this issue if you are not assigned.
To resolve the issue
Follow these instructions to create a merge request.
- Don't submit your merge request until after the Hackathon has started.
- Try to address the issue in a single merge request.
- Try to stick to the scope of the issue. If you see other improvements that can be made in the file, open a separate merge request.
- When you create the merge request, select the Documentation merge request description template.
- In the merge request's description, add a link to this issue.
- Follow the commit message guidelines. Use three to five words for your commit message, start with message with a capital letter, and do not end it in a period. Other commit messages can cause the pipeline to fail.
Thank you again for contributing to the GitLab documentation!
Documentation issue
In the file development/uploads/working_with_uploads.md, update the following lines to address the listed issue.
Line | Rule | Suggestion |
---|---|---|
41 | gitlab.FutureTense | Instead of future tense 'will find', use present tense. |
56 | gitlab.FutureTense | Instead of future tense 'will outline', use present tense. |
110 | gitlab.FutureTense | Instead of future tense 'won't get', use present tense. |
126 | gitlab.Wordy | Remove the phrase 'note that'. |
127 | gitlab.FutureTense | Instead of future tense 'will be', use present tense. |
157 | gitlab.FutureTense | Instead of future tense 'will describe', use present tense. |
200 | gitlab.LatinTerms | Use 'for example' instead of 'e.g.', but consider rewriting the sentence. |
203 | gitlab.Wordy | Remove the phrase 'note that'. |
208 | gitlab.FutureTense | Instead of future tense 'will be', use present tense. |
221 | gitlab.Normal | Use 'typical' or 'standard' instead of 'normal'. |
231 | gitlab.FutureTense | Instead of future tense 'will copy', use present tense. |
237 | gitlab.Normal | Use 'usually' or 'typically' instead of 'Normally'. |
281 | gitlab.Normal | Use 'usually' or 'typically' instead of 'Normally'. |
297 | gitlab.FutureTense | Instead of future tense 'going to make', use present tense. |