openshift · otikhomi · Jun 18, 2026 · ocpdocs-vale-bot · Jun 22, 2026 · ocpdocs-vale-bot
diff --git a/cloud_experts_tutorials/cloud-experts-aws-load-balancer-operator.adoc b/cloud_experts_tutorials/cloud-experts-aws-load-balancer-operator.adoc
@@ -11,7 +11,7 @@ include::snippets/snip-mobb-support-statement.adoc[leveloffset=+1]
 
 [TIP]
 ====
-Load Balancers created by the AWS Load Balancer Operator cannot be used for xref:../networking/ingress_load_balancing/routes/nw-configuring-routes.adoc#route-configuration[OpenShift Routes], and should only be used for individual services or ingress resources that do not need the full layer 7 capabilities of an OpenShift Route.
+Load Balancers created by the AWS Load Balancer Operator cannot be used for xref:../networking/ingress_load_balancing/routes/nw-configuring-routes.adoc#nw-configuring-routes[{OCP-short} Routes], and should only be used for individual services or ingress resources that do not need the full layer 7 capabilities of an {OCP-short} Route.
 ====
 
 [role="_abstract"]
@@ -37,7 +37,7 @@ The link:https://github.com/openshift/aws-load-balancer-operator[AWS Load Balanc
 
 [NOTE]
 ====
-AWS ALBs require a multi-AZ cluster, as well as three public subnets split across three AZs in the same VPC as the cluster. This makes ALBs unsuitable for many PrivateLink clusters. AWS NLBs do not have this restriction.
+AWS ALBs require a multi-availability zone (AZ) cluster, as well as three public subnets split across three AZs in the same (Virtual Private Cloud) VPC as the cluster. This makes ALBs unsuitable for many PrivateLink clusters. AWS NLBs do not have this restriction.
 ====
 
 ifndef::openshift-rosa-hcp[]
@@ -46,9 +46,9 @@ endif::openshift-rosa-hcp[]
 ifdef::openshift-rosa-hcp[]
 * xref:../rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc#rosa-hcp-sts-creating-a-cluster-quickly[A multi-AZ {product-title} cluster]
 endif::openshift-rosa-hcp[]
-* BYO VPC cluster
+* Bring Your Own (BYO) VPC cluster
 * AWS CLI
-* OC CLI
+* {oc-first}
 
 include::modules/cloud-experts-aws-load-balancer-operator-environment.adoc[leveloffset=+2]
 include::modules/cloud-experts-aws-load-balancer-operator-aws-vpc-subnets.adoc[leveloffset=+2]

diff --git a/cloud_experts_tutorials/cloud-experts-aws-secret-manager.adoc b/cloud_experts_tutorials/cloud-experts-aws-secret-manager.adoc
@@ -1,6 +1,6 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="cloud-experts-aws-secret-manager"]
-= Tutorial: Using AWS Secrets Manager CSI on {product-title} with STS
+= Tutorial: Use AWS Secrets Manager CSI on {product-title} with STS
 
 include::_attributes/attributes-openshift-dedicated.adoc[]
 :context: cloud-experts-aws-secret-manager

diff --git a/cloud_experts_tutorials/cloud-experts-consistent-egress-ip.adoc b/cloud_experts_tutorials/cloud-experts-consistent-egress-ip.adoc
@@ -1,6 +1,6 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="cloud-experts-consistent-egress-ip"]
-= Tutorial: Assigning a consistent egress IP for external traffic
+= Tutorial: Assign a consistent egress IP for external traffic
 
 include::_attributes/attributes-openshift-dedicated.adoc[]
 include::_attributes/common-attributes.adoc[]
@@ -13,19 +13,17 @@ This tutorial teaches you how to configure a set of predictable IP addresses for
 
 By default, {product-title} uses the OVN-Kubernetes container network interface (CNI) to assign random IP addresses from a pool. This can make configuring security lockdowns unpredictable or open.
 
-ifndef::openshift-rosa-hcp[]
+// Assembly configuring-egress-ips-ovn is commented out of the ROSA HCP topic map (as of June 2026).
+ifdef::openshift-rosa[]
 See xref:../networking/ovn_kubernetes_network_provider/configuring-egress-ips-ovn.adoc#configuring-egress-ips-ovn[Configuring an egress IP address] for more information.
