Update constraints link following restructure in Cypher Manual (#1874)

Cypher Manual PR: neo4j/docs-cypher#1041

Author: JPryce-Aklundh

modules/ROOT/pages/database-internals/concurrent-data-access.adoc

@@ -125,7 +125,7 @@ The easiest way to work around this is to only read each property once, and keep
 === Missing and double reads
 
 When scanning an xref:performance/index-configuration.adoc[index], entities may be observed multiple times or skipped entirely, even if they are present in the index.
-This is true even for indexes that back link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/constraints/examples/#constraints-examples-node-uniqueness[uniqueness constraints].
+This is true even for indexes that back link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/constraints/managing-constraints/#create-property-uniqueness-constraints[property uniqueness constraints].
 
 During the scan, if another concurrent query changes an entity's property to a position ahead of the scan, the entity might appear again in the index.
 Similarly, the entity may not appear at all if the property is changed to a previously scanned position.

modules/ROOT/pages/database-internals/store-formats.adoc

@@ -174,7 +174,7 @@ For example:
 bin/neo4j-admin database copy --to-format="block" mydb blockdb --copy-schema
 ----
 . After the successful completion, start the database using the Cypher command `START DATABASE mydb`.
-Indexes are populated the first time the database is started, which might take some time if there are uniqueness constraints.
+Indexes are populated the first time the database is started, which might take some time if there are property uniqueness constraints.
 
 [[change-store-format-cluster]]
 ==== In a cluster

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

@@ -976,7 +976,7 @@ This is also true when working with multiple groups.
 For example, you can use `uuid:ID(Person){label:Person}`, where the relationship CSV data can refer to different groups for its `:START_ID` and `:END_ID`, just like the full import method.
 
 * For more information on constraints, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/constraints[Cypher Manual -> Constraints].
-* For examples of creating property uniqueness constraints, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/constraints/examples/#constraints-examples-node-uniqueness[Cypher Manual -> Node property uniqueness constraints].
+* For examples of creating property uniqueness constraints, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/constraints/managing-constraints/#create-property-uniqueness-constraints[Cypher Manual -> Create property uniqueness constraints].
 ====
 
 [[import-tool-header-format-nodes]]