From a30da8a367fe61a2eedfee9369f2f777e3c0c0f4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jens=20Pryce-=C3=85klundh?=
 <112686610+JPryce-Aklundh@users.noreply.github.com>
Date: Thu, 31 Oct 2024 15:23:20 +0100
Subject: [PATCH 1/2] fix

---
 .../pages/appendix/tutorials/advanced-query-tuning.adoc   | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/modules/ROOT/pages/appendix/tutorials/advanced-query-tuning.adoc b/modules/ROOT/pages/appendix/tutorials/advanced-query-tuning.adoc
index 910b35f78..4c8c953df 100644
--- a/modules/ROOT/pages/appendix/tutorials/advanced-query-tuning.adoc
+++ b/modules/ROOT/pages/appendix/tutorials/advanced-query-tuning.adoc
@@ -15,7 +15,7 @@ Let's explain how to use these features with a more advanced query tuning exampl
 
 [NOTE]
 ====
-If you are upgrading an existing store to {neo4j-version-exact}, it may be necessary to drop and re-create existing indexes.
+If you are upgrading an existing store, it may be necessary to drop and re-create existing indexes.
 For information on native index support and upgrade considerations regarding indexes, see link:{neo4j-docs-base-uri}/operations-manual/{page-version}/performance/index-configuration[Operations Manual -> Performance -> Index configuration].
 ====
 
@@ -936,10 +936,12 @@ Predicates that will not work:
 
 [NOTE]
 ====
-If there is an existence constraint on the property, no predicate is required to trigger the optimization.
+If there is a xref:constraints/managing-constraints.adoc#create-property-existence-constraints[property existence constraint] on the property, no predicate is required to trigger the optimization.
 For example, `CREATE CONSTRAINT constraint_name FOR (p:Person) REQUIRE p.name IS NOT NULL`
 
-As of Neo4j {neo4j-version-exact}, predicates with parameters, such as `WHERE n.prop > $param`, can trigger _index-backed ORDER BY_.
+Predicates with parameters, such as `WHERE n.prop > $param`, can trigger xref:indexes/using-indexes
+
+_index-backed ORDER BY_.
 The only exception are queries with parameters of type `POINT`.
 ====
 

From 61663a308c63cf33ae8ffc16b151430c554cdf6a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jens=20Pryce-=C3=85klundh?=
 <112686610+JPryce-Aklundh@users.noreply.github.com>
Date: Thu, 31 Oct 2024 15:25:29 +0100
Subject: [PATCH 2/2] fix

---
 .../ROOT/pages/appendix/tutorials/advanced-query-tuning.adoc  | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/modules/ROOT/pages/appendix/tutorials/advanced-query-tuning.adoc b/modules/ROOT/pages/appendix/tutorials/advanced-query-tuning.adoc
index 4c8c953df..2546d7b8a 100644
--- a/modules/ROOT/pages/appendix/tutorials/advanced-query-tuning.adoc
+++ b/modules/ROOT/pages/appendix/tutorials/advanced-query-tuning.adoc
@@ -939,9 +939,7 @@ Predicates that will not work:
 If there is a xref:constraints/managing-constraints.adoc#create-property-existence-constraints[property existence constraint] on the property, no predicate is required to trigger the optimization.
 For example, `CREATE CONSTRAINT constraint_name FOR (p:Person) REQUIRE p.name IS NOT NULL`
 
-Predicates with parameters, such as `WHERE n.prop > $param`, can trigger xref:indexes/using-indexes
-
-_index-backed ORDER BY_.
+Predicates with parameters, such as `WHERE n.prop > $param`, can trigger _index-backed ORDER BY_.
 The only exception are queries with parameters of type `POINT`.
 ====