-endif::openshift-rosa-hcp[]
-ifdef::openshift-rosa-hcp[]
-See link:https://docs.openshift.com/rosa/networking/ovn_kubernetes_network_provider/configuring-egress-ips-ovn.html[Configuring an egress IP address] for more information.
-endif::openshift-rosa-hcp[]
+endif::openshift-rosa[]
 
 == Prerequisites
 
 * A {product-title} cluster deployed with OVN-Kubernetes
-* The xref:../cli_reference/openshift_cli/getting-started-cli.adoc#cli-getting-started[OpenShift CLI] (`oc`)
-* The xref:../cli_reference/rosa_cli/rosa-get-started-cli.adoc#rosa-get-started-cli[ROSA CLI] (`rosa`)
-* link:https://stedolan.github.io/jq/[`jq`]
+* The xref:../cli_reference/openshift_cli/getting-started-cli.adoc#cli-getting-started[{oc-first}]
+* The xref:../cli_reference/rosa_cli/rosa-get-started-cli.adoc#rosa-get-started-cli[{rosa-cli-first}]
+* link:https://jqlang.org/[`jq`]
 
 include::modules/egress-ip-env-variables.adoc[leveloffset=+1]
 include::modules/egress-ip-capacity.adoc[leveloffset=+1]

diff --git a/cloud_experts_tutorials/cloud-experts-custom-dns-resolver.adoc b/cloud_experts_tutorials/cloud-experts-custom-dns-resolver.adoc
@@ -1,16 +1,16 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="cloud-experts-custom-dns-resolver"]
-= Tutorial: Deploying {product-title} with a Custom DNS Resolver
+= Tutorial: Deploy {product-title} with a custom DNS resolver
 
 include::_attributes/attributes-openshift-dedicated.adoc[]
 :context: cloud-experts-custom-dns-resolver
 
 toc::[]
 
 [role="_abstract"]
-A link:https://docs.aws.amazon.com/vpc/latest/userguide/DHCPOptionSet.html[custom DHCP option set] enables you to customize your VPC with your own DNS server, domain name, and more. {product-title} clusters support using custom DHCP option sets. By default, {product-title} clusters require setting the "domain name servers" option to `AmazonProvidedDNS` to ensure successful cluster creation and operation. Customers who want to use custom DNS servers for DNS resolution must do additional configuration to ensure successful {product-title} cluster creation and operation. 
+A link:https://docs.aws.amazon.com/vpc/latest/userguide/DHCPOptionSet.html[custom Dynamic Host Configuration Protocol (DHCP) option set] enables you to customize your Virtual Private Cloud (VPC) with your own Domain Name System (DNS) server, domain name, and more. {product-title} clusters support using custom DHCP option sets. By default, {product-title} clusters require setting the "domain name servers" option to `AmazonProvidedDNS` to ensure successful cluster creation and operation. Customers who want to use custom DNS servers for DNS resolution must do additional configuration to ensure successful {product-title} cluster creation and operation.
 
-In this tutorial, we will configure our DNS server to forward DNS lookups for specific DNS zones (further detailed below) to an link:https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html[Amazon Route 53 Inbound Resolver]. 
+In this tutorial, we will configure our DNS server to forward DNS lookups for specific DNS zones (further detailed below) to an link:https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html[Amazon Route 53 Inbound Resolver].
 
 [NOTE]
 ====
@@ -19,7 +19,7 @@ This tutorial uses the open-source BIND DNS server (`named`) to demonstrate the
 
 == Prerequisites
 
-* ROSA CLI (`rosa`)
+* {rosa-cli-first}
 * AWS CLI (`aws`)
 ifdef::openshift-rosa[]
 * A manually created AWS VPC

