Fixed Vale future tense issues

What does this MR do?

This MR fixes the following Vale issues in the file: /docs/configuration/autoscale.md.

167:1   error  Avoid using future tense: "will be". Use present tense instead.        gitlab.FutureTense
167:65  error  Avoid using future tense: "will be". Use present tense instead.        gitlab.FutureTense
169:8   error  Avoid using future tense: "will start". Use present tense instead.     gitlab.FutureTense
183:35  error  Avoid using future tense: "will be". Use present tense instead.        gitlab.FutureTense
184:15  error  Avoid using future tense: "will always". Use present tense instead.    gitlab.FutureTense
194:43  error  Avoid using future tense: "will tell". Use present tense instead.      gitlab.FutureTense
199:50  error  Avoid using future tense: "will run". Use present tense instead.       gitlab.FutureTense
201:12  error  Avoid using future tense: "will generate". Use present tense instead.  gitlab.FutureTense
232:20  error  Avoid using future tense: "will have". Use present tense instead.      gitlab.FutureTense
233:74  error  Avoid using future tense: "will not". Use present tense instead.       gitlab.FutureTense
254:14  error  Avoid using future tense: "will be". Use present tense instead.        gitlab.FutureTense
254:72  error  Avoid using future tense: "will be". Use present tense instead.        gitlab.FutureTense
276:69  error  Avoid using future tense: "will be". Use present tense instead.        gitlab.FutureTense
277:40  error  Avoid using future tense: "will be". Use present tense instead.        gitlab.FutureTense
285:56  error  Avoid using future tense: "will be". Use present tense instead.        gitlab.FutureTense
293:34  error  Avoid using future tense: "will be". Use present tense instead.        gitlab.FutureTense
294:52  error  Avoid using future tense: "will be". Use present tense instead.        gitlab.FutureTense
304:63  error  Avoid using future tense: "will be". Use present tense instead.        gitlab.FutureTense
322:1   error  Avoid using future tense: "will enable". Use present tense instead.    gitlab.FutureTense
344:56  error  Avoid using future tense: "will be". Use present tense instead.        gitlab.FutureTense
345:33  error  Avoid using future tense: "will execute". Use present tense instead.   gitlab.FutureTense
346:30  error  Avoid using future tense: "will not". Use present tense instead.       gitlab.FutureTense
353:55  error  Avoid using future tense: "will query". Use present tense instead.     gitlab.FutureTense
354:5   error  Avoid using future tense: "will download". Use present tense instead.  gitlab.FutureTense
379:6   error  Avoid using future tense: "will remove". Use present tense instead.    gitlab.FutureTense
380:24  error  Avoid using future tense: "will share". Use present tense instead.     gitlab.FutureTense
386:70  error  Avoid using future tense: "will provide". Use present tense instead.   gitlab.FutureTense
387:49  error  Avoid using future tense: "will be". Use present tense instead.        gitlab.FutureTense
389:19  error  Avoid using future tense: "will be". Use present tense instead.        gitlab.FutureTense
391:26  error  Avoid using future tense: "will exist". Use present tense instead.     gitlab.FutureTense

Related issues

Related to: gitlab#284446 (closed)

Author's checklist (required)

• Follow the Documentation Guidelines and Style Guide.
• If you have developer access or higher (for example, GitLab team members or Core Team members)
  • Apply the documentation label.
  • Assign the designated Technical Writer.

When applicable:

• Update the permissions table.
• Link docs to and from the higher-level index page, plus other related docs where helpful.
• Add GitLab's version history note(s).
• Add/update the feature flag section.
• If you're changing document headings, search docs/* for old headings and replace them with the new ones to avoid broken anchors.

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

• Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

• Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
  • Ensure Technical Writing, documentation, and a docs:: scoped label are added.
  • Add docs-only when the only files changed are under docs/*.
  • Add twdoing when starting work on the MR.
  • Add twfinished if Technical Writing team work on the MR is complete but it remains open.

3. Maintainer

1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
2. Ensure a release milestone is set.
3. If there has not been a technical writer review, create an issue for one using the Doc Review template.