From d84eaccc0531a1ee22cfe81df9c38c2dd8b46b4e Mon Sep 17 00:00:00 2001 From: Janelle Neczypor Date: Mon, 17 Aug 2026 13:22:01 -0700 Subject: [PATCH] OSDOCS-21003: Spelling errors --- modules/albo-validate-install.adoc | 2 +- modules/configuring-a-proxy-during-installation-cli.adoc | 2 +- modules/nw-networkpolicy-create-ocm.adoc | 2 +- modules/removing-cluster-wide-proxy-intro.adoc | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/modules/albo-validate-install.adoc b/modules/albo-validate-install.adoc index 21eec851e2a..2c2e72f68f6 100644 --- a/modules/albo-validate-install.adoc +++ b/modules/albo-validate-install.adoc @@ -122,7 +122,7 @@ spec: EOF ---- + -The `service.beta.kubernetes.io/aws-load-balancer-type` annotation is immutable for existing services. To change the load balancer type, you must recreate the service. +The `service.beta.kubernetes.io/aws-load-balancer-type` annotation is immutable for existing services. To change the load balancer type, you must re-create the service. . Test access to the NLB endpoint for the application: + diff --git a/modules/configuring-a-proxy-during-installation-cli.adoc b/modules/configuring-a-proxy-during-installation-cli.adoc index 59e8ec42bf4..ab14efcdfb8 100644 --- a/modules/configuring-a-proxy-during-installation-cli.adoc +++ b/modules/configuring-a-proxy-during-installation-cli.adoc @@ -40,7 +40,7 @@ where: ** The `additional-trust-bundle-file`, `http-proxy`, and `https-proxy` arguments are all optional. ** The `additional-trust-bundle-file` argument is a file path pointing to a bundle of PEM-encoded X.509 certificates, which are all concatenated together. The additional-trust-bundle-file argument is required for users who use a TLS-inspecting proxy unless the identity certificate for the proxy is signed by an authority from the {op-system-first} trust bundle. This applies regardless of whether the proxy is transparent or requires explicit configuration using the http-proxy and https-proxy arguments. ** The `http-proxy` and `https-proxy` arguments must point to a valid URL. -** A comma-separated lis of destination domain names, IP addresses, or network CIDRs to exclude proxying. +** A comma-separated list of destination domain names, IP addresses, or network CIDRs to exclude proxying. + ** Preface a domain with `.` to match subdomains only. For example, `.y.com` matches `x.y.com`, but not `y.com`. Use `*` to bypass proxy for all destinations. ** If you scale up workers that are not included in the network defined by the `networking.machineNetwork[].cidr` field from the installation configuration, you must add them to this list to prevent connection issues. diff --git a/modules/nw-networkpolicy-create-ocm.adoc b/modules/nw-networkpolicy-create-ocm.adoc index fb82611dbf2..980f3c4fcec 100644 --- a/modules/nw-networkpolicy-create-ocm.adoc +++ b/modules/nw-networkpolicy-create-ocm.adoc @@ -51,7 +51,7 @@ To define granular rules describing the ingress or egress network traffic allowe . Add egress rules to your network policy: -.. Select *Add egress rule* to configure a new rule. This action creates a new *Egress rule* row with an *Add allowed destination*"* drop-down menu where you specify how to limit outbound traffic. The drop-down menu offers three options to limit your egress traffic: +.. Select *Add egress rule* to configure a new rule. This action creates a new *Egress rule* row with an *Add allowed destination* drop-down menu where you specify how to limit outbound traffic. The drop-down menu offers three options to limit your egress traffic: + *** *Allow pods from the same namespace* limits outbound traffic to pods within the same namespace. You can specify the pods in a namespace, but leaving this option blank allows all of the traffic from pods in the namespace. diff --git a/modules/removing-cluster-wide-proxy-intro.adoc b/modules/removing-cluster-wide-proxy-intro.adoc index bf67a2e2ccf..23e7458fa22 100644 --- a/modules/removing-cluster-wide-proxy-intro.adoc +++ b/modules/removing-cluster-wide-proxy-intro.adoc @@ -7,4 +7,4 @@ = Removing a cluster-wide proxy [role="_abstract"] -You can remove your cluster-wide proxy by using the ROSA CLI. After removing the cluster, you should also remove any trust bundles that you added to the cluster. +You can remove your cluster-wide proxy by using the ROSA CLI. After removing the proxy, you should also remove any trust bundles that you added to the cluster.