Remove mentions of Neo4j 6.0 (#1088)

Author: JPryce-Aklundh

modules/ROOT/pages/functions/scalar.adoc

@@ -1206,11 +1206,10 @@ This can include the introduction of new types and subtypes of already supported
 If a new type is introduced, it will be returned by the `valueType()` function as soon as it is released.
 However, if a more precise subtype of a previously supported type is introduced, it would be considered a breaking change.
 
+For example, the function currently returns `"FLOAT"`, but if a more specific `FLOAT` type was added, e.g. `FLOAT32`, this would be considered more specific and not be returned until the next major release of Neo4j.
+As a result,`"FLOAT"` would continue to be returned for any `FLOAT32` values until the next major release.
 
-For example, the function currently returns `"FLOAT"`, but if a more specific `FLOAT` type was added, e.g. `FLOAT32`, this would be considered more specific and not be returned until Neo4j 6.0.
-As a result,`"FLOAT"` would continue to be returned for any `FLOAT32` values until the release of Neo4j 6.0.
-
-The below list contains all supported types displayed by the `valueType()` function:
+The below list contains all currently supported types displayed by the `valueType()` function:
 
 *  Predefined types
 ** `NOTHING`

modules/ROOT/pages/syntax/naming.adoc

@@ -49,11 +49,6 @@ Some techniques to mitigate this are:
 
 ====
 
-[NOTE]
-====
-Several special characters have been deprecated and will require escaping in Neo4j 6.0, see xref::deprecations-additions-removals-compatibility.adoc#cypher-deprecations-additions-removals-5.15[here] for the comprehensive list of deprecated characters.
-====
-
 == Scoping and namespace rules
 
 * Node labels, relationship types and property names may re-use names.