Remove mentions of Neo4j v5

modules/ROOT/pages/backup-restore/copy-database.adoc

@@ -270,8 +270,6 @@ CREATE DATABASE database-copy
 SHOW DATABASES
 ----
 
-. (For versions before Neo4j 5.20) If your original database has a schema defined, change your active database to the copied database and recreate the schema using the schema commands saved in the file _<database-name>-schema.cypher_.
-
 === Filtering data while copying a database
 
 You can use `neo4j-admin database copy` to filter out any unwanted data while copying a database, for example, by removing nodes, labels, properties, and relationships.
@@ -341,8 +339,6 @@ This is the newly created version of the database.
 START DATABASE neo4j
 ----
 
-. (For versions before Neo4j 5.20) If your original database has a schema defined, recreate the schema using the schema commands saved in the file _<database-name>-schema.cypher_.
-
 [TIP]
 ====
 For a detailed example of how to reclaim unused space, see xref:performance/space-reuse.adoc#space-reuse-reclaim-space[Reclaim unused space].

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

@@ -20,13 +20,6 @@ It is best practice, but not mandatory, to perform the backup from a server on t
 You should install Neo4j on that machine to make the `neo4j-admin` command available.
 This machine is known as a backup client.
 
-
-[NOTE]
-====
-Neo4j 5 introduces a new version of the backup command which produces immutable backup artifacts (as opposed to mutable folders as in previous versions).
-====
-
-
 [[backup-artifact]]
 === Backup artifact
 

modules/ROOT/pages/clustering/databases.adoc

@@ -616,7 +616,7 @@ The `S3SeedProvider` supports:
 
 [NOTE]
 ====
-Neo4j 5 comes bundled with necessary libraries for AWS S3 connectivity.
+Neo4j comes bundled with necessary libraries for AWS S3 connectivity.
 Therefore, if you use `S3SeedProvider`,`aws cli` is not required but can be used with the `CloudSeedProvider`.
 ====
 

modules/ROOT/pages/clustering/setup/discovery.adoc

@@ -14,7 +14,7 @@ Neo4j provides several mechanisms for cluster members to discover each other and
 In Neo4j 5.23, a new discovery service was introduced.
 You must move to the new version before you start using Neo4j 2025.01.
 
-Details are provided in link:https://neo4j.com/docs/operations-manual/5/clustering/setup/discovery/#clustering-discovery-v1-to-v2[the guide for the Neo4j 5.x series].
+See link:{neo4j-docs-base-uri}/operations-manual/5/clustering/setup/discovery/#clustering-discovery-v1-to-v2[Cluster server discovery in Operations Manual version 5] for more information.
 ====
 
 [[clustering-discovery-methods]]

modules/ROOT/pages/configuration/neo4j-conf.adoc

@@ -27,8 +27,7 @@ It prevents Neo4j from starting if the _neo4j.conf_ file contains _typos_, _inco
 If you set more than one value for xref:configuration/configuration-settings.adoc#config_server.jvm.additional[`server.jvm.additional`], each setting value adds another custom JVM argument to the `java` launcher.
 +
 To disable the strict validation, set `server.config.strict_validation.enabled=false`.
-* By default, the character encoding is assumed to be ISO 8859-1.
-From Neo4j 4.8 onwards, this can be overridden by setting the environment variable `NEO4J_CONFIG_FILE_CHARSET` to, for example, `utf8`.
+* By default, the character encoding is assumed to be ISO 8859-1 but can be overridden by setting the environment variable `NEO4J_CONFIG_FILE_CHARSET` to, for example, `utf8`.
 
 
 == Configuration settings
@@ -55,15 +54,7 @@ All configuration settings fall into one of the following scopes that behave dif
 * `server` settings apply only to the specific server and can be varied between configuration files across a cluster/DBMS.
 * `browser` settings apply only to Neo4j Browser.
 * `client` settings apply only to the client.
-+
-[NOTE]
-====
-In Neo4j 5, the `fabric` scope is no longer available.
-All configuration settings identified by the `fabric` namespace in the `neo4j.conf` file are moved into the `system` database.
-The Cypher surface is extended to support the Fabric configuration.
 
-For more information, see xref:database-administration/composite-databases/concepts.adoc[Composite databases].
-====
 Component::
 Component namespaces are used to group settings that affect similar systems.
 

modules/ROOT/pages/database-administration/composite-databases/concepts.adoc

@@ -4,11 +4,7 @@
 [[composite-databases-concepts]]
 = Concepts
 
-A Composite database is a special type of database introduced in Neo4j 5.
-It supersedes the previous Fabric implementation in Neo4j 4.x.
-
-In Neo4j 5, fabric has been expanded as a concept and now refers to the architectural design of a unified system that provides a single access point to local or distributed graph data.
-
+A Composite database is a special type of database.
 Composite databases are the means to access this partitioned data or graphs with a single Cypher query.
 
 Composite databases *do not store data* independently.

modules/ROOT/pages/tools/neo4j-admin/migrate-database.adoc

@@ -6,7 +6,7 @@ You can use the `neo4j-admin database migrate` command to migrate a Neo4j databa
 
 A store format defines how the data of a database is stored on the file system.
 
-As of Neo4j 5, the store format of a database is versioned with the `MAJOR.MINOR` scheme, independent of Neo4j versioning.
+The store format of a database is versioned with the `MAJOR.MINOR` scheme, independent of Neo4j versioning.
 An upgrade to the latest `MINOR` format version is an automatic operation performed on database startup.
 A migration to a higher `MAJOR` format version or another format is a manual action performed with the `migrate` command.
 

modules/ROOT/pages/tutorial/tutorial-composite-database.adoc

@@ -124,7 +124,7 @@ bin/cypher-shell -u neo4j -p neo4j
 ----
 Password change required
 new password: ********
-Connected to Neo4j 5 at neo4j://localhost:7687 as user neo4j.
+Connected to Neo4j 2025.01 at neo4j://localhost:7687 as user neo4j.
 Type :help for a list of available commands or :exit to exit the shell.
 Note that Cypher queries must end with a semicolon.
 ----