diff --git a/cloud_experts_tutorials/cloud-experts-deploy-api-data-protection.adoc b/cloud_experts_tutorials/cloud-experts-deploy-api-data-protection.adoc
@@ -1,16 +1,17 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="cloud-experts-deploy-api-data-protection"]
-= Tutorial: Deploying OpenShift API for Data Protection on a {product-title} cluster
+= Tutorial: Deploy {oadp-full} on a {product-title} cluster
 
 include::_attributes/attributes-openshift-dedicated.adoc[]
+include::_attributes/common-attributes.adoc
 :context: cloud-experts-deploy-api-data-protection
 
 toc::[]
 
 include::snippets/snip-mobb-support-statement.adoc[leveloffset=+1]
 
 [role="_abstract"]
-The following tutorial shows you how to deploy the OpenShift API for data protection on your {product-title} cluster.
+The following tutorial shows you how to deploy the {oadp-full} on your {product-title} cluster.
 
 [id="cloud-experts-deploy-api-data-protection-prerequisites_{context}"]
 == Prerequisites

diff --git a/cloud_experts_tutorials/cloud-experts-entra-id-idp.adoc b/cloud_experts_tutorials/cloud-experts-entra-id-idp.adoc
@@ -1,6 +1,6 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="cloud-experts-entra-id-idp"]
-= Tutorial: Configuring Microsoft Entra ID (formerly Azure Active Directory) as an identity provider
+= Tutorial: Configure Microsoft Entra ID (formerly Azure Active Directory) as an identity provider
 
 include::_attributes/attributes-openshift-dedicated.adoc[]
 :context: cloud-experts-entra-id-idp

diff --git a/...s_tutorials/cloud-experts-rosa-hcp-activation-and-account-linking-tutorial.adoc b/...s_tutorials/cloud-experts-rosa-hcp-activation-and-account-linking-tutorial.adoc
@@ -1,6 +1,6 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="cloud-experts-activation-account-linking"]
-= Tutorial: {product-title} activation and account linking
+= Tutorial: Activate {product-title} and link your account
 
 include::_attributes/attributes-openshift-dedicated.adoc[]
 :context: cloud-experts-activation-account-linking

diff --git a/...tutorials/cloud-experts-rosa-with-hcp-private-offer-acceptance-and-sharing.adoc b/...tutorials/cloud-experts-rosa-with-hcp-private-offer-acceptance-and-sharing.adoc
@@ -1,6 +1,6 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="cloud-experts-rosa-with-hcp-private-offer-acceptance-and-sharing"]
-= Tutorial: {product-title} private offer acceptance and sharing
+= Tutorial: Accept and share a {product-title} private offer
 
 include::_attributes/attributes-openshift-dedicated.adoc[]
 :context: cloud-experts-rosa-with-hcp-private-offer-acceptance-and-sharing

diff --git a/cloud_experts_tutorials/cloud-experts-using-alb-and-waf.adoc b/cloud_experts_tutorials/cloud-experts-using-alb-and-waf.adoc
@@ -1,6 +1,6 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="cloud-experts-using-alb-and-waf"]
-= Tutorial: Using AWS WAF and AWS ALBs to protect {product-title} workloads
+= Tutorial: Use AWS WAF and AWS ALBs to protect {product-title} workloads
 
 include::_attributes/attributes-openshift-dedicated.adoc[]
 :context: cloud-experts-using-alb-and-waf
@@ -27,7 +27,7 @@ It is recommended that you use the more flexible xref:../cloud_experts_tutorials
 AWS ALBs require at least two _public_ subnets across AZs, link:https://docs.aws.amazon.com/elasticloadbalancing/latest/application/application-load-balancers.html#availability-zones[per the AWS documentation]. For this reason, only multiple AZ {product-title} clusters can be used with ALBs.
 ====
 +
-* You have access to the OpenShift CLI (`oc`).
+* You have access to the {oc-first}.
 * You have access to the AWS CLI (`aws`).
 
 include::modules/cloud-experts-using-alb-and-waf-environment-setup.adoc[leveloffset=+2]
