rephrasing

Author: HeidiSteen

articles/search/search-faceted-navigation.md

@@ -178,9 +178,11 @@ Each range is built using 0 as a starting point, a value from the list as an end
 
 ### Discrepancies in facet counts
 
-Under certain circumstances, you might find that facet counts aren't fully accurate due to the [sharding architecture](search-capacity-planning.md#concepts-search-units-replicas-partitions-shards). Every search index has multiple shards, and each shard reports the top N facets by document count, which are then combined into a single result. Because it's just the top facets for each shard, it's possible to miss or under-count matching documents in the facet response.
+Under certain circumstances, you might find that facet counts aren't fully accurate due to the [sharding architecture](search-capacity-planning.md#concepts-search-units-replicas-partitions-shards). Every search index is spread across multiple shards, and each shard reports the top N facets by document count, which are then combined into a single result. Because it's just the top N facets for each shard, it's possible to miss or under-count matching documents in the facet response.
 
-To guarantee accuracy, you can artificially inflate the count:\<number> to a large number to force full reporting from each shard. You can specify `"count": "0"` for unlimited facets. Or, you can set "count" to a value that's greater than or equal to the number of unique values of the faceted field. The tradeoff with this workaround is increased query latency, so use it only when necessary.
+To guarantee accuracy, you can artificially inflate the count:\<number> to a large number to force full reporting from each shard. You can specify `"count": "0"` for unlimited facets. Or, you can set "count" to a value that's greater than or equal to the number of unique values of the faceted field. For example, if you're faceting by a "size" field that has five unique values, you could set `"count": "5"` to ensure all matches are represented in the facet response. 
+
+The tradeoff with this workaround is increased query latency, so use it only when necessary.
 
 ## Presentation layer
 

articles/search/search-pagination-page-layout.md

@@ -60,7 +60,9 @@ Count is accurate when the index is stable. For an index under constant churn, t
 Count won't be affected by routine maintenance or other workloads on the search service. However if you have multiple partitions and a single replica, you could experience short-term fluctuations in document count (several minutes) as the partitions are restarted.
 
 > [!TIP]
-> When testing indexing, add `$count=true` to confirm the number of documents in the index. When testing query syntax, `$count=true` can quickly tell you whether your modifications are returning greater or fewer results.
+> Confirm whether the index contains the expected number of documents by adding `$count=true` on an empty search `search=*`. The result is the full count of documents in your index.
+>
+> When testing query syntax, `$count=true` can quickly tell you whether your modifications are returning greater or fewer results, which can be a useful data point to have on hand.
 
 ## Paging results