RHIDP-4090: Fixed typo

[pabel-rh]

IMPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s): 1.2, 1.3

Issue: RHIDP-4090

Reviews:

• SME: @johnmcollier
• Docs review: @hmanwani-rh or @jmagak

[rhdh-bot]

Updated preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-651/ @ 10/25/24 04:57:53

[jmagak]

LGTM, @pabel-rh

[hmanwani-rh]

@pabel-rh Before merging this PR, we’ll need approval from John.
@johnmcollier Could you please review this minor PR and provide your approval so that we can proceed with the merge?

[hmanwani-rh]

@pabel-rh Please rebase your branch

[hmanwani-rh]

/cherry-pick release-1.3

[openshift-cherrypick-robot]

@hmanwani-rh: new pull request created: #660

In response to this:

/cherry-pick release-1.3

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.

[hmanwani-rh]

/cherrypick 1.2.x

[openshift-cherrypick-robot]

@hmanwani-rh: #651 failed to apply on top of branch "1.2.x":

Applying: fixed typo
Using index info to reconstruct a base tree...
A	modules/authorization/proc-mounting-the-policy-csv-file-using-the-operator.adoc
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): modules/authorization/proc-mounting-the-policy-csv-file-using-the-operator.adoc deleted in HEAD and modified in fixed typo. Version fixed typo of modules/authorization/proc-mounting-the-policy-csv-file-using-the-operator.adoc left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 fixed typo

In response to this:

/cherrypick 1.2.x

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.