minor xref fixes for fts (#2493)

* fix syntax error in xref

* fix xref to fts-cluster-options.adoc

* resolve dead fts link to bleveMaxResultWindow

update dead reference from
xref:fts:fts-response-object-schema.adoc#request[maximum number of full text search results]
to
xref:fts:fts-advanced-settings-bleveMaxResultWindow.adoc[bleveMaxResultWindow]

* informational update

As per Abhinav corrections

Author: jon-strabala

modules/ROOT/nav.adoc

@@ -243,7 +243,7 @@
   *** xref:fts:fts-architecture-scatter-gather.adoc[Scatter Gather]
   *** xref:fts:fts-architecture-ports-used.adoc[Ports Used By FTS]
   *** xref:fts:fts-rebalance-failover.adoc[Rebalance/Failover]
- ** xref:fts:fts-cluster-operations.adoc[Cluster Level Options]
+ ** xref:fts:fts-cluster-options.adoc[Cluster Level Options]
   *** xref:fts:fts-advanced-settings-bleveMaxResultWindow.adoc[bleveMaxResultWindow]
   *** xref:fts:fts-advanced-settings-bleveMaxClauseCount.adoc[bleveMaxClauseCount]
   *** xref:fts:fts-advanced-settings-maxFeedsPerDCPAgent.adoc[maxFeedsPerDCPAgent]

modules/fts/pages/fts-supported-queries-geo-point-distance.adoc

@@ -1,7 +1,7 @@
 = Creating a Query: Radius-Based
 
 This section and those following, provide examples of the query-bodies required to make geospatial queries with the Couchbase REST API.
-Note that more detailed information on performing queries with the Couchbase REST API can be found in xref:fts-fts-searching-with-curl-http-requests.adoc[Searching with the REST API]; which shows how to use the full `curl` command and how to incorporate query-bodies into it.
+Note that more detailed information on performing queries with the Couchbase REST API can be found in xref:fts-searching-with-curl-http-requests.adoc[Searching with the REST API]; which shows how to use the full `curl` command and how to incorporate query-bodies into it.
 
 The following query-body specifies a longitude of `-2.235143` and a latitude of `53.482358`.
 The target-field `geo` is specified, as is a `distance` of `100` miles: this is the radius within which target-locations must reside for their documents to be returned.

modules/n1ql/pages/n1ql-language-reference/searchfun.adoc

@@ -142,9 +142,10 @@ For more details, refer to xref:fts:fts-sorting.adoc[Sorting Query Results].
 
 [NOTE]
 ====
-When specifying a complete full text search request with the N1QL SEARCH() function, if the value of the `size` parameter is greater than the xref:fts:fts-response-object-schema.adoc#request[maximum number of full text search results], the query ignores the `size` parameter and returns all matching results.
-
-This is different to the behavior of a complete full text search request in the Search service, where the query returns an error if the value of the `size` parameter is greater than the maximum number of full text search results.
+* If size/from (pagination) settings aren't set, the search index will "stream" all qualifying results to N1QL which can perform further filtering.
+* If `size/limit`, `from/offset` are set within the search request within the SEARCH function, FTS handles the pagination.
+* N1QL can hand down LIMIT/OFFSET settings to FTS. If this `limit+offset <= bleveMaxResultWindow` - then the FTS index is deemed pageable and N1QL hands down these settings to FTS. If not, then FTS will stream results to N1QL and N1QL will be responsible for pagination and ordering.
+* The default value for the cluster wide xref:fts:fts-advanced-settings-bleveMaxResultWindow.adoc[bleveMaxResultWindow] setting is 10000. 
 ====
 |===
 +