Merge pull request #81890 from bergerhoffer/main-417-typos

bergerhoffer · web-flow · commit e68e6b6b2699 · 2024-09-17T12:14:26.000-04:00
Typo check for main/4.17
diff --git a/applications/connecting_applications_to_services/getting-started-with-service-binding.adoc b/applications/connecting_applications_to_services/getting-started-with-service-binding.adoc
@@ -50,7 +50,7 @@ include::modules/sbo-connecting-spring-petclinic-sample-app-to-postgresql-databa
 
 [role="_additional-resources"]
 [id="additional-resources_getting-started-sbo"]
-== Additional Resources
+== Additional resources
 * xref:../../applications/connecting_applications_to_services/installing-sbo.adoc#installing-sbo[Installing Service Binding Operator].
 * xref:../../applications/creating_applications/odc-creating-applications-using-developer-perspective.adoc#odc-creating-applications-using-developer-perspective[Creating applications using the Developer perspective].
 * xref:../../operators/understanding/crds/crd-managing-resources-from-crds.adoc[Managing resources from custom resource definitions].
diff --git a/applications/connecting_applications_to_services/installing-sbo.adoc b/applications/connecting_applications_to_services/installing-sbo.adoc
@@ -25,7 +25,7 @@ endif::openshift-rosa,openshift-dedicated[]
 include::modules/op-installing-sbo-operator-using-the-web-console.adoc[leveloffset=+1]
 
 
-== Additional Resources
+== Additional resources
 
 * xref:../../applications/connecting_applications_to_services/getting-started-with-service-binding.adoc#getting-started-with-service-binding[Getting started with service binding].
 
diff --git a/cloud_experts_tutorials/cloud-experts-getting-started/cloud-experts-getting-started-what-is-rosa.adoc b/cloud_experts_tutorials/cloud-experts-getting-started/cloud-experts-getting-started-what-is-rosa.adoc
@@ -187,7 +187,7 @@ Ingress can be limited to a PrivateLink for Red{nbsp}Hat SREs and a VPN for cust
 //Watch this demo for a short preview of the cluster deployment process:
 //link:https://youtu.be/KbzUbXWs6Ck
 
-.Additional Resources
+.Additional resources
 
 * ROSA product pages:
 ** link:https://www.openshift.com/products/amazon-openshift[Red{nbsp}Hat product page]
diff --git a/cloud_experts_tutorials/cloud-experts-rosa-hcp-activation-and-account-linking-tutorial.adoc b/cloud_experts_tutorials/cloud-experts-rosa-hcp-activation-and-account-linking-tutorial.adoc
@@ -188,7 +188,7 @@ The `rosa` CLI is required for certain tasks, such as creating the account roles
 +
 image::rosa-deploy-ui-hcp-20.png[]
 
-. The next step *Accounts and roles* allows you specifying the infrastructure AWS account, into which the the ROSA cluster is deployed and where the resources are consumed and managed:
+. The next step *Accounts and roles* allows you specifying the infrastructure AWS account, into which the ROSA cluster is deployed and where the resources are consumed and managed:
 +
 .AWS infrastructure account
 +
diff --git a/contributing_to_docs/doc_guidelines.adoc b/contributing_to_docs/doc_guidelines.adoc
@@ -854,7 +854,7 @@ For more information, see "<section_name>".
 
 * Wrap the `<section_name>` string in quotation marks. The section name can be the title of a module or an assembly.
 
-* Do not state "in the Additional Resources section" or other variants. Mentioning the `<section_name>` is enough to prompt a documentation user to find the section in the same document.
+* Do not state "in the Additional resources section" or other variants. Mentioning the `<section_name>` is enough to prompt a documentation user to find the section in the same document.
 
 ==== Lead-in link sentence style for the xref attribute
 
diff --git a/modules/about-developer-perspective.adoc b/modules/about-developer-perspective.adoc
@@ -30,5 +30,5 @@ The *Developer* perspective provides workflows specific to developer use cases,
 
 You can use the *Topology* view to display applications, components, and workloads of your project. If you have no workloads in the project, the *Topology* view will show some links to create or import them. You can also use the *Quick Search* to import components directly.
 
-.Additional Resources
+.Additional resources
 See link:https://docs.openshift.com/container-platform/4.16/applications/odc-viewing-application-composition-using-topology-view.html[Viewing application composition using the Topology] view for more information on using the *Topology* view in *Developer* perspective.
