[draft] High Availability Deployment Models page

docs/cloud/high-availability/enable.mdx

@@ -137,6 +137,8 @@ Client APIs (Start, Signal, Cancel, Terminate, Query, and the equivalent Activit
 
 Same-region replicas are not affected by this setting.
 
+To deploy Worker fleets in both regions that stay on standby in the passive region until failover, see [Active / Passive (Hot)](/cloud/high-availability/deployment-patterns#active-hot).
+
 :::info
 
 To see which endpoints route to which replica, see [How requests reach the replica](/cloud/high-availability/ha-connectivity#how-requests-reach-the-replica).
@@ -152,10 +154,10 @@ Use the [`temporal cloud namespace ha update`](/cli/command-reference/cloud/name
 ```bash
 temporal cloud namespace ha update \
     --namespace <namespace>.<account> \
-    --disable-passive-poller-forwarding true
+    --passive-poller-forwarding disabled
 ```
 
-Set the flag to `false` to re-enable forwarding.
+Set the flag to `enabled` to re-enable forwarding.
 
 ### Set the forwarding behavior with the Cloud Ops API {/* #set-forwarding-curl */}
 

docs/cloud/high-availability/failovers/manage.mdx

@@ -178,6 +178,8 @@ the replica, the DNS redirection orchestrated by Temporal ensures that your exis
 Namespace without interruption. Temporal Cloud forwards their requests from the passive replica to the active region and
 the responses back, so Workers keep running through a failover.
 
+To choose where your Worker fleets run across regions, see [Deployment patterns for High Availability](/cloud/high-availability/deployment-patterns).
+
 To route Workers to the passive region's replica, see [How requests reach the replica](/cloud/high-availability/ha-connectivity#how-requests-reach-the-replica).
 
 To stop forwarding Worker polls to the active region, see [Change the forwarding behavior](/cloud/high-availability/enable#change-forwarding-behavior).

docs/cloud/high-availability/ha-connectivity.mdx

@@ -93,6 +93,10 @@ To learn what forwarding does, see [Request forwarding](/cloud/high-availability
 
 To stop forwarding Worker polls on a Namespace, see [Change the forwarding behavior](/cloud/high-availability/enable#change-forwarding-behavior).
 
+To run Worker fleets in both regions that rely on this forwarding, see [Active / Active](/cloud/high-availability/deployment-patterns#active-active).
+
+To keep passive-region Workers on standby until failover by disabling this forwarding, see [Active / Passive (Hot)](/cloud/high-availability/deployment-patterns#active-hot).
+
 ## How to use PrivateLink with High Availability features
 
 :::tip

docs/cloud/high-availability/index.mdx

@@ -105,6 +105,10 @@ To route Workers to the passive region's replica, see [How requests reach the re
 
 To disable passive region replica forwarding, see [Change the forwarding behavior](/cloud/high-availability/enable#change-forwarding-behavior).
 
+To run Worker fleets in both regions that rely on this forwarding, see [Active / Active](/cloud/high-availability/deployment-patterns#active-active).
+
+To keep passive-region Workers on standby until failover by disabling this forwarding, see [Active / Passive (Hot)](/cloud/high-availability/deployment-patterns#active-hot).
+
 ## Service levels and recovery objectives
 
 Namespaces using High Availability have a 99.99% [uptime SLA](/cloud/sla) with sub-1-minute [RPO](/cloud/rpo-rto) and 20-minute [RTO](/cloud/rpo-rto). For detailed information:

sidebars.js

@@ -1205,6 +1205,7 @@ module.exports = {
           },
           items: [
             'cloud/high-availability/enable',
+            'cloud/high-availability/deployment-patterns',
             'cloud/high-availability/monitoring',
             {
               type: 'category',