neo4j · MarkWoulfeNeo4j · Jan 29, 2025 · Jan 22, 2025 · Jan 29, 2025
diff --git a/modules/ROOT/pages/managing-instances/migration-readiness.adoc b/modules/ROOT/pages/managing-instances/migration-readiness.adoc
@@ -10,8 +10,8 @@ You can access the report for any version 4 instance via the link through the "M
 
 == Overview
 
-This tool advises how to prepare an AuraDB v4 instance for migration to AuraDB latest version.
-It reports current application queries, drivers, and database objects that would prevent you from migrating to AuraDB v5 by providing information based on your recent usage history.
+This tool advises how to prepare an AuraDB v4 instance for migration to AuraDB latest.
+It reports current application queries, drivers, and database objects that would prevent you from migrating to AuraDB latest by providing information based on your recent usage history.
 In addition, you can also see link:https://neo4j.com/docs/aura/tutorials/upgrade/[Upgrade to Neo4j 5 within Aura] for details on each identified issue and how to address it.
 
 The main categories of issues that the Migration Readiness Report deals with are:
@@ -23,8 +23,17 @@ The main categories of issues that the Migration Readiness Report deals with are
 The report page has a section for each category and a chart at the top titled "Deprecations and query timeline."
 This document explains each section, but the first is vital to controlling the others and is detailed in the following section.
 
-Note that the report only highlights issues that need to be addressed to make your code and queries compatible with AuraDB v5.
-Working on these issues presents a good opportunity to learn more about the advantages of the new features in version 5.
+Note that the report only highlights issues that need to be addressed to make your code and queries compatible with AuraDB latest.
+Working on these issues presents a good opportunity to learn more about the advantages of the new features in the latest version.
+
+
+[NOTE]
+====
+From January 2025 Neo4j Server adopted calendar versioning (CalVer).
+Earlier versions, such as Neo4j 4 and 5 used semantic versioning (SemVer).
+Neo4j Aura uses only the latest version.
+====
+
 
 === Control over the time window
 
@@ -64,7 +73,7 @@ Use the button in the popup to fetch applicable data to populate the report's ta
 image::mrr-deprecation-table.png[]
 
 Each row in the table represents a query in the selected timeframe that must be changed to seamlessly migrate to the latest Aura version.
-You have to rewrite those queries to only use v5 supported Cypher.
+You have to rewrite those queries to only use Cypher supported by the latest version.
 
 All executions of the same query are aggregated into one row (see also the "Count" column).
 Use the magnifying glass at the start of each row to access a popup with more information about the query and suggestions on dealing with each issue.

diff --git a/modules/ROOT/pages/platform/security/encryption.adoc b/modules/ROOT/pages/platform/security/encryption.adoc
@@ -22,7 +22,7 @@ These are created and managed using a supported cloud key management service (KM
 Externally, Customer Managed Keys are also known as Customer Managed Encryption Keys (CMEK).
 
 When using a Customer Managed Key, all data at rest is encrypted with the key.
-Customer Managed Keys are supported for v4.x and v5.x instances.
+Customer Managed Keys are supported for v4.x and latest version instances.
 
 When using Customer Managed Keys, you give Aura permission to encrypt and decrypt using the key, but Aura has no access to the key’s material.
 Aura has no control over the availability of your externally managed key in the KMS.
@@ -53,7 +53,7 @@ Depending on the KMS, there may be a delay between disabling a key, and when it
 
 === Import an existing database
 
-You can upload a database to instances encrypted with Customer Managed Keys in Neo4j 5 directly from the console or by using `neo4j-admin database upload`.
+You can upload a database to instances encrypted with Customer Managed Keys in Neo4j latest directly from the console or by using `neo4j-admin database upload`.
 If the database is larger than 4 GB, you have to use `neo4j-admin database upload`.
 Note that the `neo4j-admin push-to-cloud` command in Neo4j v4.4 and earlier is **not** supported for instances encrypted with Customer Managed Keys.
 //For more information see the xref:auradb/importing/import-database.adoc#_neo4j_admin_database_upload[Neo4j Admin `database upload`] documentation.

diff --git a/modules/ROOT/partials/import-database.adoc b/modules/ROOT/partials/import-database.adoc
@@ -42,7 +42,7 @@ If the database you want to upload is running an earlier version of Neo4j, pleas
 [CAUTION]
 ====
 The `neo4j-admin push-to-cloud` command in Neo4j 4.4 and earlier is not compatible with instances encrypted with xref:platform/security/encryption.adoc#_customer_managed_keys[Customer Managed Keys].
-Use `neo4j-admin database upload` in Neo4j 5 to upload data to instances encrypted with Customer Managed Keys.
+Use `neo4j-admin database upload` in Neo4j latest to upload data to instances encrypted with Customer Managed Keys.
 
 For Neo4j 4.x instances in Azure encrypted with Customer Managed Keys, use Neo4j Data Importer to load data, as `neo4j-admin database upload` is not supported.
 See the https://neo4j.com/docs/data-importer/current/introduction[Data Importer documentation] for more information.