Mike's corrections on limits, python sample page edits

Author: HeidiSteen

articles/search/search-limits-quotas-capacity.md

@@ -78,9 +78,14 @@ When estimating document size, remember to consider only those fields that add v
 
 ## Vector index size limits
 
-When you index documents with vector fields, Azure AI Search constructs internal vector indexes using the algorithm parameters you provide. The size of these vector indexes is restricted by the memory reserved for vector search for your service's tier (or `SKU`).
+When you index documents with vector fields, Azure AI Search constructs internal vector indexes using the algorithm parameters you provide. The size of these vector indexes is restricted by the memory reserved for vector search for your service's tier (or `SKU`). For guidance on managing and maximizing vector storage, see [Vector index size and staying under limits](vector-search-index-size.md).
 
-Vector limits vary by [service creation date](vector-search-index-size.md#how-to-check-service-creation-date) and [tier](search-sku-tier.md). For guidance on managing and maximizing vector storage, see [Vector index size and staying under limits](vector-search-index-size.md).
+Vector limits vary by:
+
++ [service creation date](vector-search-index-size.md#how-to-check-service-creation-date)
++ [region](search-region-support.md)
+
+Higher vector limits from April 2024 onwards exist on *new search services* in regions providing the extra capacity, which is most of them.
 
 This table shows the progression of vector quota increases in GB over time. The quota is per partition, so if you scale a new Standard (S1) service to 6 partitions, total vector quota is 35 multiplied by 6.
 
@@ -99,7 +104,7 @@ This table shows the progression of vector quota increases in GB over time. The
 
 <sup>4</sup> Higher vector quota for more tiers and regions based on partition size updates.
 
-The service enforces a vector index size quota **for every partition** in your search service. Each extra partition increases the available vector index size quota. This quota is a hard limit to ensure your service remains healthy, which means that further indexing attempts once the limit is exceeded results in failure. You can resume indexing once you free up available quota by either deleting some vector documents or by scaling up in partitions.
+The service enforces a vector index size quota *for every partition* in your search service. Each extra partition increases the available vector index size quota. This quota is a hard limit to ensure your service remains healthy, which means that further indexing attempts once the limit is exceeded results in failure. You can resume indexing once you free up available quota by either deleting some vector documents or by scaling up in partitions.
 
 > [!IMPORTANT]
 > Higher vector limits are tied to larger partition sizes. Regions that run on older infrastructure are subject to the July-April limits. Review the [regions list](search-region-support.md) for status on partition storage limits.

articles/search/search-region-support.md

@@ -76,7 +76,7 @@ You can create an Azure AI Search resource in any of the following Azure public
 | North Europe​​ | ✅ | ✅ | ✅ |
 | West Europe​​ <sup>1, 2</sup>| ✅ | ✅ | ✅ |
 | France Central​​ | ✅ | ✅ | ✅ |
-| Germany West Central​ <sup>2</sup> ​| ✅ |  | ✅ |
+| Germany West Central​ ​| ✅ |  | ✅ |
 | Italy North​​ |  |  | ✅ |
 | Norway East​​ | ✅ |  | ✅ |
 | Poland Central​​ |  |  |  |
@@ -107,9 +107,7 @@ You can create an Azure AI Search resource in any of the following Azure public
 
 | Region | AI integration | Semantic ranking | Availability zones |
 |--|--|--|--|
-| South Africa North​ <sup>1</sup> | ✅ |  | ✅ |
-
-<sup>1</sup> This region runs on older infrastructure that has lower storage limits per partition at every tier. Choose a different region if you want [higher limits](search-limits-quotas-capacity.md#service-limits).
+| South Africa North​ | ✅ |  | ✅ |
 
 ### Asia Pacific