remove and update many more mentions of 5.x

Author: renetapopova

modules/ROOT/pages/authentication-authorization/auth-providers.adoc

@@ -1,5 +1,5 @@
 :description: This section explains how to use Cypher to manage authentication and authorization at the user level using Cypher.
-:page-role: enterprise-edition new-5.24
+:page-role: enterprise-edition
 
 [[access-control-auth-providers]]
 = User auth providers

modules/ROOT/pages/authentication-authorization/dbms-administration.adoc

@@ -1574,13 +1574,7 @@ The ability to use elevated privileges when executing a procedure can be granted
 A user with this privilege will not be restricted to their other privileges when executing the procedures matched by the <<access-control-name-globbing, name-globbing>>.
 The `EXECUTE BOOSTED PROCEDURE` privilege only affects the elevation, and not the execution of the procedure.
 Therefore, it is needed to grant `EXECUTE PROCEDURE` privilege for the procedures as well.
-
-
-[NOTE]
-====
-Since Neo4j 5.0, both `EXECUTE PROCEDURE` and `EXECUTE BOOSTED PROCEDURE` are needed to execute a procedure with elevated privileges.
-This differs from Neo4j 4.x, when only the `EXECUTE BOOSTED PROCEDURE` is required.
-====
+Both `EXECUTE PROCEDURE` and `EXECUTE BOOSTED PROCEDURE` are needed to execute a procedure with elevated privileges.
 
 [source, cypher, role=noplay]
 ----
