Fix stable version links in deprecation admonition (#830)

* Fix stable version links in deprecation admonition

* Take aliases into account

* Proper title for fast cluster restore page

* Add and fix aliases

Author: Simran-B

site/content/arangodb/3.10/components/tools/arangorestore/fast-cluster-restore.md

@@ -1,5 +1,5 @@
 ---
-title: Version 0.3
+title: Fast cluster restore procedure (version 0.3)
 menuTitle: Fast Cluster Restore
 weight: 10
 description: >-

site/content/arangodb/3.11/release-notes/deprecated-and-removed-features.md

@@ -4,6 +4,9 @@ menuTitle: Deprecated and removed features
 weight: 100
 description: >-
   Features listed in this section should no longer be used, because they are considered obsolete and may get removed in a future release
+aliases:
+  - ../develop/drivers/csharp-dotnet # 3.10 -> 3.11
+  - ../components/tools/arangorestore/fast-cluster-restore # 3.10 -> 3.11
 ---
 Features listed on this page should no longer be used because they have been
 deprecated and may get removed in a future release, or have been removed already
@@ -19,13 +22,12 @@ See the [Release notes](_index.md) of the respective versions for
 detailed information about breaking changes before upgrading.
 {{< /info >}}
 
-- **VelocyStream protocol**:
+- **VelocyStream protocol**:\
   ArangoDB's own bi-directional asynchronous binary protocol VelocyStream (VST)
   is deprecated in v3.11 and removed in v3.12.0. Use JSON or VelocyPack over the
   HTTP(S) protocol instead.
 
-- **Little-endian on-disk key format for the RocksDB storage engine**:
-
+- **Little-endian on-disk key format for the RocksDB storage engine**:\
   The little-endian on-disk key format for the RocksDB storage engine is
   deprecated and support will be removed in v3.12. Parallel index creation and
   the `--use-experimental-dump` arangodump option are only available in v3.11
@@ -34,7 +36,7 @@ detailed information about breaking changes before upgrading.
   Only deployments that were set up with the RocksDB storage engine using
   ArangoDB v3.2 or v3.3 and that have been upgraded since then are affected.
 
-- **Pregel features**:
+- **Pregel features**:\
   The following features have been deprecated or removed from Pregel in v3.11:
 
   - The experimental _Custom Pregel_ feature, also known as
@@ -48,82 +50,96 @@ detailed information about breaking changes before upgrading.
   - The `useMemoryMaps` option for Pregel jobs to use memory-mapped files as a
     backing storage for large datasets has been removed.
 
-- **Cloud Migration Tool**:
+- **Cloud Migration Tool**:\
   The `arangosync-migration` tool to move from on-premises to the cloud is not
   available anymore.
 
-- **Leader/Follower Deployment Mode**:
+- **Fast cluster restore procedure**:\
+  The procedure for speeding up _arangorestore_ in a cluster environment has been
+  removed from the documentation because the tool supports threading more
+  multiple collections (from version 3.3 onward) as well as single collections
+  (from version 3.8 onward using the non-enveloped format). For even faster
+  restoration with zero downtime, you can use _arangobackup_ for
+  [Hot Backups](../operations/backup-and-restore.md/#hot-backups).
+
+- **C# / .NET driver**:\
+  The [arangodb-net-standard](https://github.com/ArangoDB-Community/arangodb-net-standard)
+  driver is not an official ArangoDB driver anymore but may still be maintained
+  by the community.
+
+- **Leader/Follower Deployment Mode**:\
   The Leader/Follower deployment mode is deprecated and already removed from
   documentation. Active Failover and OneShard databases in clusters are better
   alternatives.
 
-- **Skiplist and hash indexes**:
+- **Skiplist and hash indexes**:\
   Skiplist and hash indexes have been deprecated in 3.9 and will be removed in a 
   future version of ArangoDB. Currently, they are an alias for a
   [persistent index](../indexes-and-search/indexing/basics.md#persistent-index).
 
-- **Bundled NPM modules**:
+- **Bundled NPM modules**:\
   The bundled NPM modules `aqb`, `chai`, `dedent`, `error-stack-parser`,
   `graphql-sync`, `highlight.js`, `i` (inflect), `iconv-lite`, `joi`,
   `js-yaml`, `lodash`, `minimatch`, `qs`, `semver`, `sinon`, and `timezone`
   have been deprecated in 3.9 and will be removed in a future version of ArangoDB.
   If you want to use NPM modules in your Foxx service, please refer to the
   [Foxx guide](../develop/foxx-microservices/guides/using-node-modules.md).
 
-- **Batch Requests API**:
+- **Batch Requests API**:\
   The [batch request REST API](../develop/http-api/batch-requests.md) is deprecated and will be 
   removed in a future version. Instead of using this API, please use the 
   [HTTP interface for documents](../develop/http-api/documents.md#multiple-document-operations)
   that can insert, update, replace or remove arrays of documents.
 
-- **PUT method in Cursor API**:
+- **PUT method in Cursor API**:\
   The HTTP endpoint `PUT /_api/cursor/<cursor-id>` in the
   [Cursor REST API](../develop/http-api/queries/aql-queries.md) is deprecated and will be
   removed in a future version. Please use the drop-in replacement
   `POST /_api/cursor/<cursor-id>` instead. The POST endpoint is functionally
   equivalent to the PUT endpoint, but does not violate idempotency requirements
   prescribed by the [HTTP specification](https://tools.ietf.org/html/rfc7231#section-4.2).
 
-- **Fulltext indexes**:
+- **Fulltext indexes**:\
   The fulltext index type is deprecated from version 3.10 onwards.
   It is recommended to use [ArangoSearch](../indexes-and-search/arangosearch/_index.md) for advanced full-text search capabilities.
 
-- **Simple Queries**: Idiomatic interface in arangosh to perform trivial queries.
+- **Simple Queries**:\
+  Idiomatic interface in arangosh to perform trivial queries.
   They are superseded by [AQL queries](../aql/_index.md), which can also
   be run in arangosh. AQL is a language on its own and way more powerful than
   *Simple Queries* could ever be. In fact, the (still supported) *Simple Queries*
   are translated internally to AQL, then the AQL query is optimized and run
   against the database in recent versions, because of better performance and
   reduced maintenance complexity.
 
-- **Accessing collections by ID instead of by name**:
+- **Accessing collections by ID instead of by name**:\
   Accessing collections by their internal ID instead of accessing them by name
   is deprecated and highly discouraged. This functionality may be removed in
   future versions of ArangoDB.
 
-- **Old metrics REST API**:
+- **Old metrics REST API**:\
   The old metrics API under `/_admin/metrics` is deprecated and replaced by
   a new one under `/_admin/metrics/v2` from version 3.8.0 on. This step was
   necessary because the old API did not follow quite a few Prometheus
   guidelines for metrics.
 
-- **Statistics REST API**:
+- **Statistics REST API**:\
   The endpoints `/_admin/statistics` and `/_admin/statistics-description`
   are deprecated in favor of the new metrics API under `/_admin/metrics/v2`.
   The metrics API provides a lot more information than the statistics API, so
   it is much more useful.
 
-- **Database target version REST API**:
+- **Database target version REST API**:\
   The `GET /_admin/database/target-version` endpoint is deprecated in favor of the
   more general version API with the endpoint `GET /_api/version`. The endpoint may be
   removed in a future version of ArangoDB.
 
-- **Replication logger-follow REST API**:
+- **Replication logger-follow REST API**:\
   The endpoint `/_api/replication/logger-follow` is deprecated since 3.4.0 and
   may be removed in a future version. Client applications should use the REST 
   API endpoint `/_api/wal/tail` instead, which is available since ArangoDB 3.3.
 
-- **Loading and unloading of collections**:
+- **Loading and unloading of collections**:\
   The JavaScript functions for explicitly loading and unloading collections,
   `db.<collection-name>.load()` and `db.<collection-name>.unload()` and their
   REST API endpoints `PUT /_api/collection/<collection-name>/load` and
@@ -132,7 +148,8 @@ detailed information about breaking changes before upgrading.
   RocksDB storage engine. The load/unload functionality was useful only with
   the MMFiles storage engine, which is not available anymore since 3.7.
 
-- **Actions**: Snippets of JavaScript code on the server-side for minimal
+- **Actions**:\
+  Snippets of JavaScript code on the server-side for minimal
   custom endpoints. Since the Foxx revamp in 3.0, it became really easy to
   write [Foxx Microservices](../develop/foxx-microservices/_index.md), which allow you to define
   custom endpoints even with complex business logic.
@@ -142,7 +159,8 @@ detailed information about breaking changes before upgrading.
   folder). They are not actively removed, they remain on upgrade or backup
   restoration from previous versions.
 
-- **Outdated AQL functions**: The following AQL functions are deprecated and
+- **Outdated AQL functions**:\
+  The following AQL functions are deprecated and
   their usage is discouraged:
   - `IS_IN_POLYGON`
   - `NEAR`
@@ -151,25 +169,27 @@ detailed information about breaking changes before upgrading.
 
   See [Geo functions](../aql/functions/geo.md) for substitutes.
 
-- **`bfs` option** in AQL graph traversal: Using the *bfs* attribute inside
+- **`bfs` option** in AQL graph traversal:\
+  Using the *bfs* attribute inside
   traversal options is deprecated since v3.8.0. The preferred way to start a
   breadth-first traversal is by using the new `order` attribute, and setting it
   to a value of `bfs`.
 
-- **`overwrite` option**: The `overwrite` option for insert operations (either
+- **`overwrite` option**:\
+  The `overwrite` option for insert operations (either
   single document operations or AQL `INSERT` operations) is deprecated in favor
   of the `overwriteMode` option, which provides more flexibility.
 
-- **`minReplicationFactor` collection option**: The `minReplicationFactor`
+- **`minReplicationFactor` collection option**:\
+  The `minReplicationFactor`
   option for collections has been renamed to `writeConcern`. If
   `minReplicationFactor` is specified and no `writeConcern` is set, the
   `minReplicationFactor` value will still be picked up and used as
   `writeConcern` value. However, this compatibility mode will be removed
   eventually, so changing applications from using `minReplicationFactor` to
   `writeConcern` is advised.
 
-- **Outdated startup options**
-
+- **Outdated startup options**:\
   The following _arangod_ startup options are deprecated and will be removed
   in a future version:
   - `--database.old-system-collections` (no need to use it anymore)
@@ -224,12 +244,14 @@ detailed information about breaking changes before upgrading.
   - `--log.use-microtime` (use `--log.time-format` instead)
   - `--log.performance` (use `--log.level` instead)
 
-- **Obsoleted startup options**: Any startup options marked as obsolete can be
+- **Obsoleted startup options**:\
+  Any startup options marked as obsolete can be
   removed in any future version of ArangoDB, so their usage is highly
   discouraged. Their functionality is already removed, but they still exist to
   prevent unknown startup option errors.
 
-- **arangoimp** executable: ArangoDB release packages install an executable named
+- **arangoimp** executable:\
+  ArangoDB release packages install an executable named
   _arangoimp_ as an alias for the _arangoimport_ executable. This is done to 
   provide compatibility with older releases, in which _arangoimport_ did not
   yet exist and was named _arangoimp_. The renaming was actually carried out in
@@ -238,12 +260,14 @@ detailed information about breaking changes before upgrading.
   While the _arangoimport_ executable will remain, the _arangoimp_ alias will be 
   removed in a future version of ArangoDB.
 
-- **HTTP and JavaScript traversal APIs**: The HTTP traversal API
+- **HTTP and JavaScript traversal APIs**:\
+  The HTTP traversal API
   is deprecated since version 3.4.0. The JavaScript traversal module
   `@arangodb/graph/traversal` is also deprecated since then. The preferred way
   to traverse graphs is via AQL.
 
-- **JavaScript-based AQL graph functions**: The following JavaScript-based AQL
+- **JavaScript-based AQL graph functions**:\
+  The following JavaScript-based AQL
   graph functions are deprecated:
   - `arangodb::GRAPH_EDGES`
   - `arangodb::GRAPH_VERTICES`
@@ -264,7 +288,7 @@ detailed information about breaking changes before upgrading.
 
   These functions will be removed in ArangoDB 3.12.
 
-- **Specialized index creation methods in JavaScript API**:
+- **Specialized index creation methods in JavaScript API**:\
   The following JavaScript methods for creating indexes from the ArangoShell
   (_arangosh_) or from within Foxx are deprecated:
   - `collection.ensureHashIndex(...)`