Skip to content

Simplify AWS terminology in section headings - #119178

Open
msarage-ux wants to merge 1 commit into
openshift:mainfrom
msarage-ux:simplify-aws-terminology-4.20
Open

Simplify AWS terminology in section headings#119178
msarage-ux wants to merge 1 commit into
openshift:mainfrom
msarage-ux:simplify-aws-terminology-4.20

Conversation

@msarage-ux

Copy link
Copy Markdown

Summary

This PR simplifies the terminology used in section headings by replacing the verbose "Amazon Web Services (AWS)" with the concise "AWS" abbreviation, aligning with recent documentation style improvements.

Changes

  • modules/rosa-hcp-firewall-prerequisites.adoc: Changed heading from "Domains for Amazon Web Services (AWS) APIs" to "Domains for AWS APIs"
  • modules/ossm-federation-across-cluster.adoc: Changed heading from "Exposing the federation ingress on Amazon Web Services (AWS)" to "Exposing the federation ingress on AWS"

Justification

Recent PRs have been standardizing terminology by using concise "AWS" in section headings while keeping the full "Amazon Web Services (AWS)" on first mention in body text. This change follows that established pattern for consistency across the documentation.

Testing

  • Verified AsciiDoc syntax is correct
  • Changes are limited to section headings only
  • No functional impact

🤖 Generated with Claude Code

Replace verbose "Amazon Web Services (AWS)" with concise "AWS" in
section headings, following recent documentation style improvements.

Changes:
- modules/rosa-hcp-firewall-prerequisites.adoc
- modules/ossm-federation-across-cluster.adoc

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@openshift-ci openshift-ci Bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Sep 2, 2026
@openshift-ci

openshift-ci Bot commented Sep 2, 2026

Copy link
Copy Markdown

Hi @msarage-ux. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant