fix and add links from Index and Constraints pages to Privileges sect…

…ion in Ops Manual (neo4j#791)

modules/ROOT/pages/constraints/syntax.adoc

@@ -298,7 +298,7 @@ List constraints in the database, either all or filtered on constraint type.
 
 [NOTE]
 ====
-Listing constraints requires the link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/database-administration/#access-control-database-administration-constraints[`DROP CONSTRAINT` privilege][`SHOW CONSTRAINTS` privilege].
+Listing constraints requires the link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/database-administration/#access-control-database-administration-constraints[`SHOW CONSTRAINTS` privilege].
 ====
 
 The simple version of the command allows for a `WHERE` clause and will give back the default set of output columns:

modules/ROOT/pages/indexes-for-full-text-search.adoc

@@ -56,6 +56,7 @@ The commands and procedures for full-text indexes are listed in the table below:
 | Create full-text node index.
 | `+CREATE FULLTEXT INDEX ...+`
 | Create a node full-text index for the given labels and properties.
+See the xref:indexes-for-search-performance.adoc#indexes-create-indexes[`CREATE INDEX`] command for more details.
 
 | Create full-text relationship index.
 | `+CREATE FULLTEXT INDEX ...+`
@@ -77,14 +78,16 @@ Create a relationship full-text index for the given relationship types and prope
 | Drop full-text index.
 | `+DROP INDEX ...+`
 | Drop the specified index.
+See the xref:indexes-for-search-performance.adoc#indexes-drop-indexes[`DROP INDEX`] command for more details.
+
 
 | Eventually consistent indexes.
 | https://neo4j.com/docs/operations-manual/current/reference/procedures/#procedure_db_index_fulltext_awaiteventuallyconsistentindexrefresh[`db.index.fulltext.awaitEventuallyConsistentIndexRefresh`]
 | Wait for the updates from recently committed transactions to be applied to any eventually-consistent full-text indexes.
 
 | Listing all full-text indexes.
 | `SHOW FULLTEXT INDEXES`
-| Lists all full-text indexes, see xref::indexes-for-search-performance.adoc#indexes-list-indexes[the `SHOW INDEXES` command] for details.
+| Lists all full-text indexes, see the xref::indexes-for-search-performance.adoc#indexes-list-indexes[`SHOW INDEXES`] command for details.
 
 |===
 
@@ -96,6 +99,8 @@ Full-text indexes are created with the `CREATE FULLTEXT INDEX` command.
 An index can be given a unique name when created (or get a generated one), which is used to reference the specific index when querying or dropping it.
 A full-text index applies to a list of labels or a list of relationship types, for node and relationship indexes respectively, and then a list of property names.
 
+Creating a full-text index requires link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/database-administration/#access-control-database-administration-index[the `CREATE INDEX` privilege].
+
 [NOTE]
 ====
 More details about the syntax descriptions can be found xref:administration/index.adoc#administration-syntax[here].
@@ -443,6 +448,7 @@ RETURN
 
 A full-text node index is dropped by using the xref::indexes-for-search-performance.adoc#indexes-drop-an-index[same command as for other indexes], `DROP INDEX`.
 
+Dropping a full-text index requires link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/database-administration/#access-control-database-administration-index[the `DROP INDEX` privilege].
 
 .+DROP INDEX+
 ======

modules/ROOT/pages/indexes-for-search-performance.adoc

@@ -71,7 +71,7 @@ The `+CREATE INDEX+` command is optionally idempotent. This mean that its defaul
 With `IF NOT EXISTS`, no error is thrown and nothing happens should an index with the same name or same schema and index type already exist.
 It may still throw an error if conflicting constraints exist, such as constraints with the same name or schema and backing index type.
 
-Creating an index requires link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration/standard-databases/manage-databases/#manage-databases-stop/authentication-authorization/database-administration/#access-control-database-administration-index[the `CREATE INDEX` privilege].
+Creating an index requires link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/database-administration/#access-control-database-administration-index[the `CREATE INDEX` privilege].
 
 [NOTE]
 ====
@@ -694,7 +694,7 @@ Full output: `+SHOW INDEXES YIELD *+`.
 
 Listing indexes also allows for `WHERE` and `YIELD` clauses to filter the returned rows and columns.
 
-Listing indexes require link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration/standard-databases/manage-databases/#manage-databases-stop/authentication-authorization/database-administration/#access-control-database-administration-index[the `SHOW INDEX` privilege].
+Listing indexes require link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/database-administration/#access-control-database-administration-index[the `SHOW INDEX` privilege].
 
 [discrete]
 === Examples
@@ -810,7 +810,7 @@ The `DROP INDEX` command is optionally idempotent.
 This means that its default behavior is to throw an error if an attempt is made to drop the same index twice.
 With `IF EXISTS`, no error is thrown and nothing happens should the index not exist.
 
-Dropping an index requires link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration/standard-databases/manage-databases/#manage-databases-stop/authentication-authorization/database-administration/#access-control-database-administration-index[the `DROP INDEX` privilege].
+Dropping an index requires link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/database-administration/#access-control-database-administration-index[the `DROP INDEX` privilege].
 
 [discrete]
 === Examples
@@ -1113,9 +1113,8 @@ SHOW [ALL \| FULLTEXT \| LOOKUP \| POINT \| RANGE \| TEXT] INDEX[ES]
 |===
 
 
-Creating an index requires link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration/standard-databases/manage-databases/#manage-databases-stop/authentication-authorization/database-administration/#access-control-database-administration-index[the `CREATE INDEX` privilege],
-while dropping an index requires link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration/standard-databases/manage-databases/#manage-databases-stop/authentication-authorization/database-administration/#access-control-database-administration-index[the `DROP INDEX` privilege] and
-listing indexes require link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration/standard-databases/manage-databases/#manage-databases-stop/authentication-authorization/database-administration/#access-control-database-administration-index[the `SHOW INDEX` privilege].
+Creating an index requires link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/database-administration/#access-control-database-administration-index[the `CREATE INDEX` privilege],
+while dropping an index requires link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/database-administration/#access-control-database-administration-index[the `DROP INDEX` privilege] and listing indexes require link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/database-administration/#access-control-database-administration-index[the `SHOW INDEX` privilege].
 
 xref:planning-and-tuning/query-tuning/using.adoc[Planner hints and the USING keyword] describes how to make the Cypher planner use specific indexes (especially in cases where the planner would not necessarily have used them).
 

modules/ROOT/pages/indexes-for-vector-search.adoc

@@ -79,6 +79,8 @@ Returns the requested number of approximate nearest neighbor nodes and their sim
 You can create vector indexes using the procedure {link-procedures-reference}#procedure_db_index_vector_createNodeIndex[`db.index.vector.createNodeIndex`].
 The name of the index must be unique so that you can reference it when xref:#indexes-vector-query[querying] or if you want to xref:indexes-vector-drop[drop] the index.
 
+Creating a vector index requires link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/database-administration/#access-control-database-administration-index[the `CREATE INDEX` privilege].
+
 [IMPORTANT]
 ====
 The index name must be unique among both indexes and constraints.
@@ -251,6 +253,8 @@ If the query vector itself is not wanted, you can use `WHERE score < 1` to remov
 
 A vector index is dropped by using the xref:indexes-for-search-performance.adoc#indexes-drop-an-index[same command as for other indexes], `DROP INDEX`.
 
+Dropping a vector index requires link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/database-administration/#access-control-database-administration-index[the `DROP INDEX` privilege].
+
 .+DROP INDEX+
 ======