DOC-469 | Remove 3.7 content, version remarks (#1360)

* Remove 3.7 content, version remarks

* Apply to 3.12

---------

Co-authored-by: Paula Mihu <[email protected]>

Author: Simran-B

3.11/analyzers.md

@@ -1616,37 +1616,35 @@ Also see [Known Issues](release-notes-known-issues311.html#arangosearch).
 Stemming support is provided by [Snowball](https://snowballstem.org/){:target="_blank"},
 which supports the following languages:
 
-Language     | Code
--------------|-----
-Arabic     * | `ar`
-Armenian  ** | `hy`
-Basque     * | `eu`
-Catalan    * | `ca`
-Danish     * | `da`
-Dutch        | `nl`
-English      | `en`
-Finnish      | `fi`
-French       | `fr`
-German       | `de`
-Greek      * | `el`
-Hindi      * | `hi`
-Hungarian  * | `hu`
-Indonesian * | `id`
-Irish      * | `ga`
-Italian      | `it`
-Lithuanian * | `lt`
-Nepali     * | `ne`
-Norwegian    | `no`
-Portuguese   | `pt`
-Romanian   * | `ro`
-Russian      | `ru`
-Serbian    * | `sr`
-Spanish      | `es`
-Swedish      | `sv`
-Tamil      * | `ta`
-Turkish    * | `tr`
-Yiddish   ** | `yi`
-
-\* <small>Introduced in: v3.7.0</small>
-
-\*\* <small>Introduced in: v3.10.0</small>
+Language    | Code
+------------|-----
+Arabic      | `ar`
+Armenian  * | `hy`
+Basque      | `eu`
+Catalan     | `ca`
+Danish      | `da`
+Dutch       | `nl`
+English     | `en`
+Finnish     | `fi`
+French      | `fr`
+German      | `de`
+Greek       | `el`
+Hindi       | `hi`
+Hungarian   | `hu`
+Indonesian  | `id`
+Irish       | `ga`
+Italian     | `it`
+Lithuanian  | `lt`
+Nepali      | `ne`
+Norwegian   | `no`
+Portuguese  | `pt`
+Romanian    | `ro`
+Russian     | `ru`
+Serbian     | `sr`
+Spanish     | `es`
+Swedish     | `sv`
+Tamil       | `ta`
+Turkish     | `tr`
+Yiddish   * | `yi`
+
+\* <small>Introduced in: v3.10.0</small>

3.11/appendix-java-script-modules-arango-db.md

@@ -193,8 +193,7 @@ const result2 = query`
 `.toArray();
 ```
 
-It is also possible to pass query options to the query helper
-(introduced in v3.7.0):
+It is also possible to pass query options to the query helper:
 
 ```js
 const { query } = require('@arangodb');

3.11/aql/functions-arangosearch.md

@@ -481,8 +481,6 @@ FOR doc IN viewName
 
 ### NGRAM_MATCH()
 
-<small>Introduced in: v3.7.0</small>
-
 `NGRAM_MATCH(path, target, threshold, analyzer) → fulfilled`
 
 Match documents whose attribute value has an
@@ -603,8 +601,6 @@ enabled. The `PHRASE()` function will otherwise not find anything.
 
 #### Object tokens
 
-<small>Introduced in v3.7.0</small>
-
 - `{IN_RANGE: [low, high, includeLow, includeHigh]}`:
   see [IN_RANGE()](#in_range). *low* and *high* can only be strings.
 - `{LEVENSHTEIN_MATCH: [token, maxDistance, transpositions, maxTerms, prefix]}`:
@@ -797,8 +793,6 @@ that is used outside of `SEARCH` operations.
 
 `STARTS_WITH(path, prefixes, minMatchCount) → startsWith`
 
-<small>Introduced in: v3.7.1</small>
-
 Match the value of the attribute that starts with one of the `prefixes`, or
 optionally with at least `minMatchCount` of the prefixes.
 
@@ -902,8 +896,6 @@ contains one of the prefixes (`something`).
 
 ### LEVENSHTEIN_MATCH()
 
-<small>Introduced in: v3.7.0</small>
-
 `LEVENSHTEIN_MATCH(path, target, distance, transpositions, maxTerms, prefix) → fulfilled`
 
 Match documents with a [Damerau-Levenshtein distance](https://en.wikipedia.org/wiki/Damerau%E2%80%93Levenshtein_distance){:target=_"blank"}
@@ -999,8 +991,6 @@ FOR doc IN viewName
 
 ### LIKE()
 
-<small>Introduced in: v3.7.2</small>
-
 `LIKE(path, search) → bool`
 
 Check whether the pattern `search` is contained in the attribute denoted by `path`,

3.11/aql/functions-array.md

@@ -171,8 +171,6 @@ RETURN FLATTEN( [ 1, 2, [ 3, 4 ], 5, [ 6, 7 ], [ 8, [ 9, 10 ] ] ], 2 )
 
 ## INTERLEAVE()
 
-<small>Introduced in: v3.7.1</small>
-
 `INTERLEAVE(array1, array2, ... arrayN) → newArray`
 
 Accepts an arbitrary number of arrays and produces a new array with the elements
@@ -253,8 +251,6 @@ RETURN INTERSECTION( [2,4,6], [8,10,12], [14,16,18] )
 
 ## JACCARD()
 
-<small>Introduced in: v3.7.0</small>
-
 `JACCARD(array1, array2) → jaccardIndex`
 
 Calculate the [Jaccard index](https://en.wikipedia.org/wiki/Jaccard_index){:target="_blank"}
@@ -673,8 +669,6 @@ RETURN REMOVE_NTH( [ "a", "b", "c", "d", "e" ], -2 )
 
 ## REPLACE_NTH()
 
-<small>Introduced in: v3.7.0</small>
-
 `REPLACE_NTH(anyArray, position, replaceValue, defaultPaddingValue) → newArray`
 
 Replace the element at *position* in *anyArray* with *replaceValue*.

3.11/aql/functions-bit.md

@@ -6,8 +6,6 @@ title: AQL Bit Functions
 Bit functions
 =============
 
-<small>Introduced in: v3.7.7</small>
-
 AQL offers some bit manipulation and interpretation functions for bitwise
 arithmetic.
 

3.11/aql/functions-miscellaneous.md

@@ -589,8 +589,6 @@ FOR i IN 1..3 FILTER WARN(i < 2, "i is not smaller 2") RETURN i
 
 ### IN_RANGE()
 
-<small>Introduced in: v3.7.0</small>
-
 `IN_RANGE(value, low, high, includeLow, includeHigh) → included`
 
 Returns true if *value* is greater than (or equal to) *low* and less than

3.11/aql/functions-numeric.md

@@ -540,8 +540,6 @@ POW( 5, 0 ) // 1
 PRODUCT()
 ---------
 
-<small>Introduced in: v3.7.2</small>
-
 `PRODUCT(numArray) → product`
 
 Return the product of the values in *array*.

3.11/aql/functions-string.md

@@ -473,8 +473,6 @@ string representation.
 IPV4_FROM_NUMBER()
 ------------------
 
-<small>Introduced in: v3.7.2</small>
-
 `IPV4_FROM_NUMBER(numericAddress) → stringAddress`
 
 Converts a numeric IPv4 address value into its string representation.
@@ -536,8 +534,6 @@ Converts a numeric IPv4 address value into its string representation.
 IPV4_TO_NUMBER()
 ----------------
 
-<small>Introduced in: v3.7.2</small>
-
 `IPV4_TO_NUMBER(stringAddress) → numericAddress`
 
 Converts an IPv4 address string into its numeric representation.
@@ -598,8 +594,6 @@ Converts an IPv4 address string into its numeric representation.
 IS_IPV4()
 ---------
 
-<small>Introduced in: v3.7.2</small>
-
 `IS_IPV4(value) → bool`
 
 Check if an arbitrary string is suitable for interpretation as an IPv4 address.
@@ -1059,8 +1053,6 @@ string representation.
 NGRAM_POSITIONAL_SIMILARITY()
 -----------------------------
 
-<small>Introduced in: v3.7.0</small>
-
 `NGRAM_POSITIONAL_SIMILARITY(input, target, ngramSize) → similarity`
 
 Calculates the [_n_-gram similarity](https://webdocs.cs.ualberta.ca/~kondrak/papers/spire05.pdf){:target="_blank"}
@@ -1099,8 +1091,6 @@ not involving Analyzers.
 NGRAM_SIMILARITY()
 ------------------
 
-<small>Introduced in: v3.7.0</small>
-
 `NGRAM_SIMILARITY(input, target, ngramSize) → similarity`
 
 Calculates [_n_-gram similarity](https://webdocs.cs.ualberta.ca/~kondrak/papers/spire05.pdf){:target="_blank"}
@@ -1652,8 +1642,6 @@ that can utilize View indexes.
 
 `STARTS_WITH(text, prefixes, minMatchCount) → startsWith`
 
-<small>Introduced in: v3.7.1</small>
-
 Check if the given string starts with one of the `prefixes`.
 
 - **text** (string): a string to compare against

3.11/aql/fundamentals-data-types.md

@@ -80,7 +80,7 @@ some bits of precision. The same is true when converting AQL numeric results to
 JavaScript (e.g. returning them to Foxx).
 {% endhint %}
 
-Since ArangoDB v3.7.7, numeric integer literals can also be expressed as binary
+Numeric integer literals can also be expressed as binary
 (base 2) or hexadecimal (base 16) number literals.
 
 - The prefix for binary integer literals is `0b`, e.g. `0b10101110`.
@@ -156,7 +156,7 @@ supported.
 [ [ "fox", "marshal" ] ]
 ```
 
-A trailing comma after the last element is allowed (introduced in v3.7.0):
+A trailing comma after the last element is allowed:
 
 ```aql
 [
@@ -234,7 +234,7 @@ then the attribute name must be quoted:
 { ´return´: … }  // quoted name (forward ticks)
 ```
 
-A trailing comma after the last element is allowed (introduced in v3.7.0):
+A trailing comma after the last element is allowed:
 
 ```aql
 {

3.11/aql/graphs-traversals.md

@@ -111,14 +111,14 @@ FOR vertex[, edge[, path]]
     - `"none"` – no uniqueness check is applied on edges. **Note:**
       Using this configuration, the traversal follows edges in cycles.
   - **edgeCollections** (string\|array): Optionally restrict edge
-    collections the traversal may visit (introduced in v3.7.0). If omitted,
+    collections the traversal may visit. If omitted,
     or an empty array is specified, then there are no restrictions.
     - A string parameter is treated as the equivalent of an array with a single
       element.
     - Each element of the array should be a string containing the name of an
       edge collection.
   - **vertexCollections** (string\|array): Optionally restrict vertex
-    collections the traversal may visit (introduced in v3.7.0). If omitted,
+    collections the traversal may visit. If omitted,
     or an empty array is specified, then there are no restrictions.
     - A string parameter is treated as the equivalent of an array with a single
       element.
@@ -127,7 +127,7 @@ FOR vertex[, edge[, path]]
     - The starting vertex is always allowed, even if it does not belong to one
       of the collections specified by a restriction.
   - **parallelism** (number, *optional*): Optionally parallelize traversal
-    execution (introduced in v3.7.1). If omitted or set to a value of `1`,
+    execution. If omitted or set to a value of `1`,
     traversal execution is not parallelized. If set to a value greater than `1`,
     then up to that many worker threads can be used for concurrently executing
     the traversal. The value is capped by the number of available cores on the

3.11/aql/operations-search.md

@@ -106,7 +106,7 @@ The conditions are now:
 - `>` (greater than)
 - `!=` (unequal)
 - `IN` (contained in array or range), also `NOT IN`
-- `LIKE` (equal with wildcards, introduced in v3.7.0), also `NOT LIKE`
+- `LIKE` (equal with wildcards), also `NOT LIKE`
 
 Also see the [`IN_RANGE()` function](functions-arangosearch.html#in_range) for
 an alternative to a combination of `<`, `<=`, `>`, `>=` operators for range
@@ -299,7 +299,7 @@ The `SEARCH` operation accepts an options object with the following attributes:
   <!-- Internal only: nodnf, noneg -->
 - `countApproximate` (string, _optional_): controls how the total count of rows
   is calculated if the `fullCount` option is enabled for a query or when
-  a `COLLECT WITH COUNT` clause is executed (introduced in v3.7.6)
+  a `COLLECT WITH COUNT` clause is executed
   - `"exact"` (default): rows are actually enumerated for a precise count.
   - `"cost"`: a cost-based approximation is used. Does not enumerate rows and
     returns an approximate result with O(1) complexity. Gives a precise result

3.11/arangosearch-views.md

@@ -201,9 +201,7 @@ During view modification the following directives apply:
 
 - **primarySortCompression** (_optional_; type: `string`; default: `lz4`; _immutable_)
 
-  <small>Introduced in: v3.7.1</small>
-
-  Defines how to compress the primary sort data (introduced in v3.7.0).
+  Defines how to compress the primary sort data.
 
   - `"lz4"` (default): use LZ4 fast compression.
   - `"none"`: disable compression to trade space for speed.
@@ -247,8 +245,6 @@ During view modification the following directives apply:
 
 - **storedValues** (_optional_; type: `array`; default: `[]`; _immutable_)
 
-  <small>Introduced in: v3.7.1</small>
-
   An array of objects to describe which document attributes to store in the
   View index. It can then cover search queries, which means the data can be
   taken from the index directly and accessing the storage engine can be

3.11/architecture-single-instance-vs-cluster.md

@@ -88,7 +88,7 @@ not possible, if edge collections are used directly. See
 for details. The `WITH` statement is not necessary when using named graphs
 for the traversals.
 
-Since ArangoDB 3.7.12 there is a startup option `--query.require-with`
+There is a `--query.require-with` startup option
 to make single server installations also require the `WITH` statements
 in the same places where are cluster installation would. This option
 is false by default, but be set to true to remove this behavior

3.11/data-modeling-databases-working-with.md

@@ -217,8 +217,6 @@ all clients have disconnected and references have been garbage-collected.
 
 ### Compact
 
-<small>Introduced in: v3.6.7, v3.7.3</small>
-
 Compact the entire data, for all databases:
 
 `db._compact(options)`

3.11/data-modeling-documents-document-methods.md

@@ -499,8 +499,7 @@ used to specify the following options:
     performed on collections sharded by `_key`.
   - `overwriteMode`: this optional flag can have one of the following values:
     - `ignore`: if a document with the specified `_key` value exists already,
-      nothing will be done and no write operation will be carried out
-      (introduced in v3.7.0).
+      nothing will be done and no write operation will be carried out.
       The insert operation will return success in this case. This mode does not
       support returning the old document version using the `returnOld`
       attribute. `returnNew` will only set the `new` attribute in the response
@@ -510,8 +509,7 @@ used to specify the following options:
       also be used when no overwrite mode is specified but the `overwrite`
       flag is set to `true`.
     - `update`: if a document with the specified `_key` value exists already,
-      it will be patched (partially updated) with the specified document value
-      (introduced in v3.7.0).
+      it will be patched (partially updated) with the specified document value.
       The overwrite mode can be further controlled via the `keepNull` and
       `mergeObjects` parameters.
     - `conflict`: if a document with the specified `_key` value exists already,

3.11/data-modeling-documents-schema-validation.md

@@ -8,8 +8,6 @@ redirect_from:
 Schema Validation
 =================
 
-<small>Introduced in: v3.7.1</small>
-
 While ArangoDB is schema-less, it allows to enforce certain document structures
 on collection level. The desired structure can be described in the popular
 [JSON Schema](https://json-schema.org/){:target="_blank"} format (draft-4,

3.11/graphs-pregel.md

@@ -101,7 +101,7 @@ The `state` field has one of the following values:
 | `"loading"`    | The graph data is being loaded from the database into memory before executing the algorithm.
 | `"running"`    | The algorithm is executing normally.
 | `"storing"`    | The algorithm finished, but the results are still being written back into the collections. Only occurs if the `store` parameter is set to `true`.
-| `"done"`       | The execution is done. In version 3.7.1 and later, this means that storing is also done. In earlier versions, the results may not be written back into the collections yet. This event is announced in the server log (requires at least `info` log level for the `pregel` topic).
+| `"done"`       | The execution is done. This means that storing is also done. This event is announced in the server log (requires at least `info` log level for the `pregel` topic).
 | `"canceled"`   | The execution was permanently canceled, either by the user or by an error.
 | `"in error"`   | The execution is in an error state. This can be caused by primary DB-Servers being unreachable or unresponsive. The execution might recover later, or switch to `canceled` if it is not able to recover successfully.
 | `"recovering"` | The execution is actively recovering and switches back to `running` if the recovery is successful.
@@ -137,8 +137,8 @@ pregel.cancel(execution);
 ```
 
 You might get inconsistent results if you requested to store the results and
-then cancel an execution when it is already in its `storing` state (or `done`
-state in versions prior to 3.7.1). The data is written multi-threaded into all
+then cancel an execution when it is already in its `storing` state.
+The data is written multi-threaded into all
 collection shards at once. This means there are multiple transactions
 simultaneously. A transaction might already be committed when you cancel the
 execution job. Therefore, you might see some updated documents, while other

3.11/graphs-satellite-graphs.md

@@ -6,8 +6,6 @@ title: ArangoDB SatelliteGraphs
 SatelliteGraphs
 ===============
 
-<small>Introduced in: v3.7.0</small>
-
 {% include hint-ee-arangograph.md feature="SatelliteGraphs" plural=true %}
 
 What is a SatelliteGraph?