Merge pull request #128 from HeidiSteen/heidist-rag

misc edit

Author: prmerger-automator[bot]

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

@@ -63,11 +63,14 @@ You might find some variation in maximum limits if your service happens to be pr
 
 ## Document limits 
 
-You can have approximately 24 billion documents per index on Basic, S1, S2, S3, L1, and L2 search services. For S3 HD, the limit is 2 billion documents per index. Each instance of a complex collection counts as a separate document in terms of these limits.
+Maximum number of documents per index are:
 
-### Document size limits per API call
++ 24 billion on Basic, S1, S2, S3, L1, and L2 search services.
++ 2 billion on S3 HD.
 
-The maximum document size when calling an Index API is approximately 16 megabytes.
+Each instance of a complex collection counts as a separate document in terms of these limits.
+
+Maximum document size when calling an Index API is approximately 16 megabytes.
 
 Document size is actually a limit on the size of the Index API request body. Since you can pass a batch of multiple documents to the Index API at once, the size limit realistically depends on how many documents are in the batch. For a batch with a single document, the maximum document size is 16 MB of JSON.
 
@@ -79,19 +82,15 @@ When you index documents with vector fields, Azure AI Search constructs internal
 
 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 table describes the vector index size quota per partition across the service tiers. For context, it includes:
-
-+ [Partition storage limits](#service-limits) for each tier, repeated here for context.
-+ Amount of each partition (in GB) available for vector indexes (created when you add vector fields to an index).
-+ Approximate number of embeddings (floating point values) per partition.
+Vector limits vary by service creation date and tier.
 
-Use the [GET Service Statistics](/rest/api/searchservice/get-service-statistics) to retrieve your vector index size quota or review the **Indexes** page or **Usage** tab in the Azure portal.
++ To check the age of your search service or learn more about vector indexes, see [Vector index size and staying under limits](vector-search-index-size.md).
 
-Vector limits vary by service creation date and tier. To check the age of your search service and learn more about vector indexes, see [Vector index size and staying under limits](vector-search-index-size.md).
++ To view the vector quota in effect for your search service, use [GET Service Statistics](/rest/api/searchservice/get-service-statistics), or check the **Properties** and **Usage** tabs for your search service in the Azure portal.
 
-### Storage quota (GB)
+#### Storage quota (GB)
 
-This table shows the progression of storage quota increases in GB over time. Vector quota is per partition, so the increase in vector quota is bound to the increase in per-partition storage for each tier. Higher capacity partitions came online starting in April 2024.
+This table repeats [partition storage limits](#service-limits) for context. The table shows the progression of storage quota increases in GB over time. Vector quota is per partition, so the increase in vector quota is bound to the increase in per-partition storage for each tier. Higher capacity partitions were brought online starting in April 2024.
 
 | Service creation date |Basic | S1| S2 | S3 | L1 | L2 |
 |-----------------------|------|---|----|----|----|----|
@@ -108,7 +107,7 @@ This table shows the progression of storage quota increases in GB over time. Vec
 
 <sup>4</sup> Higher capacity storage for more tiers and more regions. **Europe**: Germany North​, Germany West Central, Switzerland West​. **Azure Government**: Texas, Arizona, Virginia. **Africa**: South Africa North​. **Asia Pacific**: China North 3, China East 3.
 
-### Vector quota per partition (GB)
+#### Vector quota per partition (GB)
 
 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.