Fix links

Author: Simran-B

3.10/appendix-java-script-modules-request.md

@@ -66,7 +66,7 @@ The request function takes the following options:
 * *json*: if `true`, *body* will be serialized to a JSON string and the *Content-Type* header will be set to `"application/json"`. Additionally the response body will also be parsed as JSON (unless *encoding* is set to `null`). Default: `false`.
 * *form* (optional): when set to a string or object and no *body* has been set, *body* will be set to a querystring representation of that value and the *Content-Type* header will be set to `"application/x-www-form-urlencoded"`. Also see *useQuerystring*.
 * *auth* (optional): an object with the properties *username* and *password* for HTTP Basic authentication or the property *bearer* for HTTP Bearer token authentication.
-* *sslProtocol* (optional): which tls version should be used to connect to the url. The default is `4` which is TLS 1.0. See [SSL protocol](programs-arangod-ssl.html#ssl-protocol) for more opitions.
+* *sslProtocol* (optional): which tls version should be used to connect to the url. The default is `4` which is TLS 1.0. See [SSL protocol](programs-arangod-options.html#--sslprotocol) for more options.
 * *followRedirect*: whether HTTP 3xx redirects should be followed. Default: `true`.
 * *maxRedirects*: the maximum number of redirects to follow. Default: `10`.
 * *encoding*: encoding to be used for the response body. If set to `null`, the response body will be returned as a `Buffer`. Default: `"utf-8"`.

3.10/aql/common-errors.md

@@ -410,7 +410,7 @@ FOR name IN Names
 You can set the startup option `--query.allow-collections-in-expressions` to
 *false* to disallow collection names in arbitrary places in AQL expressions
 to prevent such mistakes. Also see
-[ArangoDB Server Query Options](../programs-arangod-query.html#allowing-the-usage-of-collection-names-in-aql-expressions)
+[ArangoDB Server Query Options](../programs-arangod-options.html#--queryallow-collections-in-expressions)
 
 {%- comment %}
 Rename to Error Sources?

3.10/aql/extending.md

@@ -57,9 +57,9 @@ of these resources, your query may abort with a
 [**cluster backend unavailable**](../appendix-error-codes.html) error.
 
 To overcome these mentioned limitations, you may want to increase the
-[number of available V8 contexts](../programs-arangod-javascript.html#v8-contexts)
+[number of available V8 contexts](../programs-arangod-options.html#--javascriptv8-contexts)
 (at the expense of increased memory usage), and the
-[number of available server threads](../programs-arangod-server.html#server-threads).
+[number of available server threads](../programs-arangod-options.html#--serverthreads).
 
 In addition, modification of global JavaScript variables from inside UDFs is 
 unsupported, as is reading or changing the data of any collection or running

3.10/aql/fundamentals-type-value-order.md

@@ -78,7 +78,7 @@ result is defined as follows:
 - boolean: *false* is less than *true*
 - number: numeric values are ordered by their cardinal value
 - string: string values are ordered using a localized comparison, using the configured
-  [server language](../programs-arangod-general.html#default-language)
+  [server language](../programs-arangod-options.html#--defaultlanguage)
   for sorting according to the alphabetical order rules of that language
 
 Note: unlike in SQL, *null* can be compared to any value, including *null*

3.10/aql/invocation-with-arangosh.md

@@ -270,7 +270,7 @@ the entire query result in RAM, a streaming query should be used.
   (i.e. `FOR i IN 1..100`), each row is one of such temporary values. 
   This parameter is experimental and is only taken into account if a path for a
   directory to store the temporary data is provided with the
-  [`--temp.intermediate-results-path` startup option](../programs-arangod-query.html#aql-query-with-spilling-input-data-to-disk).
+  [`--temp.intermediate-results-path` startup option](../programs-arangod-options.html#--tempintermediate-results-path).
   Default value: `5000000` rows.
 
 - `spillOverThresholdMemoryUsage`: This parameter allows for input data and 
@@ -279,7 +279,7 @@ the entire query result in RAM, a streaming query should be used.
   is used for decreasing the memory usage during the query execution. This 
   parameter is experimental and is only taken into account if a path for a 
   directory to store the temporary data is provided with the
-  [`--temp.intermediate-results-path` startup option](../programs-arangod-query.html#aql-query-with-spilling-input-data-to-disk).
+  [`--temp.intermediate-results-path` startup option](../programs-arangod-options.html#--tempintermediate-results-path).
   Default value: 128MB.
 
 ## With `db._createStatement()` (ArangoStatement)

3.10/aql/operations-with.md

@@ -48,7 +48,7 @@ vertex collections as part of graph traversals.
 
 You can enable the `--query.require-with` startup option to make single server
 instances require `WITH` declarations like cluster deployments to ease development,
-see [Requiring `WITH` statements](../programs-arangod-query.html#requiring-with-statements).
+see [Requiring `WITH` statements](../programs-arangod-options.html#--queryrequire-with).
 
 Dynamic access via the `DOCUMENT()` function does not require you to list the
 involved collections. Using named graphs in traversals (`GRAPH "graph-name"`)

3.10/arangosearch-views.md

@@ -257,7 +257,7 @@ is used by these writers (in terms of "writers pool") one can use
   Maximum memory byte size per writer (segment) before a writer (segment) flush is
   triggered. `0` value turns off this limit for any writer (buffer) and data will
   be flushed periodically based on the
-  [value defined for the flush thread](programs-arangod-server.html#data-source-flush-synchronization)
+  [value defined for the flush thread](programs-arangod-options.html#--serverflush-interval)
   (ArangoDB server startup option). `0` value should be used carefully due to high
   potential memory consumption.
 

3.10/architecture-storage-engines.md

@@ -53,11 +53,11 @@ The entire user transaction will not necessarily have ACID properties in this ca
 The threshold values for transaction sizes can be configured globally using the
 startup options
 
-- [`--rocksdb.intermediate-commit-size`](programs-arangod-rocksdb.html#non-pass-through-options)
+- [`--rocksdb.intermediate-commit-size`](programs-arangod-options.html#--rocksdbintermediate-commit-size)
 
-- [`--rocksdb.intermediate-commit-count`](programs-arangod-rocksdb.html#non-pass-through-options)
+- [`--rocksdb.intermediate-commit-count`](programs-arangod-options.html#--rocksdbintermediate-commit-count)
 
-- [`--rocksdb.max-transaction-size`](programs-arangod-rocksdb.html#non-pass-through-options)
+- [`--rocksdb.max-transaction-size`](programs-arangod-options.html#--rocksdbmax-transaction-size)
 
 It is also possible to override these thresholds per transaction.
 

3.10/deployment-production-checklist.md

@@ -35,7 +35,7 @@ ArangoDB
     machine, adjust the [`ARANGODB_OVERRIDE_DETECTED_TOTAL_MEMORY`](programs-arangod-env-vars.html)
     environment variable accordingly.
   - For versions prior to 3.8, make sure to change the
-    [`--query.memory-limit`](programs-arangod-query.html#limiting-memory-usage-of-aql-queries)
+    [`--query.memory-limit`](programs-arangod-options.html#--querymemory-limit)
     query option according to the node size and workload.
   - Disable swap space to avoid slowdown which can result in servers being incorrectly 
     detected as failed.

3.10/features-enterprise-edition.md

@@ -108,4 +108,4 @@ features outlined below. For additional information, see
 - **Advanced Encryption and Security Configuration**:
   Key rotation for [JWT secrets](http/general.html#hot-reload-of-jwt-secrets)
   and [on-disk encryption](http/administration-and-monitoring.html#encryption-at-rest),
-  as well as [Server Name Indication (SNI)](programs-arangod-ssl.html#server-name-indication-sni).
+  as well as [Server Name Indication (SNI)](programs-arangod-options.html#--sslserver-name-indication).

3.10/http/general.md

@@ -150,7 +150,7 @@ in client requests. ArangoDB supports authentication via HTTP Basic or JWT.
 Authentication is turned on by default for all internal database APIs but
 turned off for custom Foxx apps. To toggle authentication for incoming
 requests to the internal database APIs, use the option
-[--server.authentication](../programs-arangod-server.html#enabledisable-authentication).
+[--server.authentication](../programs-arangod-options.html#--serverauthentication).
 This option is turned on by default so authentication is required for the
 database APIs.
 
@@ -161,7 +161,7 @@ requests (see [Cross Origin Resource Sharing requests](#cross-origin-resource-sh
 The response to an HTTP OPTIONS request will be generic and not expose any private data.
 
 There is an additional option to control authentication for custom Foxx apps. The option
-[--server.authentication-system-only](../programs-arangod-server.html#enabledisable-authentication-for-system-api-requests-only)
+[--server.authentication-system-only](../programs-arangod-options.html#--serverauthentication-system-only)
 controls whether authentication is required only for requests to the internal
 database APIs and the admin interface. It is turned on by default, meaning that
 other APIs (this includes custom Foxx apps) do not require authentication.

3.10/indexing-persistent.md

@@ -303,7 +303,7 @@ will match.
 ## Persistent Indexes and Server Language
 
 The order of index entries in persistent indexes adheres to the configured
-[server language](programs-arangod-general.html#default-language).
+[server language](programs-arangod-options.html#--defaultlanguage).
 If, however, the server is restarted with a different language setting as when
 the persistent index was created, not all documents may be returned anymore and
 the sort order of those which are returned can be wrong (whenever the persistent

3.10/installation-linux-osconfiguration.md

@@ -32,7 +32,7 @@ sudo locale-gen "en_US.UTF-8"
 Your distribution may also provide a frontend for doing so, for instance
 [`dpkg-reconfigure locales` on Debian](https://wiki.debian.org/Locale){:target="_blank"}.
 
-If you don't set a [default language](programs-arangod-general.html#default-language)
+If you don't set a [default language](programs-arangod-options.html#--defaultlanguage)
 for the server explicitly, ArangoDB will use the default locale of your system.
 
 {% hint 'warning' %}

3.10/release-notes-new-features310.md

@@ -1043,7 +1043,7 @@ arangod --temp.intermediate-results-path "tempDir"
 --temp.intermediate-results-spillover-threshold-memory-usage 134217728
 ```
 
-For more information, refer to the [Query invocation](aql/invocation-with-arangosh.html#additional-parameters-for-spilling-data-from-the-query-onto-disk) and [Query options](programs-arangod-query.html#aql-query-with-spilling-input-data-to-disk) topics.
+For more information, refer to the [Query invocation](aql/invocation-with-arangosh.html#additional-parameters-for-spilling-data-from-the-query-onto-disk) and [Query options](programs-arangod-options.html#--tempintermediate-results-path) topics.
 
 ## Internal changes
 

3.10/release-notes-new-features36.md

@@ -658,13 +658,13 @@ Startup options
 
 ### Metrics API option
 
-The new [option](programs-arangod-server.html#metrics-api)
+The new [option](programs-arangod-options.html#--servermetrics-api)
 `--server.export-metrics-api` allows you to disable the metrics API by setting
 it to `false`, which is otherwise turned on by default.
 
 ### OneShard cluster option
 
-The [option](programs-arangod-cluster.html#more-advanced-options)
+The [option](programs-arangod-options.html#--clusterforce-one-shard)
 `--cluster.force-one-shard` enables the new OneShard feature for the entire
 cluster deployment. It forces the cluster into creating all future collections
 with only a single shard and using the same DB-Server as these collections'
@@ -674,7 +674,7 @@ transactional guarantees.
 
 ### Cluster upgrade option
 
-The new [option](programs-arangod-cluster.html#upgrade) `--cluster.upgrade`
+The new [option](programs-arangod-options.html#--clusterupgrade) `--cluster.upgrade`
 toggles the cluster upgrade mode for Coordinators. It supports the following
 values:
 
@@ -765,7 +765,7 @@ For example, to turn off the rule `use-indexes-for-sort`, use
 
     --query.optimizer-rules "-use-indexes-for-sort"
 
-The purpose of this [startup option](programs-arangod-query.html#optimizer-rule-defaults)
+The purpose of this [startup option](programs-arangod-options.html#--queryoptimizer-rules)
 is to be able to enable potential future experimental optimizer rules, which
 may be shipped in a disabled-by-default state.
 
@@ -791,7 +791,7 @@ Hot Backup
 TLS v1.3
 --------
 
-Added support for TLS 1.3 for the [arangod server](programs-arangod-ssl.html#ssl-protocol)
+Added support for TLS 1.3 for the [arangod server](programs-arangod-options.html#--sslprotocol)
 and the client tools (also added to v3.5.1).
 
 The arangod server can be started with option `--ssl.protocol 6` to make it require

3.10/release-notes-new-features37.md

@@ -566,7 +566,7 @@ See: [HTTP Switching Protocols](http/general.html#switching-protocols)
 
 Sometimes it is desirable to have the same server use different server keys
 and certificates when it is contacted under different names. This is possible
-with the [Server Name Indication](programs-arangod-ssl.html#server-name-indication-sni)
+with the [Server Name Indication](programs-arangod-options.html#--sslserver-name-indication)
 (SNI) TLS extension. It is now supported by ArangoDB using a new startup option
 `--ssl.server-name-indication`.
 

3.10/transactions-stream-transactions.md

@@ -67,7 +67,7 @@ connections were interrupted.
 A given transaction is intended to be used **serially**. No concurrent requests
 using the same transaction ID should be issued by the client. The server can
 make some effort to serialize certain operations (see
-[Streaming Lock Timeout](programs-arangod-transaction.html#streaming-lock-timeout)),
+[Streaming Lock Timeout](programs-arangod-options.html#--transactionstreaming-lock-timeout)),
 however, this degrades the server's performance and may lead to sporadic
 errors with code `28` (locked).
 

3.10/tutorials-reduce-memory-footprint.md

@@ -174,7 +174,7 @@ Statistics
 ----------
 
 The server collects
-[statistics](programs-arangod-server.html#toggling-server-statistics) regularly,
+[statistics](programs-arangod-options.html#--serverstatistics) regularly,
 which is displayed in the web interface. You will have a light query load every
 few seconds, even if your application is idle, because of the statistics. If required, you can 
 turn it off via:
@@ -272,7 +272,7 @@ The default for this option is 4, which means that a Coordinator with `t`
 scheduler threads can execute up to `4 * t` requests concurrently. The
 minimal value for this option is 1.
 
-Also see [Preventing cluster overwhelm](programs-arangod-server.html#preventing-cluster-overwhelm).
+Also see the [_arangod_ startup options](programs-arangod-options.html#--serverongoing-low-priority-multiplier).
 
 CPU usage
 ---------

3.10/upgrading-manually-active-failover.md

@@ -20,7 +20,7 @@ Preparations
 
 The ArangoDB installation packages (e.g. for Debian or Ubuntu) set up a
 convenient standalone instance of `arangod`. During installation, this instance's
-database will be upgraded (see [`--database.auto-upgrade`](programs-arangod-database.html#auto-upgrade))
+database will be upgraded (see [`--database.auto-upgrade`](programs-arangod-options.html#--databaseauto-upgrade))
 and the service will be (re)started.
 
 You have to make sure that your _Active Failover_ deployment is independent of this

3.10/upgrading-manually-cluster.md

@@ -19,7 +19,7 @@ Preparations
 
 The ArangoDB installation packages (e.g. for Debian or Ubuntu) set up a
 convenient standalone instance of `arangod`. During installation, this instance's
-database will be upgraded (see [`--database.auto-upgrade`](programs-arangod-database.html#auto-upgrade))
+database will be upgraded (see [`--database.auto-upgrade`](programs-arangod-options.html#--databaseauto-upgrade))
 and the service will be (re)started.
 
 You have to make sure that your _cluster_ deployment is independent of this

3.11/appendix-java-script-modules-request.md

@@ -66,7 +66,7 @@ The request function takes the following options:
 * *json*: if `true`, *body* will be serialized to a JSON string and the *Content-Type* header will be set to `"application/json"`. Additionally the response body will also be parsed as JSON (unless *encoding* is set to `null`). Default: `false`.
 * *form* (optional): when set to a string or object and no *body* has been set, *body* will be set to a querystring representation of that value and the *Content-Type* header will be set to `"application/x-www-form-urlencoded"`. Also see *useQuerystring*.
 * *auth* (optional): an object with the properties *username* and *password* for HTTP Basic authentication or the property *bearer* for HTTP Bearer token authentication.
-* *sslProtocol* (optional): which tls version should be used to connect to the url. The default is `4` which is TLS 1.0. See [SSL protocol](programs-arangod-ssl.html#ssl-protocol) for more opitions.
+* *sslProtocol* (optional): which tls version should be used to connect to the url. The default is `4` which is TLS 1.0. See [SSL protocol](programs-arangod-options.html#--sslprotocol) for more options.
 * *followRedirect*: whether HTTP 3xx redirects should be followed. Default: `true`.
 * *maxRedirects*: the maximum number of redirects to follow. Default: `10`.
 * *encoding*: encoding to be used for the response body. If set to `null`, the response body will be returned as a `Buffer`. Default: `"utf-8"`.

3.11/aql/common-errors.md

@@ -410,7 +410,7 @@ FOR name IN Names
 You can set the startup option `--query.allow-collections-in-expressions` to
 *false* to disallow collection names in arbitrary places in AQL expressions
 to prevent such mistakes. Also see
-[ArangoDB Server Query Options](../programs-arangod-query.html#allowing-the-usage-of-collection-names-in-aql-expressions)
+[ArangoDB Server Query Options](../programs-arangod-options.html#--queryallow-collections-in-expressions)
 
 {%- comment %}
 Rename to Error Sources?

3.11/aql/extending.md

@@ -57,9 +57,9 @@ of these resources, your query may abort with a
 [**cluster backend unavailable**](../appendix-error-codes.html) error.
 
 To overcome these mentioned limitations, you may want to increase the
-[number of available V8 contexts](../programs-arangod-javascript.html#v8-contexts)
+[number of available V8 contexts](../programs-arangod-options.html#--javascriptv8-contexts)
 (at the expense of increased memory usage), and the
-[number of available server threads](../programs-arangod-server.html#server-threads).
+[number of available server threads](../programs-arangod-options.html#--serverthreads).
 
 In addition, modification of global JavaScript variables from inside UDFs is 
 unsupported, as is reading or changing the data of any collection or running

3.11/aql/fundamentals-type-value-order.md

@@ -78,7 +78,7 @@ result is defined as follows:
 - boolean: *false* is less than *true*
 - number: numeric values are ordered by their cardinal value
 - string: string values are ordered using a localized comparison, using the configured
-  [server language](../programs-arangod-general.html#default-language)
+  [server language](../programs-arangod-options.html#--defaultlanguage)
   for sorting according to the alphabetical order rules of that language
 
 Note: unlike in SQL, *null* can be compared to any value, including *null*

3.11/aql/invocation-with-arangosh.md

@@ -270,7 +270,7 @@ the entire query result in RAM, a streaming query should be used.
   (i.e. `FOR i IN 1..100`), each row is one of such temporary values. 
   This parameter is experimental and is only taken into account if a path for a
   directory to store the temporary data is provided with the
-  [`--temp.intermediate-results-path` startup option](../programs-arangod-query.html#aql-query-with-spilling-input-data-to-disk).
+  [`--temp.intermediate-results-path` startup option](../programs-arangod-options.html#--tempintermediate-results-path).
   Default value: `5000000` rows.
 
 - `spillOverThresholdMemoryUsage`: This parameter allows for input data and 
@@ -279,7 +279,7 @@ the entire query result in RAM, a streaming query should be used.
   is used for decreasing the memory usage during the query execution. This 
   parameter is experimental and is only taken into account if a path for a 
   directory to store the temporary data is provided with the
-  [`--temp.intermediate-results-path` startup option](../programs-arangod-query.html#aql-query-with-spilling-input-data-to-disk).
+  [`--temp.intermediate-results-path` startup option](../programs-arangod-options.html#--tempintermediate-results-path).
   Default value: 128MB.
 
 ## With `db._createStatement()` (ArangoStatement)