[NO ISSUE] Straightening out lots of merge conflicts and inconsistencies in search-request-params

Author: sarahlwelton

modules/search/pages/search-request-params.adoc

@@ -138,24 +138,32 @@ Use `search_after` with `from/offset` and `sort` to control pagination in search
 
 Give a value for each string or JSON object in the <<sort_arr,sort array>> to the `search_after` array.
 You must provide the values in the same order that they appear in the <<sort_arr,sort array>>.
+Your `sort` array must force a total order on your search results.
+
 Values in the `search_after` array must be strings.
 You cannot use `search_after` with numbers or other field data types - if your `sort` array includes fields with a `date` or `number` type, you cannot use `search_after`. 
 Only result relevancy score values can be entered as strings in the array. 
 
 The Search Service starts search result pagination after the document with the values you provide in the array.
 
-Use `search_after` to make the memory requirements of deeper page searches more manageable, when compared to using only `from/offset`.
+For example, if you had a set of 10 documents to sort based on `_id` values of 1-10, with `from` set to `2` and `search_after` set to `8`, documents 9-10 appear on the same page.
+
+To reduce the resource costs of deeper pagination on your Search queries, try to always include your document ID values as the final sort criteria in your `sort` array. 
+Set the `search_after` property to include the values from the last result on your previous page of search results to effectively paginate.
+
+Use `search_after` to make the memory requirements of deeper page searches more manageable, when compared to using only `from`/`offset`. 
 `search_after` lets you start your search results from a specific result, rather than needing to process a number of search results to skip.
 
-To reduce the resource costs of deeper pagination on your Search queries, try to always include your document ID values as the final sort criteria in your <<sort_arr,sort array>>. 
-Set the `search_after` property to include the values from the last result on your previous page of search results to effectively paginate. 
+|[[search_before]]search_before |Array |No a|
 
 NOTE: If you use `search_before` in a search request, you cannot use `search_after`. Both properties are included in the example code to show the correct syntax.
 
 Use `search_before` with `from/offset` and `sort` to control pagination in search results.
 
-Give a value for each string or JSON object in the `sort` array to the `search_before` array.
+Give a value for each string or JSON object in the <<sort_arr,sort array>> to the `search_before` array. 
 You must provide the values in the same order that they appear in the `sort` array.
+Your `sort` array must force a total order on your search results.
+
 Values in the `search_before` array must be strings.
 You cannot use `search_before` with numbers or other field data types - if your `sort` array includes fields with a `date` or `number` type, you cannot use `search_before`. 
 Only result relevancy score values can be entered as strings in the array.
@@ -164,9 +172,12 @@ The Search Service starts search result pagination before the document with the
 
 For example, if you had a set of 10 documents to sort based on `_id` values of 1-10, with `from` set to `2` and `search_before` set to `8`, documents 2-6 appear on the same page.
 
-To reduce the resource costs of deeper pagination on your Search queries, try to always include your document ID values as the final sort criteria in your <<sort_arr,sort array>>. 
+To reduce the resource costs of deeper pagination on your Search queries, try to always include your document ID values as the final sort criteria in your `sort` array. 
 Set the `search_before` property to include the values from the last result on your previous page of search results to effectively paginate. 
 
+Use `search_before` to make the memory requirements of deeper page searches more manageable, when compared to using only `from`/`offset`.
+`search_before` lets you start your search results back from a specific result, rather than needing to process a number of search results to skip.
+
 |[[collections]]collections |Array |No |Contains an array of strings that specify the collections where you want to run the query. 
 
 |====