@@ -40,4 +40,4 @@ include::modules/cloud-experts-using-alb-and-waf-configure-aws-waf.adoc[leveloff
 [id="additional-resources_{context}"]
 == Additional resources
 
-* link:https://youtu.be/-HorEsl2ho4[Adding Extra Security with AWS WAF, CloudFront and ROSA | Amazon Web Services on YouTube]
+* link:https://youtu.be/-HorEsl2ho4[Adding Extra Security with AWS WAF, CloudFront and {product-title} | Amazon Web Services on YouTube]
diff --git a/cloud_experts_tutorials/cloud-experts-using-aws-ack.adoc b/cloud_experts_tutorials/cloud-experts-using-aws-ack.adoc
@@ -1,6 +1,6 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="cloud-experts-using-aws-ack"]
-= Tutorial: Using AWS Controllers for Kubernetes on {product-title}
+= Tutorial: Use AWS Controllers for Kubernetes on {product-title}
 
 include::_attributes/attributes-openshift-dedicated.adoc[]
 :context: cloud-experts-using-aws-ack
@@ -19,7 +19,7 @@ Use this tutorial to deploy the ACK S3 Operator. You can also adapt it for any o
 
 * A {product-title} cluster
 * A user account with `cluster-admin` privileges
-* The OpenShift CLI (`oc`)
+* The {oc-first}
 * The Amazon Web Services (AWS) CLI (`aws`)
 
 include::modules/cloud-experts-using-aws-ack-environment-setup.adoc[leveloffset=+1]

diff --git a/cloud_experts_tutorials/cloud-experts-using-cloudfront-and-waf.adoc b/cloud_experts_tutorials/cloud-experts-using-cloudfront-and-waf.adoc
@@ -1,16 +1,16 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="cloud-experts-using-cloudfront-and-waf"]
-= Tutorial: Using AWS WAF and Amazon CloudFront to protect {product-title} workloads
+= Tutorial: Use AWS WAF and Amazon CloudFront to protect {product-title} workloads
 
 include::_attributes/attributes-openshift-dedicated.adoc[]
 :context: cloud-experts-using-cloudfront-and-waf
 
 toc::[]
 
 [role="_abstract"]
-AWS WAF is a web application firewall that lets you monitor the HTTP and HTTPS requests that are forwarded to your protected web application resources.
+You can use AWS Web Application Firewall (WAF) to monitor HTTP and HTTPS requests that are forwarded to your protected web application resources.
 
-You can use an Amazon CloudFront to add a Web Application Firewall (WAF) to your {product-title} workloads. Using an external solution protects {product-title} resources from experiencing denial of service due to handling the WAF.
+You can use an Amazon CloudFront to add a WAF to your {product-title} workloads. Using an external solution protects {product-title} resources from experiencing denial of service due to handling the WAF.
 
 [NOTE]
 ====
@@ -20,7 +20,7 @@ WAFv1, WAF classic, is no longer supported. Use WAFv2.
 == Prerequisites
 
 * A {product-title} cluster.
-* You have access to the OpenShift CLI (`oc`).
+* You have access to the {oc-first}.
 * You have access to the AWS CLI (`aws`).
 
 include::modules/cloud-experts-using-cloudfront-and-waf-setup-environ.adoc[leveloffset=+1]
@@ -34,4 +34,4 @@ include::modules/cloud-experts-using-cloudfront-and-waf-test-waf.adoc[leveloffse
 [id="additional-resources_{context}"]
 == Additional resources
 
-* link:https://youtu.be/-HorEsl2ho4[Adding Extra Security with AWS WAF, CloudFront and ROSA | Amazon Web Services on YouTube]
+* link:https://youtu.be/-HorEsl2ho4[Adding Extra Security with AWS WAF, CloudFront and {product-title} | Amazon Web Services on YouTube]
diff --git a/modules/accepting-private-offer.adoc b/modules/accepting-private-offer.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="accepting-private-offer_{context}"]
-= Accepting a private offer
+= Accept a private offer
 
 [role="_abstract"]
 You can accept private offers from other team members within your Red{nbsp}Hat organization account.
@@ -27,7 +27,7 @@ image::rosa-regular-private-offer.png[]
 [caption="Private offer selection selection screen"]
 image::rosa-private-offer-selection-selection-screen.png[]
 