diff --git a/modules/cert-manager-certificate-api-server.adoc b/modules/cert-manager-certificate-api-server.adoc
@@ -13,7 +13,7 @@
 
 .Procedure
 
-. Create an issuer. For more information, see "Configuring an issuer" in the "Additional Resources" section.
+. Create an issuer. For more information, see "Configuring an issuer" in the "Additional resources" section.
 
 . Create a certificate:
 
diff --git a/modules/cert-manager-certificate-ingress.adoc b/modules/cert-manager-certificate-ingress.adoc
@@ -13,7 +13,7 @@
 
 .Procedure
 
-. Create an issuer. For more information, see "Configuring an issuer" in the "Additional Resources" section.
+. Create an issuer. For more information, see "Configuring an issuer" in the "Additional resources" section.
 
 . Create a certificate:
 
diff --git a/modules/cert-manager-certificate-mgmt.adoc b/modules/cert-manager-certificate-mgmt.adoc
@@ -13,7 +13,7 @@
 
 .Procedure
 
-. Create an issuer. For more information, see "Configuring an issuer" in the "Additional Resources" section.
+. Create an issuer. For more information, see "Configuring an issuer" in the "Additional resources" section.
 
 . Create a certificate:
 
diff --git a/modules/cluster-logging-forwarding-separate-indices.adoc b/modules/cluster-logging-forwarding-separate-indices.adoc
@@ -69,5 +69,5 @@ spec:
 This configuration might significantly increase the number of shards on the cluster.
 ====
 
-.Additional Resources
+.Additional resources
 * link:https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/[Kubernetes Annotations]
diff --git a/modules/cluster-logging-logcli-reference.adoc b/modules/cluster-logging-logcli-reference.adoc
@@ -27,5 +27,5 @@ $ logcli --bearer-token="$(oc whoami -t)" --addr https://lokistack-dev-openshift
 $ logcli --bearer-token="$(oc whoami -t)" --addr https://lokistack-dev-openshift-logging.apps.devcluster.openshift.com/api/logs/v1/audit labels
 ----
 
-.Additional Resources
+.Additional resources
 * link:https://grafana.com/docs/loki/latest/tools/logcli/[LogCLI Documentation]
diff --git a/modules/cnf-configuring-single-numa-policy.adoc b/modules/cnf-configuring-single-numa-policy.adoc
@@ -13,4 +13,4 @@ The NUMA Resources Operator requires a single NUMA node policy to be configured
 The preferred way to configure a single NUMA node policy is to apply a performance profile. You can use the Performance Profile Creator (PPC) tool to create the performance profile. If a performance profile is created on the cluster, it automatically creates other tuning components like `KubeletConfig` and the `tuned` profile.
 ====
 
-For more information about creating a performance profile, see "About the Performance Profile Creator" in the "Additional Resources" section.
+For more information about creating a performance profile, see "About the Performance Profile Creator" in the "Additional resources" section.
diff --git a/modules/cnf-topology-aware-lifecycle-manager-preparing-for-updates.adoc b/modules/cnf-topology-aware-lifecycle-manager-preparing-for-updates.adoc
@@ -12,7 +12,7 @@ You must mirror both the platform image and Operator images that you want to upd
 
 * For platform updates, you must perform the following steps:
 +
-. Mirror the desired {product-title} image repository. Ensure that the desired platform image is mirrored by following the "Mirroring the {product-title} image repository" procedure linked in the Additional Resources. Save the contents of the `imageContentSources` section in the `imageContentSources.yaml` file:
+. Mirror the desired {product-title} image repository. Ensure that the desired platform image is mirrored by following the "Mirroring the {product-title} image repository" procedure linked in the Additional resources. Save the contents of the `imageContentSources` section in the `imageContentSources.yaml` file:
 +
 .Example output
 [source,yaml]
diff --git a/modules/creating-nfd-cr-cli-disconnected.adoc b/modules/creating-nfd-cr-cli-disconnected.adoc
@@ -13,7 +13,7 @@ As a cluster administrator, you can create a `NodeFeatureDiscovery` CR instance
 * You have access to an {product-title} cluster
 * You installed the {oc-first}.
 * You logged in as a user with `cluster-admin` privileges.
-* You installed the the NFD Operator.
+* You installed the NFD Operator.
 * You have access to a mirror registry with the required images.
 * You installed the `skopeo` CLI tool.
 
