temporalio · brianmacdonald-temporal · Mar 2, 2026 · Feb 27, 2026 · Mar 2, 2026
@@ -23,7 +23,7 @@ keywords:
 
 import { RelatedReadContainer, RelatedReadItem } from '@site/src/components';
 
-Temporal Cloud Automation changes the way how you manage and scale your cloud infrastructure.
+Temporal Cloud Automation changes how you manage and scale your cloud infrastructure.
 Its features enable you to automate critical tasks like user and namespace management, mTLS certificate rotation, and access control, ensuring security and operational efficiency.
 Cloud Automation offers secure authentication across all interfaces, reducing errors and enhancing security.
 
@@ -40,4 +40,4 @@ Cloud Automation offers secure authentication across all interfaces, reducing er
   <RelatedReadItem path="/cloud/terraform-provider" text="Terraform Provider for Cloud" archetype="cloud-guide" />
 </RelatedReadContainer>
 
-From centralizing cloud operations and automating certificate rotation to streamlining user management and onboarding new teams, Temporal's Cloud Automation features covers a wide range of use cases that enhance efficiency and security across your organization.
+From centralizing cloud operations and automating certificate rotation to streamlining user management and onboarding new teams, Temporal's Cloud Automation features cover a wide range of use cases that enhance efficiency and security across your organization.
@@ -24,7 +24,7 @@ Workflow input and output need to be serialized and deserialized so they can be
 
 Temporal provides its own default Data Converter logic, which is not apparent to a user if payloads contain plain text or JSON data.
 For enhanced security, you can implement your own encryption standards using a Codec Server.
-Temporal's data encryption capabilities ensures the security and confidentiality of your Workflows and provides protection without compromising performance.
+Temporal's data encryption capabilities ensure the security and confidentiality of your Workflows and provides protection without compromising performance.
 
 Jump straight to a Temporal SDK feature guide.
 

@@ -36,7 +36,7 @@ Through a Temporal SDK, Temporal provides a wide range of features that enable d
 - **[Temporal Nexus](/evaluate/nexus)**: Connect Temporal Applications across (and within) isolated Namespaces for improved modularity, security, debugging, and fault isolation. Nexus supports cross-team, cross-domain, and multi-region use cases.
 - **[Workflow message passing](/evaluate/development-production-features/workflow-message-passing)**: Build responsive applications that react to events at runtime and enable data retrieval from ongoing Workflows.
 - **Versioning**: Support multiple versions of your business logic for long-running business processes.
-- **[Observability](/evaluate/development-production-features/observability)**: List business process, view their state, and set up dashboards with metrics.
+- **[Observability](/evaluate/development-production-features/observability)**: List business processes, view their state, and set up dashboards with metrics.
 - **[Debugging](/evaluate/development-production-features/debugging)**: Surface errors and step through code to find issues.
 - **[Data encryption](/evaluate/development-production-features/data-encryption)**: Transform data and protect the privacy of the users of your application.
 - **[Throughput composability](/evaluate/development-production-features/throughput-composability)**: Breakup business processes by data streams, team ownership, or other organization factors.

@@ -42,15 +42,15 @@ Temporal provides Signals, Queries, and Updates to allow rich interactivity with
 
 **Updates**: Update to send synchronous requests to your Workflow and track it in real-time.
 
