temporalio · brianmacdonald-temporal · Mar 2, 2026 · Feb 27, 2026 · Feb 27, 2026 · Mar 2, 2026
@@ -27,7 +27,7 @@ tags:
   - TRUs
 ---
 
-Each Namespace in Temporal has a rate limit, which is measure in [Actions](/cloud/pricing#action) per second. 
+Each Namespace in Temporal has a rate limit, which is measured in [Actions](/cloud/pricing#action) per second. 
 Temporal offers two different modes for adjusting capacity: On-Demand Capacity or Provisioned Capacity.
 With On-Demand Capacity, Namespace capacity is increased automatically along with usage.
 With Provisioned Capacity, you can control your capacity limits by requesting Temporal Resource Units (TRUs).

@@ -96,7 +96,7 @@ When you connect to Temporal Cloud through GCP Private Service Connect you norma
 1. **Point your SDKs/Workers at the Private Service Connect endpoint IP address** _and_
 2. **Override the Server Name Indicator (SNI)** so that the TLS handshake still presents the public Temporal Cloud hostname (e.g., `my-namespace.my-account.tmprl.cloud`).
 
-By creating a **private Cloud DNS zone (PZ)** that maps the public TemporalC Cloud hostname (or the region hostname) directly to the PSC endpoint IP address, you can:
+By creating a **private Cloud DNS zone (PZ)** that maps the public Temporal Cloud hostname (or the region hostname) directly to the PSC endpoint IP address, you can:
 
 - Keep using the standard Temporal Cloud hostnames in code and configuration.
 - Eliminate the need to set a custom SNI override.

@@ -223,7 +223,7 @@ TEMPORAL_TLS_SERVER_NAME=my-namespace.my-account.tmprl.cloud
 temporal workflow count -n $TEMPORAL_NAMESPACE
 ```
 
-#### grcpurl
+#### grpcurl
 ```bash
 grpcurl \
     -servername my-namespace.my-account.tmprl.cloud \

@@ -93,7 +93,7 @@ Don't forget to click Create at the end of your setup to confirm your export.
 
 To access export-related commands in tcld, please follow these steps:
 
-1. Download the latest version of tcld from following instructions (here)[https://docs.temporal.io/cloud/tcld/#install-tcld].
+1. [Download the latest version of tcld](https://docs.temporal.io/cloud/tcld/#install-tcld).
 2. Make sure your tcld version is v0.35.0 or above.
 3. Run the command: `tcld n export gcs`:
    ```bash

@@ -459,7 +459,7 @@ A: Up to 10 non-expired keys per user and 20 non-expired keys per Service Accoun
 
 A: Yes, API keys expire based on the specified expiration date. Temporal recommends rotating API keys periodically.
 
-**Q: Whats the maximum allowed expiration for an API key?**
+**Q: What's the maximum allowed expiration for an API key?**
 
 A: The maximum expiration time for an API key is 2 years.
 

@@ -63,7 +63,7 @@ The "Recent Bill" card displays the previous bill amount.
 
 - If you pay your invoices through Stripe, you'll see a **Pay Now** button.
   It takes you to the Stripe portal to complete your payment
-- If your account is set up for auto-payment, you don’t need manually pay bills.
+- If your account is set up for auto-payment, you don’t need to manually pay bills.
   However, you can choose to make manual payments whenever you wish
 
 ## Invoices {#invoice}

@@ -58,7 +58,7 @@ of numbers and letters like `f45a2`, at least five characters long. This account
 time each customer uses Temporal Cloud.
 
 At times you may need to know your customer Account ID. Accessing the account's Namespaces provides an easy way to
-capture this information. Each Temporal Namespace use an Account ID suffix. This is the alphanumeric character string
+capture this information. Each Temporal Namespace uses an Account ID suffix. This is the alphanumeric character string
 found after the period in any Temporal Cloud Namespace name.
 
 You can retrieve an Account ID from the [Temporal Cloud](https://cloud.temporal.io) Web UI or by using the `tcld`
@@ -337,7 +337,7 @@ Which one to use depends on your authentication method and whether your Namespac
 |                        | Not High Availability | High Availability                                                                                                            |
 | ---------------------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
 | mTLS Authentication    | Namespace             | Namespace                                                                                                                    |
-| API Key Authentication | Regional              | Both work, but we reommend using the Namespace endpoint because it reduces the unavailability window during a failover event |
+| API Key Authentication | Regional              | Both work, but we recommend using the Namespace endpoint because it reduces the unavailability window during a failover event |
 
 :::info
 

@@ -147,7 +147,7 @@ tcld service-account delete --service-account-id "e9d87418221548"
 ```
 
 Use the tcld Service Account list command to validate the Service Account has been removed from the account.
-The Service Account is deleted when it is no longer visible in the output of .
+The Service Account is deleted when it is no longer visible in the output of the list command.
 
   </TabItem>
 </Tabs>
@@ -224,10 +224,10 @@ The resulting Namespace-scoped Service Account will be named `<namespace>-servic
 
 #### Using tcld
 
-To create a Namespace-scoped Service Account with tcld, use the `tcld service-accounted create-scoped` command:
+To create a Namespace-scoped Service Account with tcld, use the `tcld service-account create-scoped` command:
 
 ```
-tcld service-account created-scoped -n "test-scoped-sa" --np "test-ns=Admin"
+tcld service-account create-scoped -n "test-scoped-sa" --np "test-ns=Admin"
 ```
 
 This example creates a Namespace-scoped Service Account for the Namespace `test-ns`, named `test-scoped-sa`, with `Admin` Namespace Permission.

@@ -83,7 +83,7 @@ To join Temporal Cloud, the user must select **Accept Invite** in the message.
 
 <TabItem value="invite-ops-api" label="Cloud Ops API">
 
-You can invite users pragmatically using the Cloud Ops API.
+You can invite users programmatically using the Cloud Ops API.
 
 1. Create a connection to your Temporal Service using the Cloud Operations API.
 2. Use the [CreateUser service](https://github.com/temporalio/api-cloud/blob/main/temporal/api/cloud/cloudservice/v1/service.proto) to create a user.

@@ -178,7 +178,7 @@ To delete a user, a user must have the Account Owner or Global Admin account-lev
 
 {/* How to delete a user from your Temporal Cloud account using Web UI */}
 
-### How to update an account-level role using Web UI
+### How to delete a user using Web UI
 
 1. In Temporal Web UI, select **Settings** in the left portion of the window.
 1. On the **Settings** page, find the user and, on the right end of the row, select **Delete**.
@@ -191,7 +191,7 @@ You can delete a user in two other ways in Web UI:
 
 {/* How to delete a user from your Temporal Cloud account using tcld */}
 
-### How to update an account-level role using tcld
+### How to delete a user using tcld
 
 For details, see the [tcld user delete](/cloud/tcld/user/#delete) command.
 

@@ -11,7 +11,7 @@ keywords:
   - introduction
   - metrics
   - observability
-  - promentheus
+  - prometheus
   - reference
   - tcld cli
   - temporal cloud

@@ -52,7 +52,7 @@ includes a default dashboard to visualize the data with HyperDX. See the [integr
 
 ### New Relic
 
-New Relic integrates with Temporal Cloud via the infrastructure agent using a flex integration that pull data from the OpenMetrics endpoint. See the [integration page](https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration/) for more details.
+New Relic integrates with Temporal Cloud via the infrastructure agent using a flex integration that pulls data from the OpenMetrics endpoint. See the [integration page](https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration/) for more details.
 
 ### Prometheus \+ Grafana
 

@@ -211,7 +211,7 @@ For Temporal SDKs, you must have Prometheus running and configured to listen on
 
 For this example, you can run Prometheus locally or as a Docker container.
 In either case, ensure that you set the listen targets to the ports where you expose your scrape endpoints.
-When you run Prometheus locally, set your target address to port 8077 in your Prometheus configuration YAML file. (We set the scrape endopint to port 8077 in the [SDK metrics setup](#sdk-metrics-setup) example.)
+When you run Prometheus locally, set your target address to port 8077 in your Prometheus configuration YAML file. (We set the scrape endpoint to port 8077 in the [SDK metrics setup](#sdk-metrics-setup) example.)
 
 Example:
 

@@ -11,7 +11,7 @@ keywords:
   - introduction
   - metrics
   - observability
-  - promentheus
+  - prometheus
   - reference
   - tcld cli
   - temporal cloud

@@ -196,7 +196,7 @@ Labels: temporal_account, temporal_namespace, operation, temporal_service_type
 
 Temporal Cloud metrics include key-value pairs called labels in their associated metadata.
 Labels help you categorize and differentiate metrics for precise filtering, querying, and aggregation.
-Use labels to specific attributes or compare values, such as numeric buckets in histograms.
+Use labels to filter specific attributes or compare values, such as numeric buckets in histograms.
 This added context enhances the monitoring and analysis capabilities, providing deeper insights into your data.
 
 Use the following labels to filter metrics:

@@ -270,7 +270,7 @@ Testing uses the following process:
 
 1. Create or identify a non-production Namespace that can tolerate data loss in the event of issues.
 2. Create target cloud-side Namespace and add the Namespace definition to the S2S Proxy configuration.
-3. Run test Workflows agains the Namespace.
+3. Run test Workflows against the Namespace.
 4. Perform a complete end-to-end migration for the Namespace (see remaining phases for full process).
 
 Testing is considered successful if all data from the self-hosted deployment is migrated to cloud.

@@ -34,7 +34,7 @@ Nexus requests (commands, polling) are counted as part of the overall [Namespace
 
 ## Operational Limits
 
-Nexus has operational limits for thing like the maximum number of Nexus Endpoints and the maximum request handler timeout.
+Nexus has operational limits for things like the maximum number of Nexus Endpoints and the maximum request handler timeout.
 
 ### Max Nexus Endpoints
 

@@ -1,7 +1,7 @@
 ---
 id: observability
 slug: /cloud/nexus/observability
-title: Obserability - Temporal Nexus
+title: Observability - Temporal Nexus
 description: Learn about integrated observability in Temporal Nexus including cloud metrics and audit log streaming.
 sidebar_label: Observability
 tags:

@@ -129,7 +129,7 @@ The following examples illustrate the RTO and SLA calculations for different typ
 
 Suppose that region `middle-earth-1` experienced a cascading failure starting at 10:00:00 UTC, causing various instances and machines to fail over time. Temporal's automatic failover triggered for all Namespaces and completed at 10:15:00 UTC. 
 
-- Namespace 0 was in the region but its cell was not affected by the outage. The only downtime it had was for a few seconds during the failover operation. It experienced a near-zero Recovery Time, and its service error rate was neglible.  Graceful failover was successful, and this Namespace achieved a recovery point of 0.
+- Namespace 0 was in the region but its cell was not affected by the outage. The only downtime it had was for a few seconds during the failover operation. It experienced a near-zero Recovery Time, and its service error rate was negligible.  Graceful failover was successful, and this Namespace achieved a recovery point of 0.
 
 - Namespace 1_A was in the region and its cell experienced a partial degradation that caused 10% of requests to fail in the first 5 minutes, 25% in the second five minutes, and 50% in the third five minutes. Since it was significantly impacted from 10:00:00 to 10:15:00, its Recovery Time was 15 minutes. If it had no other service errors that month, then its service error rate for the month would be: ( (1 - 10%) + (1 - 25%) + (1 - 50%) + 8925 * 100% ) / 8928  = 99.990%. (Note: there are 8928 5-minute periods in a 31-day month.)  Graceful failover was successful, and this Namespace achieved a recovery point of 0.
 

@@ -120,7 +120,7 @@ There is no SLA for replication lag.
 Temporal recommends that customers do not trigger failovers except for testing or emergency situations.
 High Availability feature's four-9 guarantee SLA means Temporal will handle failovers and ensure high availability.
 Temporal also monitors replication lag.
-Customer who decide to trigger failovers should look at this metric before moving forward.
+Customers who decide to trigger failovers should look at this metric before moving forward.
 
 **If the lag is high, what should you do?**
 We don't expect users to failover.

@@ -110,7 +110,7 @@ import, create, update, and delete Namespaces with Terraform.
 You must use an Identity with Temporal Cloud Namespace management privileges. This includes the Account Owner, Global
 Admin, or Developer Account Role.
 
-For more detailed examples on how to manage Namespaces via Terraform, check the [Terraform Registry documention for Namspaces](https://registry.terraform.io/providers/temporalio/temporalcloud/latest/docs/resources/namespace).
+For more detailed examples on how to manage Namespaces via Terraform, check the [Terraform Registry documentation for Namespaces](https://registry.terraform.io/providers/temporalio/temporalcloud/latest/docs/resources/namespace).
 
 **How do I create a Namespace with Terraform?**
 
@@ -465,7 +465,7 @@ For example, to change the allowed caller Namespaces on a Nexus Endpoint:
    ```
 
    Upon completion, you will see a success message indicating your Nexus Endpoint has been updated. It may take several
-   seconds to update a Nexus Endpoint in the control plane which is visibile from the Temporal UI or tcld CLI.
+   seconds to update a Nexus Endpoint in the control plane which is visible from the Temporal UI or tcld CLI.
    Propagation of Nexus Endpoint changes to the data plane may take longer, but usually complete in less than one
    minute.
 
@@ -561,7 +561,7 @@ Cautions about Temporal User management:
 
 :::
 
-For more detailed examples on how to manage Namespaces via Terraform, check the Terraform Registry documention for [provisioning a Temporal Cloud user](https://registry.terraform.io/providers/temporalio/temporalcloud/latest/docs/resources/user).
+For more detailed examples on how to manage Namespaces via Terraform, check the Terraform Registry documentation for [provisioning a Temporal Cloud user](https://registry.terraform.io/providers/temporalio/temporalcloud/latest/docs/resources/user).
 
 **How do I create a Temporal Cloud User with Terraform?**