feat: add information on multiple VPCs.

use-timescale/vpc.md

@@ -11,16 +11,14 @@ cloud_ui:
 
 # Secure your $CLOUD_LONG services with VPC Peering and AWS PrivateLink
 
-You use Virtual Private Cloud ($VPC) peering to ensure that your $CLOUD_LONG services are 
+You use Virtual Private Cloud ($VPC) peering to ensure that your $SERVICE_LONG are 
 only accessible through your secured AWS infrastructure. This reduces the potential 
 attack vector surface and improves security.
 
 The data isolation architecture that ensures a highly secure connection between your apps and 
-$CLOUD_LONG:
+$CLOUD_LONG is:
 
-<img class="main-content__illustration"
-src="https://assets.timescale.com/docs/images/tsc-vpc-architecture.svg"
-alt="The AWS Security Groups dashboard"/>
+![$CLOUD_LONG isolation architecture](https://assets.timescale.com/docs/images/tsc-vpc-architecture.svg)
 
 Your apps run inside your AWS Customer VPC, your services always run 
 inside the secure $CLOUD_LONG $VPC. You control secure communication between apps in
@@ -35,9 +33,19 @@ peering connection to your Customer VPC, you use AWS Security Groups to
 restrict the services in your Customer VPC that are visible to the Peering VPC.
 The last step is to attach individual services to the Peering VPC. 
 
-The number of VPCs you can attach to your project depends on your [pricing plan][pricing-plans]. If you 
-need more VPCs either contact contact [support@timescale.com](mailto:support@timescale.com) or change your
-pricing plan in $CONSOLE. Each $CLOUD_LONG VPC can have as many peering connections as you need.
+* You define each $CLOUD_LONG $VPC on a [$CLOUD_LONG project level][project-members]. 
+* You can attach:
+  * Any number of Customer $VPCs to a $CLOUD_LONG $VPC.
+  * A $SERVICE_LONG to a single $CLOUD_LONG $VPC at a time.
+
+      The $SERVICE_SHORT and $VPC must be in the same AWS region. To support multiple AWS regions, you need multiple 
+      $CLOUD_LONG $VPCs.
+  * Multiple $SERVICE_LONGs to the same $CLOUD_LONG $VPC.
+* You cannot attach a $SERVICE_LONG to multiple $CLOUD_LONG $VPCs at the same time.
+
+The number of $CLOUD_LONG $VPCs you have in your project depends on your [pricing plan][pricing-plans]. 
+If you need another $CLOUD_LONG $VPC, either contact [support@timescale.com](mailto:support@timescale.com) or change your
+pricing plan in [$CONSOLE][console-login]. 
 
 ## Prerequisites
 
@@ -69,9 +77,21 @@ between $CLOUD_LONG and your own VPC in a logically isolated virtual network.
 
 1.  In [$CONSOLE > VPC][console-vpc], click `New VPC`.
 
-    The number of VPCs you can attach to your project depends on your [pricing plan][pricing-plans]. If you
-    need more VPCs either contact contact [support@timescale.com](mailto:support@timescale.com) or change 
-    your pricing plan in $CONSOLE. Each $CLOUD_LONG VPC can have as many peering connections as you need.
+    ![$CLOUD_LONG new $VPC](https://assets.timescale.com/docs/images/console-add-vpc.png)
+
+    * You can attach:
+      * Any number of Customer $VPCs to a $CLOUD_LONG $VPC.
+      * A $SERVICE_LONG to a single $CLOUD_LONG $VPC at a time.
+
+        The $SERVICE_SHORT and $VPC must be in the same AWS region. To support multiple AWS regions, you need multiple
+        $CLOUD_LONG $VPCs.
+      * Multiple $SERVICE_LONGs to the same $CLOUD_LONG $VPC.
+      * You cannot attach a $SERVICE_LONG to multiple $CLOUD_LONG $VPCs at the same time.
+
+    The number of $CLOUD_LONG $VPCs you have in your project depends on your [pricing plan][pricing-plans].
+    If you need another $CLOUD_LONG $VPC, either contact [support@timescale.com](mailto:support@timescale.com) or change your
+    pricing plan in [$CONSOLE][console-login].
+
 
 1.  Choose your region and IP range, then click `Create VPC`. 
 
@@ -227,3 +247,4 @@ some time for DNS propagation.
 
 [create-service]: /getting-started/:currentVersion:/services/#create-a-timescale-cloud-service
 [pricing-plans]: /about/:currentVersion:/pricing-and-account-management/
+[project-members]: /use-timescale/:currentVersion:/members/