-.. The drop down menu allows selecting between multiple offers, if available. The previously activated public offer is shown together with the newly provided agreement based offer that is labeled as "Upgrade" in Figure 3.
+.. In the drop-down menu, select from multiple offers, if available. The previously activated public offer is shown together with the newly provided agreement based offer that is labeled as "Upgrade" in Figure 3.
 +
 [caption="Private offer selection dropdown"]
 +
@@ -48,15 +48,15 @@ image::rosa-private-offer-details.png[]
 +
 [NOTE]
 ====
-Private offers have several available configurations. 
+Private offers have several available configurations.
 
-* It is possible that the private offer you are accepting is set up with a fixed future start date. 
-* If you do not have another active {product-title} subscription at the time of accepting the private offer, a public offer or an older private offer entitlement, accept the private offer itself and continue with the account linking and cluster deployment steps after the specified service start date. 
+* It is possible that the private offer you are accepting is set up with a fixed future start date.
+* If you do not have another active {product-title} subscription at the time of accepting the private offer, a public offer or an older private offer entitlement, accept the private offer itself and continue with the account linking and cluster deployment steps after the specified service start date.
 
 You must have an active {product-title} entitlement to complete these steps. Service start dates are always reported in the UTC time zone
 ====
 
-. Create or upgrade your contract. 
+. Create or upgrade your contract.
 +
 .. For private offers accepted by an AWS account that does not have {product-title} activated yet and is creating the first contract for this service, click the *Create contract button*.
 +
@@ -78,7 +78,7 @@ image::rosa-private-offer-acceptance-confirmation-window.png[]
 [caption="Subscription confirmation"]
 image::rosa-subscription-contfirmation.png[]
 
-. If the accepted private offer has a future start date specified, return to the private offer page after the service start date, and click the *Setup your account* button to proceed with the Red{nbsp}Hat and AWS account linking. 
+. If the accepted private offer has a future start date specified, return to the private offer page after the service start date, and click the *Setup your account* button to proceed with the Red{nbsp}Hat and AWS account linking.
 +
 [NOTE]
 ====

diff --git a/modules/aws-account-billing-selection.adoc b/modules/aws-account-billing-selection.adoc
@@ -11,7 +11,7 @@ When deploying {product-title} clusters, verify that end users select the AWS bi
 
 .Procedure
 
-* When using the web interface for deploying {product-title}, the Associated AWS infrastructure account" is typically set to the AWS account ID used by the administrator of the cluster that is being created. 
+* When using the web interface for deploying {product-title}, the associated AWS infrastructure account is typically set to the AWS account ID used by the administrator of the cluster that is being created. 
 ** This can be the same AWS account as the billing AWS account. 
 ** AWS resources are deployed into this account and all the billing associated with those resources are processed accordingly.
 +

diff --git a/modules/aws-rh-linking.adoc b/modules/aws-rh-linking.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="aws-rh-linking_{context}"]
-= AWS and Red{nbsp}Hat account and subscription linking
+= Link AWS and Red{nbsp}Hat accounts and subscriptions
 
 [role="_abstract"]
 You must link your AWS and Red{nbsp}Hat accounts and subscriptions.

diff --git a/modules/cloud-experts-aws-load-balancer-operator-cleanup.adoc b/modules/cloud-experts-aws-load-balancer-operator-cleanup.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="cloud-experts-aws-load-balancer-operator-cleanup_{context}"]
-= Cleaning up
+= Clean up
 
 [role="_abstract"]
 Clean up your AWS resources after completing this lab tutorial.

diff --git a/modules/cloud-experts-aws-load-balancer-operator-environment.adoc b/modules/cloud-experts-aws-load-balancer-operator-environment.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="cloud-experts-aws-load-balancer-operator-environment_{context}"]
-= Setting up your environment
+= Set up your environment
 
 [role="_abstract"]
 You can use environment variables to ensure consistency across the commands within this lab.

diff --git a/modules/cloud-experts-aws-load-balancer-operator-validating.adoc b/modules/cloud-experts-aws-load-balancer-operator-validating.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="cloud-experts-aws-load-balancer-operator-validating_{context}"]
-= Validating the deployment
+= Validate the deployment
 
 [role="_abstract"]
 You can validate your load balancer Operators using the {oc-first} tool.