diff --git a/modules/creating-nfd-cr-cli.adoc b/modules/creating-nfd-cr-cli.adoc
@@ -20,7 +20,7 @@ The following example shows the use of `-rhel9` to acquire the correct image.
 * You have access to an {product-title} cluster
 * You installed the {oc-first}.
 * You logged in as a user with `cluster-admin` privileges.
-* You installed the the NFD Operator.
+* You installed the NFD Operator.
 
 .Procedure
 
diff --git a/modules/creating-nfd-cr-web-console.adoc b/modules/creating-nfd-cr-web-console.adoc
@@ -12,7 +12,7 @@ As a cluster administrator, you can create a `NodeFeatureDiscovery` CR by using
 
 * You have access to an {product-title} cluster
 * You logged in as a user with `cluster-admin` privileges.
-* You installed the the NFD Operator.
+* You installed the NFD Operator.
 
 .Procedure
 
diff --git a/modules/creating-scaling-machine-sets-compute-nodes-networking.adoc b/modules/creating-scaling-machine-sets-compute-nodes-networking.adoc
@@ -52,7 +52,7 @@ spec:
 # ...
 ----
 
-. To mange the `BareMetalHost` object within the `openshift-machine-api` namespace of your cluster, change to the namespace by entering the following command:
+. To manage the `BareMetalHost` object within the `openshift-machine-api` namespace of your cluster, change to the namespace by entering the following command:
 +
 [source,terminal]
 ----
diff --git a/modules/gitops-about-argo-rollout-manager-custom-resources-and-spec.adoc b/modules/gitops-about-argo-rollout-manager-custom-resources-and-spec.adoc
@@ -34,5 +34,5 @@ spec: {}
 
 With the Argo Rollouts controller resource, you can manage the progressive application delivery in your namespace. The Argo Rollouts controller resource monitors the cluster for events, and reacts whenever there is a change in any resource related to Argo Rollouts. The controller reads all the rollout details and brings the cluster to the same state as described in the rollout definition.
 
-.Additional Resources
+.Additional resources
 link:https://argo-rollouts-manager.readthedocs.io/en/latest/crd_reference/[`RolloutManager` Custom Resource specification]
diff --git a/modules/install-sno-ibm-z-kvm.adoc b/modules/install-sno-ibm-z-kvm.adoc
@@ -170,4 +170,4 @@ $ virt-install \
 <1> For the `--location` parameter, specify the location of the kernel/initrd on the HTTP or HTTPS server.
 <2> Specify the location of the `bootstrap.ign` config file. Only HTTP and HTTPS protocols are supported.
 <3> For the `coreos.live.rootfs_url=` artifact, specify the matching `rootfs` artifact for the `kernel` and `initramfs` you are booting. Only HTTP and HTTPS protocols are supported.
-<4> For the `ip=` parameter, assign the IP address manually as described in "Installing a cluster with with {op-system-base} KVM on {ibm-z-name} and {ibm-linuxone-name}".
+<4> For the `ip=` parameter, assign the IP address manually as described in "Installing a cluster with {op-system-base} KVM on {ibm-z-name} and {ibm-linuxone-name}".
diff --git a/modules/installing-ocp-agent-ibm-z-zvm.adoc b/modules/installing-ocp-agent-ibm-z-zvm.adoc
@@ -7,7 +7,7 @@
 = Adding {ibm-z-title} agents with z/VM
 
 Use the following procedure to manually add {ibm-z-name} agents with z/VM.
-Only use this procedure for {ibm-z-name} clusters with with z/VM.
+Only use this procedure for {ibm-z-name} clusters with z/VM.
 
 .Procedure
 
@@ -56,4 +56,4 @@ You can use the `CP PUNCH` command or, if you use Linux, the `vmur` command, to
 $ ipl c
 ----
 +
-For more information, see link:https://www.ibm.com/docs/en/zvm/latest?topic=commands-ipl[IPL] ({ibm-title} Documentation).
+For more information, see link:https://www.ibm.com/docs/en/zvm/latest?topic=commands-ipl[IPL] ({ibm-title} Documentation).
diff --git a/modules/logging-loki-cli-install.adoc b/modules/logging-loki-cli-install.adoc
@@ -226,7 +226,7 @@ spec:
 $ oc apply -f <filename>.yaml
 ----
 
