Fix internal links to anchors

Simran-B · Simran-B · commit 23ad54afdd66 · 2023-12-14T14:52:32.000+01:00
diff --git a/site/content/3.10/arangograph/notebooks.md b/site/content/3.10/arangograph/notebooks.md
@@ -20,7 +20,7 @@ passwords, and endpoint URLs.
 
 ![ArangoGraph Notebooks Architecture](../../images/arangograph-notebooks-architecture.png)
 
-The ArangoGraph Notebook has built-in [ArangoGraph Magic Commands](.#arangograph-magic-commands)
+The ArangoGraph Notebook has built-in [ArangoGraph Magic Commands](#arangograph-magic-commands)
 that answer questions like:
 - What ArangoDB database am I connected to at the moment?
 - What data does the ArangoDB instance contain?
diff --git a/site/content/3.10/develop/http-api/general-request-handling.md b/site/content/3.10/develop/http-api/general-request-handling.md
@@ -139,7 +139,7 @@ HTTP request. The server executes the jobs from the queue asynchronously as fast
 as possible, while clients can continue to do other work.
 
 If the server queue is full (i.e. contains as many jobs as specified by the
-[`--server.maximal-queue-size`](../../components/arangodb-server/options.md#arangodb-server-options)
+[`--server.maximal-queue-size`](../../components/arangodb-server/options.md#--servermaximal-queue-size)
 startup option), then the request is rejected instantly with an HTTP
 `503 Service Unavailable` status code.
 
diff --git a/site/content/3.11/arangograph/notebooks.md b/site/content/3.11/arangograph/notebooks.md
@@ -20,7 +20,7 @@ passwords, and endpoint URLs.
 
 ![ArangoGraph Notebooks Architecture](../../images/arangograph-notebooks-architecture.png)
 
-The ArangoGraph Notebook has built-in [ArangoGraph Magic Commands](.#arangograph-magic-commands)
+The ArangoGraph Notebook has built-in [ArangoGraph Magic Commands](#arangograph-magic-commands)
 that answer questions like:
 - What ArangoDB database am I connected to at the moment?
 - What data does the ArangoDB instance contain?
diff --git a/site/content/3.11/develop/http-api/general-request-handling.md b/site/content/3.11/develop/http-api/general-request-handling.md
@@ -139,7 +139,7 @@ HTTP request. The server executes the jobs from the queue asynchronously as fast
 as possible, while clients can continue to do other work.
 
 If the server queue is full (i.e. contains as many jobs as specified by the
-[`--server.maximal-queue-size`](../../components/arangodb-server/options.md#arangodb-server-options)
+[`--server.maximal-queue-size`](../../components/arangodb-server/options.md#--servermaximal-queue-size)
 startup option), then the request is rejected instantly with an HTTP
 `503 Service Unavailable` status code.
 
diff --git a/site/content/3.11/release-notes/version-3.11/whats-new-in-3-11.md b/site/content/3.11/release-notes/version-3.11/whats-new-in-3-11.md
@@ -1072,7 +1072,7 @@ To enable tracing for traversals and path searches at startup, you can set
 `--log.level graphs=trace`.
 
 To enable or disable it at runtime, you can call the
-[`PUT /_admin/log/level`](../../develop/http-api/monitoring/logs.md#set-the-sersver-log-levels)
+[`PUT /_admin/log/level`](../../develop/http-api/monitoring/logs.md#set-the-server-log-levels)
 endpoint of the HTTP API and set the log level using a request body like
 `{"graphs":"TRACE"}`.
 
diff --git a/site/content/3.12/arangograph/notebooks.md b/site/content/3.12/arangograph/notebooks.md
@@ -20,7 +20,7 @@ passwords, and endpoint URLs.
 
 ![ArangoGraph Notebooks Architecture](../../images/arangograph-notebooks-architecture.png)
 
-The ArangoGraph Notebook has built-in [ArangoGraph Magic Commands](.#arangograph-magic-commands)
+The ArangoGraph Notebook has built-in [ArangoGraph Magic Commands](#arangograph-magic-commands)
 that answer questions like:
 - What ArangoDB database am I connected to at the moment?
 - What data does the ArangoDB instance contain?
diff --git a/site/content/3.12/develop/http-api/general-request-handling.md b/site/content/3.12/develop/http-api/general-request-handling.md
@@ -139,7 +139,7 @@ HTTP request. The server executes the jobs from the queue asynchronously as fast
 as possible, while clients can continue to do other work.
 
 If the server queue is full (i.e. contains as many jobs as specified by the
-[`--server.maximal-queue-size`](../../components/arangodb-server/options.md#arangodb-server-options)
+[`--server.maximal-queue-size`](../../components/arangodb-server/options.md#--servermaximal-queue-size)
 startup option), then the request is rejected instantly with an HTTP
 `503 Service Unavailable` status code.
 
diff --git a/site/content/3.12/release-notes/version-3.11/whats-new-in-3-11.md b/site/content/3.12/release-notes/version-3.11/whats-new-in-3-11.md
@@ -1072,7 +1072,7 @@ To enable tracing for traversals and path searches at startup, you can set
 `--log.level graphs=trace`.
 
 To enable or disable it at runtime, you can call the
-[`PUT /_admin/log/level`](../../develop/http-api/monitoring/logs.md#set-the-sersver-log-levels)
+[`PUT /_admin/log/level`](../../develop/http-api/monitoring/logs.md#set-the-server-log-levels)
 endpoint of the HTTP API and set the log level using a request body like
 `{"graphs":"TRACE"}`.
 
diff --git a/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md b/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md
@@ -93,7 +93,7 @@ memory limit and not just 56% of it.
 
 ## Higher reported memory usage for AQL queries
 
-Due to the [improved memory accounting in v3.12](whats-new-in-3-12.md#improved-memory-accounting),
+Due to the [improved memory accounting in v3.12](whats-new-in-3-12.md#improved-memory-accounting-and-usage),
 certain AQL queries may now get aborted because they exceed the defined
 memory limit but didn't get killed in previous versions. This is because of the
 more accurate memory tracking that reports a higher (actual) usage now. It allows