@@ -1873,13 +1867,7 @@ The ability to use elevated privileges when executing a user-defined function (U
 A user with this privilege will not be restricted to their other privileges when executing the UDFs matched by the <<access-control-name-globbing, name-globbing>>.
 The `EXECUTE BOOSTED USER DEFINED FUNCTION` privilege only affects the elevation and not the execution of the function.
 Therefore, it is needed to grant `EXECUTE USER DEFINED FUNCTION` privilege for the functions as well.
-
-
-[NOTE]
-====
-Since Neo4j 5.0, both `EXECUTE USER DEFINED FUNCTION` and `EXECUTE BOOSTED USER DEFINED FUNCTION` are needed to execute a function with elevated privileges.
-This differs from Neo4j 4.x, when only the `EXECUTE BOOSTED USER DEFINED FUNCTION` is required.
-====
+oth `EXECUTE USER DEFINED FUNCTION` and `EXECUTE BOOSTED USER DEFINED FUNCTION` are needed to execute a function with elevated privileges.
 
 [IMPORTANT]
 ====

modules/ROOT/pages/authentication-authorization/immutable-roles-privileges.adoc

@@ -4,8 +4,7 @@
 :description: This section explains how to use Cypher to manage immutable roles and privileges.
 
 
-Immutable privileges are useful for restricting the actions of users who can themselves administer xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-privilege-management[privileges]. 
-Starting with Neo4j 5.26, Neo4j also introduces immutable roles.
+Immutable privileges are useful for restricting the actions of users who can themselves administer xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-privilege-management[privileges].
 Immutable roles are useful for providing _system roles_, which appear as permanent parts of the DBMS.
 
 
@@ -38,8 +37,8 @@ The following examples demonstrate how to use Cypher to manage immutable roles a
 
 === Restricting the actions of users who can manage privileges
 
-To prevent all users (including those with `PRIVILEGE MANAGEMENT` privileges) from performing *database management*, attach an immutable privilege to the `PUBLIC` role. 
-The `PUBLIC` role implicitly and irrevocably applies to all users. 
+To prevent all users (including those with `PRIVILEGE MANAGEMENT` privileges) from performing *database management*, attach an immutable privilege to the `PUBLIC` role.
+The `PUBLIC` role implicitly and irrevocably applies to all users.
 
 . Ensure that you have completed steps 1 and 2 from <<administer-immutable-roles-and-privileges>>.
 . Run the following command to deny the `IMMUTABLE DATABASE MANAGEMENT` privilege to the `PUBLIC` role:

modules/ROOT/pages/authentication-authorization/load-privileges.adoc

@@ -11,8 +11,6 @@ CREATE ROLE roleLoadCidr
 [[access-control-load-privileges]]
 = Load privileges
 
-_This feature is available from Neo4j 5.13._
-
 This section explains how to use Cypher to manage load privileges.
 All load privileges apply to the whole system.
 Like DBMS privileges, they do not belong to one specific database or graph.
@@ -102,8 +100,6 @@ The `LOAD ON ALL DATA` privilege is granted to the `PUBLIC` role by default.
 [[access-control-load-cidr]]
 == The `CIDR` privilege
 
-_This feature is available from Neo4j 5.16._
-
 The load privilege on `CIDR cidr` enables or disables loading data from the given IPv4 or IPv6 CIDR range.
 If granted, the user can load data from sources in the given CIDR range.
 If missing or denied, no data can be loaded from sources in the given CIDR range.

modules/ROOT/pages/authentication-authorization/manage-privileges.adoc

@@ -48,7 +48,7 @@ The components of the graph privilege commands are:
 ** `IMMUTABLE` can optionally be specified when performing a `GRANT` or `DENY` to indicate that the privilege cannot be subsequently removed unless auth is disabled.
 Auth must also be disabled in order to `GRANT` or `DENY` an immutable privilege.
 Contrastingly, when `IMMUTABLE` is specified in conjunction with a `REVOKE` command, it will act as a filter and only remove matching _immutable_ privileges.
-Starting from Neo4j 5.26, immutable privileges can also be used together with immutable roles.
+Immutable privileges can also be used together with immutable roles.
 See xref:authentication-authorization/immutable-roles-privileges.adoc[] for more information.
 
 * _graph-privilege_:

modules/ROOT/pages/authentication-authorization/manage-roles.adoc

@@ -340,7 +340,7 @@ For more information, see xref:authentication-authorization/dbms-administration.
 
 
 You can view all available roles using the Cypher command `SHOW ROLES`, which returns a single column by default.
-Starting from 5.26, you can optionally use `SHOW ROLES YIELD *` to see if the role is immutable.
+Optionally, you can also use `SHOW ROLES YIELD *` to see if the role is immutable.
 See <<access-control-immutable-roles, Immutable roles>> for more information.
 
 .`SHOW ROLES` output
@@ -582,7 +582,6 @@ This is equivalent to running `DROP ROLE myrole IF EXISTS` followed by `CREATE R
 The `CREATE OR REPLACE ROLE` command does not allow you to use the `IF NOT EXISTS`.
 ====
 
-[role=new-in-5.26]
 [[access-control-immutable-roles]]
 == Immutable roles
 

modules/ROOT/pages/authentication-authorization/manage-users.adoc

@@ -752,7 +752,6 @@ You can create users using one of the following Cypher commands, depending on wh
 In both cases, you can specify the user's password, whether they must change it at the next login, their status, home database, and auth provider settings.
 The `SET` clauses can be applied in any order.
 It is mandatory to specify a `SET PASSWORD` and/or at least one `SET AUTH` clause because users must have at least one auth provider.
-`SET AUTH` is available from Neo4j 5.24 onwards.
 
 .`CREATE USER` syntax
 [source, syntax, role="noheader"]

modules/ROOT/pages/authentication-authorization/property-based-access-control.adoc

@@ -7,7 +7,7 @@ CREATE ROLE regularUsers;
 ----
 ////
 
-:page-role: enterprise-edition aura-db-business-critical aura-db-dedicated new-5.24
+:page-role: enterprise-edition aura-db-business-critical aura-db-dedicated
 [[property-based-access-control]]
 = Property-based access control
 
@@ -106,7 +106,7 @@ GRANT READ {*} ON GRAPH * FOR (n) WHERE n.createdAt > date() TO regularUsers
 ----
 [NOTE]
 ====
-The `date()` function is evaluated, and the value used to evaluate the privilege is the date when the property-based privilege is created. 
+The `date()` function is evaluated, and the value used to evaluate the privilege is the date when the property-based privilege is created.
 Keep this in mind when designing your property rules, and use the `SHOW PRIVILEGES AS COMMANDS` command to check the stored value.
 This is essential when revoking property-based privileges containing evaluated function values like `date()`.
 ====

modules/ROOT/pages/authentication-authorization/sso-integration.adoc

@@ -114,7 +114,7 @@ The default is `false`, to read the claim from the token.
 | xref:configuration/configuration-settings.adoc#config_dbms.security.oidc.-provider-.claims.groups[dbms.security.oidc.<provider>.claims.groups]
 |
 | true
-| The claim to use for the database roles. Neo4j expects to find a claim in the JWT or user_info response with this name. The claim may be a string claim representing a single role or a string array claim representing multiple roles. From Neo4j 5.4, the JWT claim may also contain a single group returned as a string as well as a list of groups as was previously required.
+| The claim to use for the database roles. Neo4j expects to find a claim in the JWT or user_info response with this name. The claim may be a string claim representing a single role or a string array claim representing multiple roles. The JWT claim may also contain a single group returned as a string as well as a list of groups as was previously required.
 
 | xref:configuration/configuration-settings.adoc#config_dbms.security.oidc.-provider-.authorization.group_to_role_mapping[dbms.security.oidc.<provider>.authorization.group_to_role_mapping]
 |

modules/ROOT/pages/backup-restore/aggregate.adoc

@@ -102,13 +102,13 @@ Consult Neo4j support before use.
 
 [NOTE]
 ====
-The `--from-path=<path>` option can also load backup artifacts from AWS S3 buckets (from Neo4j 5.19), Google Cloud storage buckets (from Neo4j 5.21), and Azure buckets (from Neo4j 5.24).
+The `--from-path=<path>` option can also load backup artifacts from AWS S3 buckets, Google Cloud storage buckets, and Azure buckets.
 For more information, see <<aggregate-backup-cloud-storage>>.
 ====
 
 [NOTE]
 ====
-Neo4j 5.24 introduces the `--temp-path` option to address potential issues related to disk space when performing backup-related commands, especially when cloud storage is involved.
+The `--temp-path` option addresses potential issues related to disk space when performing backup-related commands, especially when cloud storage is involved.
 
 If `--temp-path` is not set, a temporary directory is created inside the directory specified by the `--from-path` option.
 
@@ -142,7 +142,6 @@ bin/neo4j-admin database aggregate-backup --from-path=/mnt/backups/neo4j-2022-10
 ----
 The command checks the `/mnt/backups/` directory for a backup chain including the file _neo4j-2022-10-18T13-00-07.backup_, for the database `neo4j`.
 If found, it is then aggregated into a single backup artifact.
-This option is only available in Neo4j 5.2 and later.
 
 [[aggregate-backup-cloud-storage]]
 === Aggregating a backup chain located in a cloud storage