[DOCS] Fix deep paging recommendations

Corrects recommendation to reference the `search_after` parameter,
not API.

docs/reference/search/request/from-size.asciidoc

@@ -41,9 +41,9 @@ multiple shards, each shard must generate its own sorted results. These separate
 results must then be combined and sorted to ensure that the overall sort order
 is correct.
 
-As an alternative to deep paging, we recommend using the
-<<request-body-search-scroll,Scroll>> or
-<<request-body-search-search-after,Search After>> APIs.
+As an alternative to deep paging, we recommend using
+<<request-body-search-scroll,scroll>> or the
+<<request-body-search-search-after,`search_after`>> parameter.
 
 WARNING: {es} uses Lucene's internal doc IDs as tie-breakers. These internal
 doc IDs can be completely different across replicas of the same

docs/reference/search/search.asciidoc

@@ -97,9 +97,9 @@ multiple shards, each shard must generate its own sorted results. These separate
 results must then be combined and sorted to ensure that the overall order is
 correct.
 
-As an alternative to deep paging, we recommend using the
-<<request-body-search-scroll,Scroll>> or
-<<request-body-search-search-after,Search After>> APIs.
+As an alternative to deep paging, we recommend using
+<<request-body-search-scroll,scroll>> or the
+<<request-body-search-search-after,`search_after`>> parameter.
 
 [IMPORTANT]
 ====
@@ -194,9 +194,9 @@ multiple shards, each shard must generate its own sorted results. These separate
 results must then be combined and sorted to ensure that the overall order is
 correct.
 
-As an alternative to deep paging, we recommend using the
-<<request-body-search-scroll,Scroll>> or
-<<request-body-search-search-after,Search After>> APIs.
+As an alternative to deep paging, we recommend using
+<<request-body-search-scroll,scroll>> or the
+<<request-body-search-search-after,`search_after`>> parameter.
 
 [IMPORTANT]
 ====
@@ -317,9 +317,9 @@ multiple shards, each shard must generate its own sorted results. These separate
 results must then be combined and sorted to ensure that the overall order is
 correct.
 
-As an alternative to deep paging, we recommend using the
-<<request-body-search-scroll,Scroll>> or
-<<request-body-search-search-after,Search After>> APIs.
+As an alternative to deep paging, we recommend using
+<<request-body-search-scroll,scroll>> or the
+<<request-body-search-search-after,`search_after`>> parameter.
 
 [IMPORTANT]
 ====
@@ -361,9 +361,9 @@ multiple shards, each shard must generate its own sorted results. These separate
 results must then be combined and sorted to ensure that the overall order is
 correct.
 
-As an alternative to deep paging, we recommend using the
-<<request-body-search-scroll,Scroll>> or
-<<request-body-search-search-after,Search After>> APIs.
+As an alternative to deep paging, we recommend using
+<<request-body-search-scroll,scroll>> or the
+<<request-body-search-search-after,`search_after`>> parameter.
 
 [IMPORTANT]
 ====