Skip to content

EDU-4217: Corrects introductory wording for no-longer-tables #3489

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 28, 2025
Merged

EDU-4217: Corrects introductory wording for no-longer-tables #3489

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8c2e1bc
EDU-4217: Corrects introductory wording for no-longer-tables
fairlydurable Mar 28, 2025
372360b
Merge branch 'main' into EDU-4217
fairlydurable Mar 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions docs/production-deployment/cloud/high-availability/enable.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>

Expand Down Expand Up @@ -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>
Expand All @@ -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>

Expand Down
2 changes: 1 addition & 1 deletion docs/production-deployment/cloud/high-availability/how-to/failovers.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>

Expand Down