docs: update pre-platform VPC peering docs (#9326)

Author: bsod90

docs/pages/product/deployment/cloud/vpc/aws.mdx

@@ -132,7 +132,12 @@ Customer Success Manager and share with them the following:
 [aws-docs-vpc-peering-routing]:
   https://docs.aws.amazon.com/vpc/latest/peering/vpc-peering-routing.html
 [aws-docs-vpc-peering]:
-  https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html
-[aws-docs-vpc-security-group]: https://docs.aws.amazon.com/vpc/latest/userguide/security-group-rules.html
+  https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html [aws-docs-vpc-security-group]: https://docs.aws.amazon.com/vpc/latest/userguide/security-group-rules.html
 [wiki-cidr-block]:
   https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_blocks
+
+## Supported Regions
+
+We support all general-purpose regions. Cube Store is currently located only in
+`US East 2` and `EU West 1` so pre-aggregations performance might depend on geographical
+proximity to it.

docs/pages/product/deployment/cloud/vpc/gcp.mdx

@@ -29,10 +29,9 @@ here][gcp-docs-create-vpc-peering], with the following amendments:
 
 ## Supported Regions
 
-- `northeast1`
-- `europe-west-2`
-- `europe-west-3`
-- `us-central-1`
+We support all general-purpose regions. Cube Store is currently located only in
+`US Central 1` and `Europe West 2` so pre-aggregations performance might depend
+on geographical proximity to it.
 
 ## Notes