Docs: Fix Vale issues in ci/triggers/README.md
Problem to solve
The Vale linter is used to support grammar linting in GitLab documentation. Because 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
As an example, here's the output from a Vale test on the Triggering pipelines through the API topic, which is in the docs here.
You don't need to fix all of these issues; fix as many as you can.
The first number is the line number in the doc file where you can find the issue.
98:30 warning Avoid using future tense: gitlab.FutureTense
"going to your"
99:69 warning Avoid using future tense: gitlab.FutureTense
"will create"
124:40 warning Avoid using future tense: gitlab.FutureTense
"will be"
149:39 warning Avoid using future tense: gitlab.FutureTense
"will get"
172:68 warning Avoid using future tense: gitlab.FutureTense
"will run"
173:18 warning Avoid using future tense: gitlab.FutureTense
"will be"
174:39 warning Avoid using future tense: gitlab.FutureTense
"will run"
193:1 warning Avoid using future tense: gitlab.FutureTense
"will be"
240:44 warning Avoid using future tense: gitlab.FutureTense
"will run"
269:41 warning Avoid using future tense: gitlab.FutureTense
"will be"
272:67 warning Avoid using future tense: gitlab.FutureTense
"will be"