RHDHBUGS-2769 - RHDH 1.9 GA release edits - formatting issue

[Gerry-Forde]

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

Version(s):

1.9, main
RHDHBUGS-2769

Preview:

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rhdh-bot]

Preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1870/

[Gerry-Forde]

/cherry-pick main

[openshift-cherrypick-robot]

@Gerry-Forde: once the present PR merges, I will cherry-pick it on top of main in a new PR and assign it to you.

Details

In response to this:

/cherry-pick main

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.

[openshift-cherrypick-robot]

@Gerry-Forde: #1870 failed to apply on top of branch "main":

Applying: RHDHBUGS-2769 - RHDH 1.9 GA release edits - formatting issue
Using index info to reconstruct a base tree...
M	modules/dynamic-plugins/ref-community-plugins-migration.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/dynamic-plugins/ref-community-plugins-migration.adoc
CONFLICT (content): Merge conflict in modules/dynamic-plugins/ref-community-plugins-migration.adoc
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 set advice.mergeConflict false"
Patch failed at 0001 RHDHBUGS-2769 - RHDH 1.9 GA release edits - formatting issue

Details

In response to this:

/cherry-pick main

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.