diff --git a/docs/production-deployment/cloud/high-availability/enable.mdx b/docs/production-deployment/cloud/high-availability/enable.mdx
index f258b479ef..be64eecda2 100644
--- a/docs/production-deployment/cloud/high-availability/enable.mdx
+++ b/docs/production-deployment/cloud/high-availability/enable.mdx
@@ -59,7 +59,7 @@ This page explains how to enable and manage these features.
 ## Create a Namespace with High Availability features {#create}
 
 To create a new Namespace with High Availability features, you can use the Temporal Cloud UI or the tcld command line utility.
-The following table explains how:
+The following instructions explain how:
 
 <Tabs>
 
@@ -98,7 +98,6 @@ Specify the [region codes](/cloud/high-availability/regions) as arguments to the
 
 If using API key authentication with the `--api-key` flag, you must add it directly after the tcld command and before `namespace create`.
 
-
 </TabItem>
 
 </Tabs>
@@ -116,7 +115,7 @@ Contact [Support](https://support.temporal.io) to request more regions.
 Upgrade an existing standard Namespace by adding High Availability features.
 Adding a replica unlocks that functionality.
 
-The following table explains how:
+The following instructions explain how:
 
 <Tabs>
 
diff --git a/docs/production-deployment/cloud/high-availability/how-to/failovers.mdx b/docs/production-deployment/cloud/high-availability/how-to/failovers.mdx
index a187c59ccb..86ec8d2f97 100644
--- a/docs/production-deployment/cloud/high-availability/how-to/failovers.mdx
+++ b/docs/production-deployment/cloud/high-availability/how-to/failovers.mdx
@@ -45,7 +45,7 @@ A forced failover when there is a significant replication lag has a higher likel
 ### Trigger the failover {#manual-failovers}
 
 You can trigger a failover manually using the Temporal&nbsp;Cloud<br />Web&nbsp;UI or the tcld CLI, depending on your preference and setup.
-The following table outlines the steps for each method:
+The following instructions outline the steps for each method:
 
 <Tabs>