RHDEVDOCS-7643: Fix duplicate word in GitOps 1.18 Glossary Application Controller entry

[sampadasawant-36]

Summary

Fixes a persistent duplicate word typo in the OpenShift GitOps Glossary (section 2.2) for version 1.18.

Location: Glossary of common terms → Application Controller (Argo CD Application Controller)

Change:

• Before: A controller that that performs the following actions...
• After: A controller that performs the following actions...

Jira: https://redhat.atlassian.net/browse/RHDEVDOCS-7643

This same typo is present in versions 1.13–1.18 and is being fixed in separate PRs for each version. It is already corrected in 1.19, 1.20, and gitops-docs-main.

Made with Cursor

[openshift-ci-robot]

@sampadasawant-36: This pull request references RHDEVDOCS-7643 which is a valid jira issue.

Details

In response to this:

Summary

Fixes a persistent duplicate word typo in the OpenShift GitOps Glossary (section 2.2) for version 1.18.

Location: Glossary of common terms → Application Controller (Argo CD Application Controller)

Change:

• Before: A controller that that performs the following actions...
• After: A controller that performs the following actions...

Jira: https://redhat.atlassian.net/browse/RHDEVDOCS-7643

This same typo is present in versions 1.13–1.18 and is being fixed in separate PRs for each version. It is already corrected in 1.19, 1.20, and gitops-docs-main.

Made with Cursor

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hi @sampadasawant-36. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.