-. Verify the installation by by running the following command:
+. Verify the installation by running the following command:
 +
 [source,terminal]
 ----
diff --git a/modules/network-observability-RTT-overview.adoc b/modules/network-observability-RTT-overview.adoc
@@ -25,4 +25,4 @@ Other RTT panels can be added in *Manage panels*:
 * Top X maximum TCP Round Trip Time with overall
 * Top X 99th percentile TCP Round Trip Time with overall
 
-See the _Additional Resources_ in this section for more information about enabling and working with this view.
+See the _Additional resources_ in this section for more information about enabling and working with this view.
diff --git a/modules/network-observability-dns-overview.adoc b/modules/network-observability-dns-overview.adoc
@@ -27,4 +27,4 @@ Other DNS tracking panels can be added in *Manage panels*:
 
 This feature is supported for IPv4 and IPv6 UDP and TCP protocols.
 
-See the _Additional Resources_ in this section for more information about enabling and working with this view.
+See the _Additional resources_ in this section for more information about enabling and working with this view.
diff --git a/modules/network-observability-flowmetrics-charts.adoc b/modules/network-observability-flowmetrics-charts.adoc
@@ -97,7 +97,7 @@ metadata:
 
 This example uses the `histogram_quantile` function to show `p50` and `p99`.
 
-You can show averages of histograms by dividing the metric, `$METRIC_sum`, by the metric ,`$METRIC_count`, which are automatically generated when you create a histogram. With the preceding example, the Prometheus query to do this is as follows:
+You can show averages of histograms by dividing the metric, `$METRIC_sum`, by the metric, `$METRIC_count`, which are automatically generated when you create a histogram. With the preceding example, the Prometheus query to do this is as follows:
 
 [source,yaml]
 ----
diff --git a/modules/network-observability-pktdrop-overview.adoc b/modules/network-observability-pktdrop-overview.adoc
@@ -37,4 +37,4 @@ Examples of OVS drops reasons are as follows:
 * `OVS_DROP_LAST_ACTION`: OVS packets dropped due to an implicit drop action, for example due to a configured network policy.
 * `OVS_DROP_IP_TTL`: OVS packets dropped due to an expired IP TTL.
 
-See the _Additional Resources_ of this section for more information about enabling and working with packet drop tracking.
+See the _Additional resources_ of this section for more information about enabling and working with packet drop tracking.
diff --git a/modules/nw-metallb-software-components.adoc b/modules/nw-metallb-software-components.adoc
@@ -11,7 +11,7 @@ When the Operator starts an instance of MetalLB, it starts a `controller` deploy
 
 [NOTE]
 ====
-You can configure deployment specifications in the MetalLB custom resource to manage how `controller` and `speaker` pods deploy and run in your cluster. For more information about these deployment specifications, see the _Additional Resources_ section.
+You can configure deployment specifications in the MetalLB custom resource to manage how `controller` and `speaker` pods deploy and run in your cluster. For more information about these deployment specifications, see the _Additional resources_ section.
 ====
 
 `controller`::
diff --git a/modules/nw-sriov-configuring-operator.adoc b/modules/nw-sriov-configuring-operator.adoc
@@ -308,7 +308,7 @@ After performing the following procedure to disable draining workloads, you must
 
 .Procedure
 
-- To set the `disableDrain` field to `true` and the `configDaemonNodeSelector` field to `node-role.kubernetes.io/master: ""` , enter the following command:
+- To set the `disableDrain` field to `true` and the `configDaemonNodeSelector` field to `node-role.kubernetes.io/master: ""`, enter the following command:
 +
 [source,terminal]
 ----
diff --git a/modules/oadp-release-notes-1-3-0.adoc b/modules/oadp-release-notes-1-3-0.adoc
@@ -56,7 +56,7 @@ During interoperability testing, {product-title} 4.14 had the pod Security mode
 
 .Possible pod volume backup failure if Velero is installed in several namespaces
 
-There was a regresssion in Pod Volume Backup (PVB) functionality when Velero was installed in several namespaces. The PVB controller was not properly limiting itself to PVBs in its own namespace.
+There was a regression in Pod Volume Backup (PVB) functionality when Velero was installed in several namespaces. The PVB controller was not properly limiting itself to PVBs in its own namespace.
 link:https://issues.redhat.com/browse/OADP-2308[OADP-2308]
 
 .OADP Velero plugins returning "received EOF, stopping recv loop" message
