diff --git a/modules/ROOT/pages/introduction/cypher_neo4j.adoc b/modules/ROOT/pages/introduction/cypher_neo4j.adoc
index 10ee3b16f..37a8eea13 100644
--- a/modules/ROOT/pages/introduction/cypher_neo4j.adoc
+++ b/modules/ROOT/pages/introduction/cypher_neo4j.adoc
@@ -55,11 +55,8 @@ Normally there is only one graph within each database, and many administrative c
 Cypher queries executed in a session may declare which graph they apply to, or use a default, given by the session.
 Composite databases can contain multiple graphs, by means of aliases to other databases.
 Queries submitted to composite databases may refer to multiple graphs within the same query.
-
 For more information, see link:{neo4j-docs-base-uri}/operations-manual/{page-version}/composite-databases/[Operations manual -> Composite databases].
 
-Composite databases can contain multiple graphs, by means of aliases to other databases. Queries submitted to composite databases may refer to multiple graphs within the same query. For more information, see Operations manual → Composite databases.
-
 *Database*:: A database is a storage and retrieval mechanism for collecting data in a defined space on disk and in memory.
 
 [[built-in-databases]]
@@ -78,7 +75,7 @@ For more information about the _system_ database, see the sections on xref::admi
 === Query considerations 
 
 Most of the time Cypher queries are reading or updating queries, which are run against a graph. 
-There are also administrative commands that apply to a database, or to the entire DBMS.
+There are also xref:administration/index.adoc[administrative commands] that apply to a database, or to the entire DBMS.
 Administrative commands cannot be run in a session connected to a normal user database, but instead need to be run within a session connected to the `system` database. 
 Administrative commands execute on the `system` database. 
 If an administrative command is submitted to a user database, it is rerouted to the system database.