DOC-10865: Migrate settings reference to docs-devex

modules/install/pages/upgrade-feature-availability.adoc

@@ -67,11 +67,11 @@ All nodes in the cluster should first be upgraded.
 All nodes in the cluster must be upgraded, before new Analytics-Service features can be used.
 
 | Query Service
-| The xref:tools:query-workbench.adoc#index-advisor[Index Advisor] and xref:settings:query-settings.adoc[Memory-Usage Quota Setting] are usable in mixed mode.
+| The xref:tools:query-workbench.adoc#index-advisor[Index Advisor] and xref:n1ql:n1ql-manage/query-settings.adoc[Memory-Usage Quota Setting] are usable in mixed mode.
 
 xref:n1ql:n1ql-language-reference/flex-indexes.adoc[Flex Indexes], though not a new feature, are usable in mixed mode only if the cluster being upgraded is at least version 6.5.
 
-The xref:n1ql:n1ql-language-reference/cost-based-optimizer.adoc[], xref:n1ql:n1ql-language-reference/transactions.adoc[], and xref:n1ql:n1ql-language-reference/userfun.adoc[] are not usable in mixed mode.
+The xref:n1ql:n1ql-language-reference/cost-based-optimizer.adoc[Cost-Based Optimizer for Queries], xref:n1ql:n1ql-language-reference/transactions.adoc[], and xref:n1ql:n1ql-language-reference/userfun.adoc[] are not usable in mixed mode.
 
 | xref:learn:clusters-and-availability/system-events.adoc[System Events]
 | System Events can only be used when every node in the cluster is running a version of Couchbase Server that is 7.1 or later.

modules/introduction/partials/new-features-76.adoc

@@ -222,19 +222,19 @@ See xref:n1ql:n1ql-language-reference/createcollection.adoc[].
 See xref:rest-api:rest-initialize-cluster.adoc[].
 
 * Named and positional parameters can now be prefixed by `$` or `@` in a query.
-See xref:settings:query-settings.adoc#section_srh_tlm_n1b[Named Parameters and Positional Parameters].
+See xref:n1ql:n1ql-manage/query-settings.adoc#section_srh_tlm_n1b[Named Parameters and Positional Parameters].
 
 * The `system:indexes` catalog now enables you to find the number of replicas configured for each index.
 See xref:n1ql:n1ql-intro/sysinfo.adoc#querying-indexes[Query Indexes].
 
 * The Query Service adds cluster-level and node-level parameters to limit the size of explain plans in the cache.
-See xref:settings:query-settings.adoc#queryPreparedLimit[queryPreparedLimit] and xref:settings:query-settings.adoc#prepared-limit[prepared-limit].
+See xref:n1ql:n1ql-manage/query-settings.adoc#queryPreparedLimit[queryPreparedLimit] and xref:n1ql:n1ql-manage/query-settings.adoc#prepared-limit[prepared-limit].
 
 * The Query Service adds support for sequential scans, controlled by RBAC, which enables querying without an index.
 See xref:learn:services-and-indexes/indexes/query-without-index.adoc[].
 
 * The node-level N1QL Feature Control parameter now accepts hexadecimal strings or decimal integers.
-See xref:settings:query-settings.adoc#n1ql-feat-ctrl[n1ql-feat-ctrl].
+See xref:n1ql:n1ql-manage/query-settings.adoc#n1ql-feat-ctrl[n1ql-feat-ctrl].
 
 * Queries can now read from replica vBuckets when active vBuckets are inaccessible.
 The Query service adds new cluster-level, node-level, and request-level parameters to configure this feature.

modules/learn/pages/data/transactions.adoc

@@ -47,7 +47,7 @@ Transaction APIs support:
 
 Multiple Key-Value and Query DML statements can be used together inside a transaction.
 
-When query DML statements are used within a transaction, xref:settings:query-settings.adoc#transactional-scan-consistency[request_plus] semantics are automatically used to ensure all updates done (and committed if done in a transaction) before the start of the transaction are visible to the query statements within it.
+When query DML statements are used within a transaction, xref:n1ql:n1ql-manage/query-settings.adoc#transactional-scan-consistency[request_plus] semantics are automatically used to ensure all updates done (and committed if done in a transaction) before the start of the transaction are visible to the query statements within it.
 
 == Using Transactions
 
@@ -297,7 +297,7 @@ Transactions can be configured using a number of settings and request-level para
 |See xref:java-sdk:howtos:distributed-acid-transactions-from-the-sdk.adoc#configuration[Setting Durability Level]
 
 |Scan consistency
-|xref:settings:query-settings.adoc#transactional-scan-consistency[Transactional Scan Consistency]
+|xref:n1ql:n1ql-manage/query-settings.adoc#transactional-scan-consistency[Transactional Scan Consistency]
 
 |Request-level Query parameters
 |Request-level parameters when using queries within transactions. See xref:n1ql:n1ql-language-reference/transactions.adoc#settings-and-parameters[{sqlpp} Transactions Settings] for details.