diff --git a/modules/odc-accessing-perspectives.adoc b/modules/odc-accessing-perspectives.adoc
@@ -12,7 +12,7 @@ You can access the *Administrator* and *Developer* perspective from the web cons
 .Prerequisites
 To access a perspective, ensure that you have logged in to the web console. Your default perspective is automatically determined by the permission of the users. The *Administrator* perspective is selected for users with access to all projects, while the *Developer* perspective is selected for users with limited access to their own projects
 
-.Additional Resources
+.Additional resources
 See link:https://docs.openshift.com/container-platform/4.16/web_console/adding-user-preferences.html[Adding User Preferences] for more information on changing perspectives.
 
 
diff --git a/modules/persistent-storage-csi-vsphere-change-max-snapshot.adoc b/modules/persistent-storage-csi-vsphere-change-max-snapshot.adoc
@@ -11,7 +11,7 @@ The default maximum number of snapshots per volume in vSphere Container Storage
 
 However, be aware that increasing the snapshot maximum involves a performance trade off, so for better performance use only 2 to 3 snapshots per volume.
 
-For more VMware snapshot performance recommendations, see *_Additional Resources_*.
+For more VMware snapshot performance recommendations, see *_Additional resources_*.
 
 .Prerequisites
 
diff --git a/modules/rosa-hcp-upgrading-cli-control-plane.adoc b/modules/rosa-hcp-upgrading-cli-control-plane.adoc
@@ -79,7 +79,7 @@ $ rosa upgrade cluster -c <cluster_name_or_id> --control-plane --version <versio
 +
 Your hosted control plane is scheduled for an immediate upgrade.
 
-** To schedule an upgrade to the the specified version at a future date, run the following command:
+** To schedule an upgrade to the specified version at a future date, run the following command:
 +
 [source,terminal]
 ----
@@ -91,4 +91,4 @@ Your hosted control plane is scheduled for an upgrade at the specified time in C
 ifeval::["{context}" != "rosa-hcp-upgrading-whole-cluster"]
 .Troubleshooting
 * Sometimes a scheduled upgrade does not initiate. See link:https://access.redhat.com/solutions/6648291[Upgrade maintenance canceled] for more information.
-endif::[]
+endif::[]
diff --git a/modules/understanding-agent-install.adoc b/modules/understanding-agent-install.adoc
@@ -11,7 +11,7 @@ The Agent-based installation comprises a bootable ISO that contains the Assisted
 
 [NOTE]
 ====
