Removal of old graph reference deprecation. (#358)

This is a partial backport of
#340 to cover the changes
applicable to 5.26.

Author: Lojjs

modules/ROOT/pages/notifications/all-notifications.adoc

@@ -1374,10 +1374,17 @@ a|
 To continue using it, escape the identifier by adding backticks around the identifier `%s`.
 - The character with the Unicode representation `%s` is deprecated for unescaped identifiers and will not be supported in the future.
 To continue using it, escape the identifier by adding backticks around the identifier `%s`.
-- label:new[Valid for Neo4j 5.5-5.25] All subqueries in a UNION [ALL] should have the same ordering for the return columns.
-Using differently ordered return items in a UNION [ALL] clause is deprecated and will be removed in a future version.
-- Databases and aliases with unescaped `.` are deprecated unless to indicate that they belong to a composite database.
+- All subqueries in a `UNION [ALL]` should have the same ordering for the return columns.
+[NOTE]
+In versions 5.5 to 5.25, using differently ordered return items in a `UNION [ALL]` clause is deprecated.
+However, starting from version 5.26, the deprecation has been withdrawn following cost-benefit analysis and valuable user feedback.
+- label:deprecated[Deprecated from 5.26.0 to 5.26.9] Databases and aliases with unescaped `.` are deprecated unless the dots indicate that they belong to a composite database.
 Names containing `.` should be escaped. (`%s`)
+[NOTE]
+Databases and aliases with unescaped `.` are deprecated in versions 5.26.0 to 5.26.9.
+However, starting from version 5.26.9, this deprecation has been withdrawn.
+The reason for this change is that the previous quoting rules have been found inconsistent and ambiguous, and will be improved in a future Cypher version.
+
 |Category
 m|DEPRECATION
 |GQLSTATUS code
@@ -1433,6 +1440,13 @@ Names containing `.` should be escaped. (Name: `foo.bar`)
 ======
 =====
 
+[NOTE]
+====
+Databases and aliases with unescaped `.` are deprecated in versions 5.26.0 to 5.26.9.
+However, starting from version 5.26.9, this deprecation has been withdrawn.
+The reason for this change is that the previous quoting rules have been found inconsistent and ambiguous, and will be improved in a future Cypher version.
+====
+
 .Using differently ordered return items in a `UNION` clause
 [.tabbed-example]
 =====
@@ -1456,17 +1470,7 @@ All subqueries in a UNION [ALL] should have the same ordering for the return col
 Using differently ordered return items in a UNION [ALL] clause is deprecated and will be removed in a future version.
 
 ======
-=====
-
-[NOTE]
-====
-Using differently ordered return items in a UNION [ALL] clause is deprecated in versions 5.5 to 5.25.
-However, starting from version 5.26, the deprecation has been withdrawn following cost-benefit analysis and valuable user feedback.
-====
 
-.Using the Unicode \u0085 in an unescaped identifier
-[.tabbed-example]
-=====
 [.include-with-neo4j-code]
 ======
 Query::
@@ -1492,10 +1496,15 @@ RETURN 'val' as one, 'val' as two
 UNION
 RETURN 'val' as one, 'val' as two
 ----
-
 ======
 =====
 
+[NOTE]
+====
+In versions 5.5 to 5.25, using differently ordered return items in a `UNION [ALL]` clause is deprecated.
+However, starting from version 5.26, the deprecation has been withdrawn following cost-benefit analysis and valuable user feedback.
+====
+
 .Using the Unicode \u0085 in an unescaped identifier
 [.tabbed-example]
 =====