all: Fix grammatical mistakes in *.tmpl files

[shmsr]

• Bug
• Docs

What does this PR do?

It fixes some grammatical mistakes in the *.tmpl files.

Why is it important?

It is important because it is important to have solid documentation with as few errors as possible. The template files are sometimes used for configuration and sometimes even for generating code. It's important to have as fewer grammatical mistakes as possible. There's a linked issue as well.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

• Closes Grammatical mistakes in template *.tmpl files  #35696

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @shmsr? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[shmsr]

It is possible there are more errors. But I'm doing this manually and even with the help of a tool but each change should be manually checked. It's possible that I missed some *.tmpl files and even some errors. But we can have multiple PRs so that changeset is reviewable in each PR.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-06-23T06:44:48.738+0000

• Duration: 150 min 31 sec

Test stats 🧪

Test	Results
Failed	0
Passed	27454
Skipped	2023
Total	29477

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[shmsr]

LGTM for the text changes! 🚀 Hopefully one of the Beats code owners can assist with the CI checks and merging, since these changes are in code files.

Thanks @kilfoyle for reviewing.

[belimawr]

/test

[shmsr]

@belimawr Whom should I ask for a review from elastic/{uptime,security-external-integrations,security-asset-management}? I'm not able to merge.

[shmsr]

Ping @elastic/security-asset-management @elastic/uptime. Could someone please review this PR?

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[andrewvc]

LGTM for the heartbeat portion

[aleksmaus]

osquerybeat updates LGTM, thank you!