-To learn more about using these powerful primitives, see our encyclopedia Entry:
+To learn more about using these powerful primitives, see our encyclopedia entry:
 
 <RelatedReadContainer>
   <RelatedReadItem path="/encyclopedia/workflow-message-passing" text="Workflow message passing (Signals, Queries, & Updates)" archetype="encyclopedia" />
 </RelatedReadContainer>
 
 For a deeper dive into Workflow message passing, enroll in one of [our courses](https://learn.temporal.io/courses/interacting_with_workflows).
 
-If you want to jump to straight to implementation details, see the SDK feature guides.
+If you want to jump straight to implementation details, see the SDK feature guides.
 
 <RelatedReadContainer>
   <RelatedReadItem path="/develop/go/message-passing" text="Go SDK Workflow message passing feature guide" archetype="feature-guide" />

@@ -51,7 +51,7 @@ Base allocations help you get started with the Temporal platform, so you can bet
 - Temporal Cloud Plans are charged monthly.
 - Action and Storage allocations are reset each calendar month.
 
-Temporal offers four plans: Essential, Business, Enterprise, Mission Critical.
+Temporal offers four plans: Essentials, Business, Enterprise, Mission Critical.
 Prices are outlined in the following table:
 
 |                   | Essentials                                                                     | Business                                                                                                                          | Enterprise                                                                                                                                                 | Mission Critical                                                                                                                                           |

@@ -31,7 +31,7 @@ We record the number of gRPC service errors that occurred.
 For each Namespace, we calculate the service-error rate as 1 - (count of errors / count of requests).
 Rates are averaged per month and reset quarterly.
 
-Errors are recorded against the SLA are service errors, such as the `UNAVAILABLE` [gRPC status code](https://grpc.github.io/grpc/core/md_doc_statuscodes.html).
+Errors recorded against the SLA are service errors, such as the `UNAVAILABLE` [gRPC status code](https://grpc.github.io/grpc/core/md_doc_statuscodes.html).
 The following errors are _not_ counted against the SLA:
 
 - `ClientVersionNotSupported`

@@ -21,7 +21,7 @@ tags:
 Temporal Cloud includes the right level of technical support and guidance, services and training needed to onboard you successfully, assist with design and deployment of your application efficiently and at scale.
 Our team has extensive knowledge of Temporal, and a broad set of skills to help you succeed with any project.
 
-Temporal Cloud provides several levels of support, from assisting with for break/fix scenarios to issues and services to helping with onboarding, design/code reviews for your application, and pre-production optimizations and operational readiness.
+Temporal Cloud provides several levels of support, from assisting with break/fix scenarios to issues and services to helping with onboarding, design/code reviews for your application, and pre-production optimizations and operational readiness.
 
 :::note
 

@@ -35,7 +35,7 @@ Offloading the responsibility of failure management from the application to the
 Temporal is a Durable Execution Platform.
 Durable Execution ensures that your application behaves correctly despite adverse conditions by guaranteeing that it will run to completion.
 This shift simplifies the development process. If a failure or a crash happens, your business processes keep running seamlessly without interruptions.
-Developers shift their focus on business logic rather than infrastructure concerns and create applications that are inherently scalable and maintainable.
+Developers shift their focus to business logic rather than infrastructure concerns and create applications that are inherently scalable and maintainable.
 
 Thousands of developers trust Temporal for use cases like order processing, customer onboarding, and payment handling because it enables them to build invincible applications that are resilient, durable, and _just work_.
 With Temporal, your applications keep running, no matter what happens.
@@ -131,7 +131,7 @@ These are powerful for debugging uses and provide real-time monitoring of your a
 ### Temporal UI
 
 The Temporal UI is a browser-based user interface that allows you to see the progress of your application.
-Also, known as the Web UI, it can also help you to quickly isolate, debug, and resolve production problems.
+Also known as the Web UI, it can also help you to quickly isolate, debug, and resolve production problems.
 
 <CaptionedImage src="/img/webui/workflow-details-page-hiw.avif" title="Recent Workflows page" />
 

@@ -71,7 +71,7 @@ Temporal ensures Durable Execution of tools, LLMs, and conversations, letting yo
 ### Human in the Loop
 
 "Human in the Loop" systems require human interaction for certain steps, such as customer onboarding, forms, or invoice approval.
-These are event driven system with humans generating events, and may be challenging to implement due to timing or unreliable connections between the human to the rest of the system.
+These are event-driven systems with humans generating events, and may be challenging to implement due to timing or unreliable connections between the human to the rest of the system.
 They can use schedules and timers to prompt for user input.
 
 **Example**: [Background checks example using the Go SDK](https://learn.temporal.io/examples/go/background-checks/).
@@ -88,7 +88,7 @@ The example below showcases how Workflow Executions, written in different langua
 
 ### Long Running Tasks
 
-This use case is particularly relevant for scenarios like shopping cart Workflows in an eCommerce app, where you can handling long-running tasks efficiently without managing state in a separate database.
+This use case is particularly relevant for scenarios like shopping cart Workflows in an eCommerce app, where you can handle long-running tasks efficiently without managing state in a separate database.
 It processes one message at a time, ensuring each message is processed only once.
 
 This approach addresses issues that can arise with long message processing times, which in other systems might cause consumer failover (typically with a default 5-minute message poll timeout) and potentially result in duplicate message processing by multiple consumers.
@@ -124,6 +124,6 @@ Temporal simplifies the complexity of state machines by providing a structured a
 
 :::tip
 
-If you're interested in code to help get you started, check out our [Temporal Example Applications](https://learn.temporal.io/examples/), [Getting Starting Tutorials](https://learn.temporal.io/getting_started/), or [Project-based Tutorials](https://learn.temporal.io/tutorials/).
+If you're interested in code to help get you started, check out our [Temporal Example Applications](https://learn.temporal.io/examples/), [Getting Started Tutorials](https://learn.temporal.io/getting_started/), or [Project-based Tutorials](https://learn.temporal.io/tutorials/).
 
 :::
@@ -50,7 +50,7 @@ Temporal recommends scaling your clusters to well above the average throughput.
 See [Scaling Temporal: The Basics](https://temporal.io/blog/scaling-temporal-the-basics) for an introduction to the topic.
 
 Temporal server throughput is often limited by the number of [Shards](/temporal-service/temporal-server#history-shard) configured for the Temporal Service.
-A Shard is an unit within a Temporal Service by which concurrent Workflow Execution throughput can be scaled.
+A Shard is a unit within a Temporal Service by which concurrent Workflow Execution throughput can be scaled.
 Shard capacity, and often overall cluster throughput, is set at build time for a cluster and that cluster setting cannot be adjusted later.
 Adding more Shards if needed requires a cluster rebuild, and a migration to the new cluster.
 
@@ -97,7 +97,7 @@ Running multiple Temporal Services is complex work, as each needs its own setup,
 Needing to monitor and manage all your Temporal Services in a unified way leads to operational management pain.
 Consider adding a layer on top of Temporal to manage multiple Temporal Services: a control plane.
 A control plane manages and directs data flow, deciding where data packets should be sent.
-A Temporal Service data plan can streamline operations and improve efficiency.
+A Temporal Service data plane can streamline operations and improve efficiency.
 Since Temporal does not ship its own open source data plane, rolling your own can be complex and take effort to add.
 
 Temporal Cloud provides exactly that support.

@@ -259,7 +259,7 @@ T = 1: namespace failover to Cluster C, adding event with event ID == 4 & versio
 
 T = 2: replication task from Cluster C arrives in Cluster B
 
-Note: below is a tree structures
+Note: below is a tree structure
 
 ```
 | -------------- | ------------- |

@@ -188,7 +188,7 @@ If you're upgrading MySQL to v8.0.17 or later to enable advanced Visibility feat
 
 ### Roll-out technique
 
-We recommend preparing a staging Temporal Service and then do the following to verify the upgrade is successful:
+We recommend preparing a staging Temporal Service and then doing the following to verify the upgrade is successful:
 
 1. Create some simulation load on the staging Temporal Service.
 2. Upgrade the database schema in the staging Temporal Service.

@@ -501,7 +501,7 @@ persistence:
 The database schema and setup for a secondary store depends on the database you plan to use.
 
 - [MySQL](#mysql)
-- [PostgresSQL](#postgresql)
+- [PostgreSQL](#postgresql)
 - [SQLite](#sqlite)
 - [Elasticsearch](#elasticsearch)
 

@@ -18,7 +18,7 @@ tags:
   - Temporal Cloud
 ---
 
-Temporal Workers run in [Kubernetes](https://kubernetes.io)-based deployments deliver scale, resilience, and flexible resource management.
+Temporal Workers running in [Kubernetes](https://kubernetes.io)-based deployments deliver scale, resilience, and flexible resource management.
 Amazon EKS (Elastic Kubernetes Service) offers one of the most popular choices for running Temporal Workers.
 It integrates smoothly with AWS services and supports auto-scaling and fault tolerance—key features for many Temporal users.
 

@@ -234,7 +234,7 @@ For example, you have a Current Version and a Ramping Version at 50%. If all of
 Keep in mind that Child Workflows of a parent or previous Auto-Upgrade Workflow default to Auto-Upgrade behavior and not Unspecified.
 :::
 
-You also want to make sure you understand how your Activities are going to work across different Worker Deployment Versions. Refer to the [Worker Versioning Activitiy behavior docs](/worker-versioning#actvity-behavior-across-versions) for more details.
+You also want to make sure you understand how your Activities are going to work across different Worker Deployment Versions. Refer to the [Worker Versioning Activity behavior docs](/worker-versioning#actvity-behavior-across-versions) for more details.
 
 ## Rolling out changes with the CLI
 
@@ -486,7 +486,7 @@ If you have implemented [Queries](/sending-messages#sending-queries) on closed p
 
 Before deploying a new Workflow revision, you can test it with synthetic traffic.
 
-To do this, use pinning in your tests, following the examples following
+To do this, use pinning in your tests, following the examples below
 
 <SdkTabs>
 <SdkTabs.Go>