Fix Vale issues for integration/elasticsearch.md

The following issues occurred when we ran a linting tool called "Vale" against this Markdown page in the GitLab documentation. The first number on each line indicates the line number where the error occurred.

To fix the issues, open a merge request for the markdown file, which you can find in the /doc directory. When you open the MR, a bot will automatically ping the appropriate GitLab technical writer. They will work with you to merge the changes.

If you feel any of these warnings are incorrect, please create an issue with the tw-test label so we can improve our Vale tests.

On the following lines, please replace future tense with present tense, in order to with to, etc. Thank you!

Updated Feb 22, 2022

245:30 Use "dropdown list".
269:4 Warning:If possible, use "select" instead of "Click".
435:1 Be concise: "to" is less wordy than "In order to".
439:78 Suggestions:Consider "in" instead of "within".
441:1 Suggestions:Consider "we recommend" instead of "It is recommended".
442:88 Suggestions:Consider "after you" instead of "Once you".
443:33 Warning:If possible, use "select" instead of "click".
591:121 Avoid using future tense: "will have". Use present tense instead.
619:8 Warning:If possible, use "select" instead of "click".
643:22 Avoid using future tense: "will index". Use present tense instead.
648:39 Avoid using future tense: "will skip". Use present tense instead.
653:7 Avoid using future tense: "will check". Use present tense instead.
721:240 Suggestions:Consider "because" or "after" instead of "since".
721:405 Be concise: "to" is less wordy than "in order to".
727:201 Avoid using future tense: "will allow". Use present tense instead.
834:8 Avoid using future tense: "will allow". Use present tense instead.
836:9 Avoid using future tense: "will behave". Use present tense instead.
850:13 Avoid using future tense: "will be". Use present tense instead.
866:39 Avoid using future tense: "will be". Use present tense instead.
871:12 Verify this use of the word "admin". Can it be updated to "administration", "administrator", "administer", or "Admin Area"?
926:5 Avoid using future tense: "will need". Use present tense instead.
941:205 Be concise: "to" is less wordy than "In order to".
949:82 Avoid using future tense: "will get". Use present tense instead.
986:80 Avoid using future tense: "will be". Use present tense instead.
989:240 Avoid using future tense: "will need". Use present tense instead.
989:314 Avoid using future tense: "will result". Use present tense instead.
989:365 Avoid using future tense: "will corrupt". Use present tense instead.
991:262 Avoid using future tense: "will no". Use present tense instead.
1011:1 Suggestions:Consider "after you" instead of "Once you".
1044:25 Avoid using future tense: "will likely". Use present tense instead.
1045:38 Avoid using future tense: "will not". Use present tense instead.
1068:17 Avoid using future tense: "will store". Use present tense instead.
1069:18 Avoid using future tense: "will only". Use present tense instead.
1070:17 Avoid using future tense: "will honor". Use present tense instead.