diff --git a/_partials/_transit-gateway.md b/_partials/_transit-gateway.md
index e49bee33a2..e84fd4e336 100644
--- a/_partials/_transit-gateway.md
+++ b/_partials/_transit-gateway.md
@@ -8,23 +8,24 @@
 
        ![Create a new VPC in $CLOUD_LONG](https://assets.timescale.com/docs/images/tiger-cloud-console/configure-peering-vpc-tiger-cloud.png)
 
-       Your $SERVICE_SHORT and Peering $VPC must be in the same AWS region. The number of Peering $VPCs you can create in your project depends on your [price tier][pricing-plans]. If you need another Peering $VPC, either contact [support@tigerdata.com](mailto:support@tigerdata.com) or change your tier in [$CONSOLE][console-login].
+       Your $SERVICE_SHORT and Peering $VPC must be in the same AWS region. The number of Peering $VPCs you can create in your project depends on your [pricing plan][pricing-plans]. If you need another Peering $VPC, either contact [support@tigerdata.com](mailto:support@tigerdata.com) or change your plan in [$CONSOLE][console-login].
 
    1.  Add a peering connection:
 
        1. In the `VPC Peering` column, click `Add`.
-       1. Provide your AWS account ID, Transit Gateway ID, CIDR ranges, and AWS region.
+       1. Provide your AWS account ID, Transit Gateway ID, CIDR ranges, and AWS region. $CLOUD_LONG creates a new isolated connection for every unique Transit Gateway ID. 
+       
+         ![Add peering](https://assets.timescale.com/docs/images/tiger-cloud-console/add-peering-tiger-cloud.png)
+ 
        1. Click `Add connection`.
 
-       ![Add peering](https://assets.timescale.com/docs/images/tiger-cloud-console/add-peering-tiger-cloud.png)
-
 1. **Accept and configure peering connection in your AWS account**
 
    Once your peering connection appears as `Processing`, you can accept and configure it in AWS:
 
    1. Accept the peering request coming from $CLOUD_LONG. The request can take up to 5 min to arrive. Within 5 more minutes after accepting, the peering should appear as `Connected` in $CONSOLE.
 
-   1. Configure at least the following in yur AWS account networking:
+   1. Configure at least the following in your AWS account networking:
 
       - Your subnet route table to route traffic to your Transit Gateway for the Peering VPC CIDRs.
       - Your Transit Gateway route table to route traffic to the newly created Transit Gateway peering attachment for the Peering VPC CIDRs.
diff --git a/use-timescale/security/transit-gateway.md b/use-timescale/security/transit-gateway.md
index af6c6d07f3..dd1840ff3d 100644
--- a/use-timescale/security/transit-gateway.md
+++ b/use-timescale/security/transit-gateway.md
@@ -20,6 +20,8 @@ You use AWS Transit Gateway as a traffic controller for your network. Instead of
 
 You can then create a peering connection between your $SERVICE_LONGs and AWS Transit Gateway in $CLOUD_LONG. This means that, no matter how big or complex your infrastructure is, you can connect securely to your $SERVICE_LONGs. 
 
+For enhanced security, you can add peering connections to multiple Transit Gateways with overlapping CIDRs—$CLOUD_LONG creates a new isolated connection for every unique Transit Gateway ID. Otherwise, the existing connection is reused for your $SERVICE_SHORTs in the same project and region. 
+
 To configure this secure connection, you:
 
 1. Connect your infrastructure to AWS Transit Gateway.
@@ -27,9 +29,7 @@ To configure this secure connection, you:
 1. Accept and configure the peering connection on your side.
 1. Attach individual $SERVICE_SHORTs to the Peering $VPC.
 
-The AWS Transit Gateway feature is available for Scale and Enterprise [pricing plans][pricing-plans].
-
-AWS Transit Gateway enable you to connect from almost any environment, this page provides examples for the most common use cases. 
+AWS Transit Gateway enables you to connect from almost any environment, this page provides examples for the most common use cases. 
 
 <Tabs label="Connect from any cloud">