Fix links.

Author: stefano-ottolenghi

modules/ROOT/pages/configuration/dynamic-settings.adoc

@@ -25,7 +25,7 @@ If you want to change the configuration settings on all cluster members, you hav
 [[dynamic-settings-discover]]
 == Discover dynamic settings
 
-Use the procedure `dbms.listConfig()` to discover which configuration values can be dynamically updated, or consult xref:configuration/dynamic-settings.adoc[Dynamic settings reference].
+Use the procedure `dbms.listConfig()` to discover which configuration values can be dynamically updated, or see the list below.
 
 .Discover dynamic settings
 ====
@@ -162,4 +162,4 @@ To reset a config value to its default, pass an empty string as the _value_ argu
 ----
 CALL dbms.setConfigValue('dbms.logs.query.enabled', '')
 ----
-====
+====

modules/ROOT/pages/manage-databases/remote-alias.adoc

@@ -37,7 +37,7 @@ See link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/acces
 
 _Carol_ can use her own regular credentials to access the remote database `Db1` in DBMS after _Alice_ assigns this privilege to her user profile.
 This configuration will also allow _Carol_ to access `Db2` in **DBMS B**.
-If the administrators decide this should not be the case, then _Bob_ must define the appropriate privileges (see link:link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/[Cypher manual -> Access control] for further information).
+If the administrators decide this should not be the case, then _Bob_ must define the appropriate privileges (see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/[Cypher manual -> Access control] for further information).
 
 == Fabric vs remote alias database
 

modules/ROOT/pages/tools/neo4j-admin/unbind.adoc

@@ -51,7 +51,7 @@ For more information about seeding Causal Clusters, see xref:clustering/seed.ado
 [WARNING]
 ====
 If a cluster holds a previous version of any of the databases being seeded, you must `DROP` those databases before seeding.
-Alternatively, you can stop every instance, unbind them from the cluster using xref:tools/neo4j-admin/unbind.adoc[neo4j-admin unbind] and then forcefully restore the correct seeds (backups) for the databases in question.
+Alternatively, you can stop every instance, unbind them from the cluster using `neo4j-admin unbind` and then forcefully restore the correct seeds (backups) for the databases in question.
 If you do not `DROP` or `unbind` before seeding, either with `neo4j-admin restore` or `neo4j-admin load`, the database's store files and cluster state will be out of sync, potentially leading to logical corruptions.
 ====