@@ -310,14 +310,14 @@ For more information, see xref:java-sdk:howtos:distributed-acid-transactions-fro
 
 |tximplicit
 |Specifies that a DML statement is a singleton transaction. By default, it is set to false.
-See xref:settings:query-settings.adoc#tximplicit[tximplicit] for details.
+See xref:n1ql:n1ql-manage/query-settings.adoc#tximplicit[tximplicit] for details.
 
 |kvtimeout
-|Specifies the maximum time to wait for a KV operation before timing out. The default value is 2.5s. See xref:settings:query-settings.adoc#kvtimeout[kvtimeout] for details.
+|Specifies the maximum time to wait for a KV operation before timing out. The default value is 2.5s. See xref:n1ql:n1ql-manage/query-settings.adoc#kvtimeout[kvtimeout] for details.
 
 |atrcollection
 |Specifies the collection where the active transaction records (ATRs) and client records are stored. The collection must be present. If not specified, the ATR is stored in the default collection in the default scope in the bucket containing the first mutated document within the transaction. See
-xref:settings:query-settings.adoc#atrcollection_req[atrcollection] for details.
+xref:n1ql:n1ql-manage/query-settings.adoc#atrcollection_req[atrcollection] for details.
 |===
 
 == Related Topics

modules/manage/pages/manage-expiration.adoc

@@ -99,7 +99,7 @@ If you then query the document's expiration metadata, you'll find that it's now
 ]
 ----
 
-You can prevent Couchbase Server from clearing the expiration value by using the xref:settings:query-settings.adoc#preserve_expiry[`preserve_expiry`] request-level parameter. 
+You can prevent Couchbase Server from clearing the expiration value by using the xref:n1ql:n1ql-manage/query-settings.adoc#preserve_expiry[preserve_expiry] request-level parameter. 
 
 You can directly preserve a document's expiration when mutating it. 
 To preserve the expiration, set the expiration metadata to the document's current expiration value.  

modules/manage/pages/manage-settings/general-settings.adoc

@@ -266,7 +266,7 @@ Note that KV range scans cannot currently be started on a replica vBucket.
 If a query uses sequential scan and a data node becomes unavailable, the query might return an error, even if read from replica is enabled for the request.
 --
 
-For additional details on all the Query settings in the lower section of the panel, refer to xref:settings:query-settings.adoc[Settings and Parameters].
+For additional details on all the Query settings in the lower section of the panel, refer to xref:n1ql:n1ql-manage/query-settings.adoc[].
 
 [#index-storage-mode]
 === Index Storage Mode
@@ -511,7 +511,7 @@ To set cluster-level query settings, for example the log level and the maximum p
 --max-parallelism 4
 ----
 
-For additional details on the cluster-level query settings, refer to xref:settings:query-settings.adoc[Settings and Parameters].
+For additional details on the cluster-level query settings, refer to xref:n1ql:n1ql-manage/query-settings.adoc[Settings and Parameters].
 
 [#rebalance-settings-via-cli]
 === Rebalance Settings via CLI

modules/manage/pages/monitor/monitoring-n1ql-query.adoc

@@ -100,8 +100,7 @@ Use the following query parameters to enable, disable, and control the monitorin
 * profile
 * controls
 
-For more details and examples, refer to the
-xref:settings:query-settings.adoc[Query Settings] section.
+For more details and examples, see xref:n1ql:n1ql-manage/query-settings.adoc[].
 
 === Enable Settings for a Query Engine
 
@@ -113,7 +112,7 @@ You need to provide correct credentials, IP address, and port details of your se
 +
 [source,sh]
 ----
-include::settings:example$save-node-level-settings.sh[tag=curl]
+include::n1ql:example$settings/save-node-level-settings.sh[tag=curl]
 ----
 +
 [source,sh]
@@ -123,7 +122,7 @@ cat  ./query_settings.json
 +
 [source,json]
 ----
-include::settings:example$node-level-settings.jsonc[]
+include::n1ql:example$settings/node-level-settings.jsonc[]
 ----
 
 . Set current query settings profile:
@@ -149,7 +148,7 @@ curl http://localhost:8093/admin/settings -u user:pword \
 +
 [source,sh]
 ----
-include::settings:example$node-level-settings.sh[tag=curl]
+include::n1ql:example$settings/node-level-settings.sh[tag=curl]
 ----
 +
 [source,json]

modules/n1ql/pages/n1ql-rest-api/intro.adoc

@@ -44,4 +44,4 @@ include::rest-api:partial$rest-query-service-table.adoc[tags=query-functions]
 
 == See Also
 
-For an explanation of how cluster-level settings, node-level settings, and request-level parameters interact, see xref:settings:query-settings.adoc[].
+For an explanation of how cluster-level settings, node-level settings, and request-level parameters interact, see xref:n1ql:n1ql-manage/query-settings.adoc[].