Remove more references to obsolete versions (#1169)

Co-authored-by: Paula Mihu <97217318+nerpaula@users.noreply.github.com>

Author: Simran-B

3.10/appendix-glossary.md

@@ -17,7 +17,7 @@ Collections contain documents of a specific type. There are currently two types:
 Collection Identifier
 ---------------------
 
-A collection identifier identifies a collection in a database. It is a string value and is unique within the database. Up to including ArangoDB 1.1, the collection identifier has been a client's primary means to access collections. Starting with ArangoDB 1.2, clients should instead use a collection's unique name to access a collection instead of its identifier.
+A collection identifier identifies a collection in a database. It is a string value and is unique within the database. Clients should use a collection's unique name to access a collection instead of its identifier.
 
 ArangoDB currently uses 64bit unsigned integer values to maintain collection ids internally. When returning collection ids to clients, ArangoDB will put them into a string to ensure the collection id is not clipped by clients that do not support big integers. Clients should treat the collection ids returned by ArangoDB as
 opaque strings when they store or use it locally.
@@ -179,7 +179,7 @@ Fulltext Index
 The fulltext index type is deprecated from version 3.10 onwards.
 {% endhint %}
 
-A fulltext index can be used to find words, or prefixes of words inside documents. A fulltext index can be defined on one attribute only, and will include all words contained in documents that have a textual value in the index attribute. Since ArangoDB 2.6 the index will also include words from the index attribute if the index attribute is an array of strings, or an object with string value members.
+A fulltext index can be used to find words, or prefixes of words inside documents. A fulltext index can be defined on one attribute only, and will include all words contained in documents that have a textual value in the index attribute. The index will also include words from the index attribute if the index attribute is an array of strings, or an object with string value members.
 
 For example, given a fulltext index on the `translations` attribute and the following documents, then searching for `лиса` using the fulltext index would return only the first document. Searching for the index for the exact string `Fox` would return the first two documents, and searching for `prefix:Fox` would return all three documents:
 

3.10/architecture-deployment-modes-active-failover-architecture.md

@@ -58,7 +58,7 @@ A multi-datacenter solution currently supported is the Datacenter-to-Datacenter
 {% endhint %}
 
 Operative Behavior
--------------------
+------------------
 
 In contrast to the normal behavior of a single-server instance, the Active-Failover
 mode will change the behavior of ArangoDB in some situations.

3.10/data-modeling-collections.md

@@ -61,7 +61,7 @@ This method is a database method and is documented in detail at [Database Method
 
 ### Synchronous replication
 
-Starting in ArangoDB 3.0, the distributed version offers synchronous
+The distributed version offers synchronous
 replication, which means that there is the option to replicate all data
 automatically within the ArangoDB cluster. This is configured for sharded
 collections on a per collection basis by specifying a "replication factor"

3.10/data-modeling-documents-document-address.md

@@ -87,9 +87,8 @@ Document Revision
 Multiple Documents in a single Command
 --------------------------------------
 
-Beginning with ArangoDB 3.0 the basic document API has been extended
-to handle not only single documents but multiple documents in a single
-command. This is crucial for performance, in particular in the cluster
+The document API can handle not only single documents but multiple documents in
+a single command. This is crucial for performance, in particular in the cluster
 situation, in which a single request can involve multiple network hops
 within the cluster. Another advantage is that it reduces the overhead of
 individual network round trips between the client

3.10/foxx-reference-routers-request.md

@@ -20,7 +20,7 @@ The request object specifies the following properties:
 * **arangoVersion**: `number`
 
   The numeric value of the `x-arango-version` header or the numeric version
-  of the ArangoDB server (e.g. `30102` for version 3.1.2) if no valid header
+  of the ArangoDB server (e.g. `30807` for version 3.8.7) if no valid header
   was provided.
 
 * **auth**: `object | null`

3.10/http/async-results-management.md

@@ -33,7 +33,7 @@ and [HttpJobPutCancel](#managing-async-results-via-http) for details.
 
 ### Fire and Forget
 
-To mitigate client blocking issues, ArangoDB since version 1.4. offers a generic mechanism 
+To mitigate client blocking issues, offers a generic mechanism 
 for non-blocking requests: if clients add the HTTP header *x-arango-async: true* to their
 requests, ArangoDB will put the request into an in-memory task queue and return an HTTP 202
 (accepted) response to the client instantly. The server will execute the tasks from

3.10/http/collection.md

@@ -23,20 +23,15 @@ Collection Identifier
 ---------------------
 
 A collection identifier lets you refer to a collection in a database. 
-It is a string value and is unique within the database. Up to including 
-ArangoDB 1.1, the collection identifier has been a client's primary 
-means to access collections. Starting with ArangoDB 1.2, clients should 
-instead use a collection's unique name to access a collection instead of 
-its identifier.
+It is a string value and is unique within the database. Clients should use
+a collection's unique name to access a collection instead of its identifier.
 ArangoDB currently uses 64bit unsigned integer values to maintain 
 collection ids internally. When returning collection ids to clients, 
 ArangoDB will put them into a string to ensure the collection id is not 
 clipped by clients that do not support big integers. Clients should treat 
 the collection ids returned by ArangoDB as opaque strings when they store 
 or use them locally.
 
-Note: collection ids have been returned as integers up to including ArangoDB 1.1
-
 Collection Name
 ---------------
 

3.10/http/document-address-and-etag.md

@@ -104,9 +104,8 @@ The revision of a document can be checking using the HTTP method *HEAD*.
 Multiple Documents in a single Request
 --------------------------------------
 
-Beginning with ArangoDB 3.0 the basic document API has been extended
-to handle not only single documents but multiple documents in a single
-request. This is crucial for performance, in particular in the cluster
+The document API can handle not only single documents but multiple documents in
+a single request. This is crucial for performance, in particular in the cluster
 situation, in which a single request can involve multiple network hops
 within the cluster. Another advantage is that it reduces the overhead of
 the HTTP protocol and individual network round trips between the client

3.10/http/replications-replication-logger.md

@@ -1,20 +1,19 @@
 ---
 layout: default
-description: Previous versions of ArangoDB allowed starting, stopping and configuring thereplication logger
+description: >-
+  You can query the current state of the logger and fetch the latest changes
+  written by the logger
 ---
 Replication Logger Commands
 ===========================
 
-Previous versions of ArangoDB allowed starting, stopping and configuring the
-replication logger. These commands are superfluous in ArangoDB 2.2 as all
-data-modification operations are written to the server's write-ahead log and are
-not handled by a separate logger anymore.
+All data-modification operations are written to the server's write-ahead log and are
+not handled by a separate replication logger.
 
-The only useful operations remaining since ArangoDB 2.2 are to query the current state
-of the logger and to fetch the latest changes written by the logger. The operations
-will return the state and data from the write-ahead log.
+You can query the current state of the logger and fetch the latest changes
+written by the logger. The operations return the state and data from the
+write-ahead log.
 
-<!-- arangod/RestHandler/RestReplicationHandler.cpp -->
 {% docublock get_api_replication_logger_return_state %}
 
 To query the latest changes logged by the replication logger, the HTTP interface
@@ -23,13 +22,13 @@ also provides the `logger-follow` method.
 This method should be used by replication clients to incrementally fetch updates 
 from an ArangoDB database.
 
-<!-- arangod/RestHandler/RestReplicationHandler.cpp -->
 {% docublock get_api_replication_logger_follow %}
 
 To check what range of changes is available (identified by tick values), the HTTP
 interface provides the methods `logger-first-tick` and `logger-tick-ranges`.
 Replication clients can use the methods to determine if certain data (identified
 by a tick *date*) is still available on the Leader.
+
 {% docublock get_api_replication_logger_first_tick %}
-{% docublock get_api_replication_logger_tick_ranges %}
 
+{% docublock get_api_replication_logger_tick_ranges %}

3.10/indexing-fulltext.md

@@ -19,7 +19,7 @@ Introduction to Fulltext Indexes
 A fulltext index can be used to find words, or prefixes of words inside documents.
 
 A fulltext index can be defined on one attribute only, and will include all words contained in
-documents that have a textual value in the index attribute. Since ArangoDB 2.6 the index
+documents that have a textual value in the index attribute. The index
 will also include words from the index attribute if the index attribute is an array of
 strings, or an object with string value members.