diff --git a/modules/cloud-experts-aws-secret-manager-create-iam-polices.adoc b/modules/cloud-experts-aws-secret-manager-create-iam-polices.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="cloud-experts-aws-secret-manager-create-iam-polices_{context}"]
-= Creating a Secret and IAM Access Policies
+= Create a Secret and IAM Access Policies
 
 [role="_abstract"]
 Use the AWS CLI to create your AWS secret and IAM access policies.

diff --git a/modules/cloud-experts-aws-secret-manager-creating-application.adoc b/modules/cloud-experts-aws-secret-manager-creating-application.adoc
@@ -10,7 +10,7 @@
 You can create your application using the secret that you created.
 
 .Procedure
-. Create an OpenShift project by running the following command:
+. Create an {OCP-short} project by running the following command:
 +
 [source,terminal]
 ----

diff --git a/modules/cloud-experts-aws-secret-manager-deply-aws-secrets.adoc b/modules/cloud-experts-aws-secret-manager-deply-aws-secrets.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="cloud-experts-aws-secret-manager-deply-aws-secrets_{context}"]
-= Deploying the AWS Secrets and Configuration Provider
+= Deploy the AWS Secrets and Configuration Provider
 
 [role="_abstract"]
 

diff --git a/modules/cloud-experts-custom-dns-resolver-configure-dns-server-classic.adoc b/modules/cloud-experts-custom-dns-resolver-configure-dns-server-classic.adoc
@@ -7,11 +7,11 @@
 = Configure your DNS server
 
 [role="_abstract"]
-{product-title} clusters require you to configure DNS server to forward the necessary private hosted zones to your Amazon Route 53 Inbound Resolver:
+{product-title} clusters require you to configure your DNS server to forward the necessary private hosted zones to your Amazon Route 53 Inbound Resolver:
 
 * `<domain-prefix>.<unique-ID>.p1.openshiftapps.com`
 
-This Amazon Route 53 private hosted zones is created during cluster creation. The `domain-prefix` is a customer-specified value, but the `unique-ID` is randomly generated during cluster creation and cannot be preselected. As such, you must wait for the cluster creation process to begin before configuring forwarding for the `p1.openshiftapps.com` private hosted zone. 
+This Amazon Route 53 private hosted zone is created during cluster creation. The `domain-prefix` is a customer-specified value, but the `unique-ID` is randomly generated during cluster creation and cannot be preselected. As such, you must wait for the cluster creation process to begin before configuring forwarding for the `p1.openshiftapps.com` private hosted zone. 
 
 .Procedure
 . Create your cluster.

diff --git a/modules/cloud-experts-custom-dns-resolver-configure-dns-server-hcp.adoc b/modules/cloud-experts-custom-dns-resolver-configure-dns-server-hcp.adoc
@@ -7,7 +7,7 @@
 = Configure your DNS server
 
 [role="_abstract"]
-{product-title} clusters require you to configure DNS server to forward the necessary private hosted zones to your Amazon Route 53 Inbound Resolver:
+{product-title} clusters require you to configure your DNS server to forward the necessary private hosted zones to your Amazon Route 53 Inbound Resolver:
 
 * `<cluster-name>.hypershift.local`
 * `rosa.<domain-prefix>.<unique-ID>.p3.openshiftapps.com`

diff --git a/modules/cloud-experts-custom-dns-resolver-environment-setup.adoc b/modules/cloud-experts-custom-dns-resolver-environment-setup.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="cloud-experts-custom-dns-resolver-environment-setup_{context}"]
-= Setting up your environment
+= Set up your environment
 
 [role="_abstract"]
 You can use environment variables to ensure consistency across the commands within this lab.

diff --git a/modules/cloud-experts-deploy-api-data-protection-cleanup.adoc b/modules/cloud-experts-deploy-api-data-protection-cleanup.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="cloud-experts-deploy-api-data-protection-cleanup_{context}"]
-=  Cleaning up
+= Clean up
 
 [role="_abstract"]
 Clean up your AWS resources after completing this lab tutorial.