-Currently, ISO boot support on {ibm-z-name} (`s390x``) is available only for {op-system-base-full} KVM, which provides the flexibility to choose either PXE or ISO-based installation. For installations with z/VM and Logical Partition (LPAR), only PXE boot is supported.
+Currently, ISO boot support on {ibm-z-name} (`s390x`) is available only for {op-system-base-full} KVM, which provides the flexibility to choose either PXE or ISO-based installation. For installations with z/VM and Logical Partition (LPAR), only PXE boot is supported.
 ====
 
 The `openshift-install agent create image` subcommand generates an ephemeral ISO based on the inputs that you provide. You can choose to provide inputs through the following manifests:
@@ -74,4 +74,4 @@ For platform `none`:
 * The `none` option requires the provision of DNS name resolution and load balancing infrastructure in your cluster. See _Requirements for a cluster using the platform "none" option_ in the "Additional resources" section for more information.
 
 * Review the information in the link:https://access.redhat.com/articles/4207611[guidelines for deploying {product-title} on non-tested platforms] before you attempt to install an {product-title} cluster in virtualized or cloud environments.
-====
+====
diff --git a/networking/configuring-cluster-wide-proxy.adoc b/networking/configuring-cluster-wide-proxy.adoc
@@ -30,7 +30,7 @@ If you use a cluster-wide proxy, you are responsible for maintaining the availab
 include::modules/cluster-wide-proxy-preqs.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
-.Additional Resources
+.Additional resources
 
 ifdef::openshift-rosa[]
 * For the installation prerequisites for ROSA clusters that use the AWS Security Token Service (STS), see xref:../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-sts-aws-prerequisites[AWS prerequisites for ROSA with STS].
@@ -58,7 +58,7 @@ include::modules/configuring-a-proxy-during-installation-cli.adoc[leveloffset=+2
 endif::openshift-rosa[]
 
 [role="_additional-resources"]
-.Additional Resources
+.Additional resources
 
 ifdef::openshift-rosa[]
 * xref:../rosa_install_access_delete_clusters/rosa-sts-creating-a-cluster-with-customizations.adoc#rosa-sts-creating-cluster-customizations-ocm_rosa-sts-creating-a-cluster-with-customizations[Creating a cluster with customizations by using OpenShift Cluster Manager]
diff --git a/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc b/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc
@@ -75,7 +75,7 @@ include::modules/nw-ingress-sharding-route-configuration.adoc[leveloffset=+2]
 
 [discrete]
 [id="additional-resources_ingress-sharding"]
-=== Additional Resources
+=== Additional resources
 
 * xref:../../scalability_and_performance/optimization/routing-optimization.adoc#baseline-router-performance_routing-optimization[Baseline Ingress Controller (router) performance]
 
diff --git a/observability/logging/log_storage/cluster-logging-loki.adoc b/observability/logging/log_storage/cluster-logging-loki.adoc
@@ -52,7 +52,7 @@ include::modules/logging-loki-memberlist-ip.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 [id="additional-resources_cluster-logging-loki"]
-== Additional Resources
+== Additional resources
 * link:https://grafana.com/docs/loki/latest/get-started/components/[Loki components documentation]
 * link:https://grafana.com/docs/loki/latest/logql/[Loki Query Language (LogQL) documentation]
 * link:https://loki-operator.dev/docs/howto_connect_grafana.md/[Grafana Dashboard documentation]
diff --git a/osd_architecture/osd_policy/osd-service-definition.adoc b/osd_architecture/osd_policy/osd-service-definition.adoc
@@ -13,12 +13,12 @@ include::modules/sdpolicy-am-cluster-self-service.adoc[leveloffset=+2]
 include::modules/sdpolicy-am-cloud-providers.adoc[leveloffset=+2]
 include::modules/sdpolicy-am-compute.adoc[leveloffset=+2]
 include::snippets/pid-limits.adoc[]
-.Additional Resources
+.Additional resources
 * xref:../../osd_architecture/osd_policy/osd-service-definition.adoc#sdpolicy-red-hat-operator_osd-service-definition[Red Hat Operator Support]
 
 include::modules/sdpolicy-am-aws-compute-types-ccs.adoc[leveloffset=+2]
 [role="_additional-resources-instance-types"]
-.Additional Resources
+.Additional resources
 
 * link:https://aws.amazon.com/ec2/instance-types[AWS Instance Types]
 
diff --git a/rosa_architecture/rosa_policy_service_definition/rosa-hcp-instance-types.adoc b/rosa_architecture/rosa_policy_service_definition/rosa-hcp-instance-types.adoc
@@ -17,6 +17,6 @@ include::modules/rosa-sdpolicy-am-aws-compute-types.adoc[leveloffset=+1]
 include::modules/rosa-sdpolicy-am-aws-compute-types-graviton.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
-.Additional Resources
+.Additional resources
 
 * link:https://aws.amazon.com/ec2/instance-types[AWS Instance Types]
diff --git a/rosa_architecture/rosa_policy_service_definition/rosa-hcp-service-definition.adoc b/rosa_architecture/rosa_policy_service_definition/rosa-hcp-service-definition.adoc
diff --git a/rosa_architecture/rosa_policy_service_definition/rosa-instance-types.adoc b/rosa_architecture/rosa_policy_service_definition/rosa-instance-types.adoc
diff --git a/rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc b/rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc
diff --git a/windows_containers/enabling-windows-container-workloads.adoc b/windows_containers/enabling-windows-container-workloads.adoc

Original file line number	Diff line number	Diff line change
@@ -188,7 +188,7 @@ The `rosa` CLI is required for certain tasks, such as creating the account roles
`188`	`188`	`+`
`189`	`189`	`image::rosa-deploy-ui-hcp-20.png[]`
`190`	`190`
`191`		`-. The next step Accounts and roles allows you specifying the infrastructure AWS account, into which the the ROSA cluster is deployed and where the resources are consumed and managed:`
	`191`	`+. The next step Accounts and roles allows you specifying the infrastructure AWS account, into which the ROSA cluster is deployed and where the resources are consumed and managed:`
`192`	`192`	`+`
`193`	`193`	`.AWS infrastructure account`
`194`	`194`	`+`