From 1d7a709f440a9679b02fa401bc280580b3978014 Mon Sep 17 00:00:00 2001 From: AlexicaWright <49636617+AlexicaWright@users.noreply.github.com> Date: Thu, 7 Nov 2024 13:59:30 +0100 Subject: [PATCH] fix link --- modules/ROOT/pages/managing-instances/migration-readiness.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/managing-instances/migration-readiness.adoc b/modules/ROOT/pages/managing-instances/migration-readiness.adoc index c3f68a595..5dfedf858 100644 --- a/modules/ROOT/pages/managing-instances/migration-readiness.adoc +++ b/modules/ROOT/pages/managing-instances/migration-readiness.adoc @@ -12,7 +12,7 @@ You can access the report for any version 4 instance via the link through the "M This tool advises how to prepare an AuraDB v4 instance for migration to AuraDB v5. 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. -In addition, you can also see xref:tutorials/upgrade.adoc[Upgrade to Neo4j 5 within Aura] for details on each identified issue and how to address it. +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: