Apply suggestions from code review

Co-authored-by: kolchfa-aws <[email protected]>
Signed-off-by: Jay Deng <[email protected]>

_search-plugins/concurrent-segment-search.md

@@ -154,7 +154,7 @@ The following aggregations do not support the concurrent search model. If a sear
 - Parent aggregations on [join]({{site.url}}{{site.baseurl}}/field-types/supported-field-types/join/) fields
 - Sampler and Diversified Sampler aggregations.
 
-## Things To Know
+## Things to know
 
 ### The `terminate_after` search parameter
 
@@ -164,11 +164,11 @@ Typically, queries are used with smaller `terminate_after` values and thus compl
 
 ### Sorting
 
-When performing sort operations there are optimizations from Lucene that allow for pruning entire segments which can greatly speed up the request. Whether or not these optimizations are able to kick in depends on both the segment layout as well as the query construction. For concurrent segment search, segments are grouped into segment slices, so in certain cases these sort optimizations may not be applicable to the segment slices. In these cases users may see an increase in query latency when performing sort operations.
+When performing sort operations, optimizations from Lucene that allow for pruning entire segments can greatly speed up the request. Whether these optimizations are able to kick in depends on both the segment layout and the query construction. For concurrent segment search, segments are grouped into segment slices, so in certain cases these sort optimizations may not be applicable to the segment slices. In these cases, you may see an increase in query latency when performing sort operations.
 
-### Terms Aggregations
+### Terms aggregations
 
-When performing concurrent segment search the `shard_size` parameter will be applied at the segment slice level. This may introduce additional document count error, which is correctly calculated by the `doc_count_error_upper_bound` response parameter for such cases.
+When performing concurrent segment search, the `shard_size` parameter will be applied at the segment slice level. This may introduce additional document count error, which is correctly calculated by the `doc_count_error_upper_bound` response parameter for such cases.
 
 ## Developer information: AggregatorFactory changes