Adding notes about syntax to explain the use of quotation marks (#252)

modules/ROOT/pages/access-control/database-administration.adoc

@@ -57,6 +57,10 @@ This can be quite powerful as it allows permissions to be switched from one data
 * _role[, ...]_
 ** The role or roles to associate the privilege with, comma-separated.
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
 
 .General grant +ON DATABASE+ privilege syntax
 [cols="<15s,<85"]

modules/ROOT/pages/access-control/dbms-administration.adoc

@@ -141,6 +141,11 @@ a|Rows: 3
 The DBMS privileges for role management are assignable using Cypher administrative commands.
 They can be granted, denied and revoked like other privileges.
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 .Role management privileges command syntax
 [options="header", width="100%", cols="3a,2"]
 |===
@@ -370,6 +375,11 @@ a|Rows: 1
 The DBMS privileges for user management can be assigned using Cypher administrative commands.
 They can be granted, denied and revoked like other privileges.
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 .User management privileges command syntax
 [options="header", width="100%", cols="3a,2"]
 |===
@@ -697,6 +707,11 @@ Impersonation is the ability of a user to assume another user's roles (and there
 
 The ability to impersonate users can be granted via the `IMPERSONATE` privilege.
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 .Impersonation privileges command syntax
 [options="header", width="100%", cols="3a,2"]
 |===
@@ -765,6 +780,11 @@ GRANT IMPERSONATE (alice, bob) ON DBMS TO userImpersonator
 The DBMS privileges for database management can be assigned by using Cypher administrative commands.
 They can be granted, denied and revoked like other privileges.
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 .Database management privileges command syntax
 [options="header", width="100%", cols="3a,2"]
 |===
@@ -930,6 +950,11 @@ The DBMS privileges for alias management can be assigned by using Cypher adminis
 They can be granted, denied and revoked like other privileges.
 It is also possible to manage aliases with xref::access-control/dbms-administration.adoc#access-control-dbms-administration-database-management[database management commands].
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 .Alias management privileges command syntax
 [options="header", width="100%", cols="3a,2"]
 |===
@@ -1093,6 +1118,11 @@ a|Rows: 1
 The DBMS privileges for privilege management can be assigned by using Cypher administrative commands.
 They can be granted, denied and revoked like other privileges.
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 .Privilege management privileges command syntax
 [options="header", width="100%", cols="3a,2"]
 |===
@@ -1240,6 +1270,11 @@ a|Rows: 1
 The DBMS privileges for procedure and user defined function execution can be assigned by using Cypher administrative commands.
 They can be granted, denied and revoked like other privileges.
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 .Execute privileges command syntax
 [options="header", width="100%", cols="3a,2"]
 |===
@@ -1821,6 +1856,11 @@ The right to perform the following privileges can be achieved with a single comm
 * Execute all procedures with elevated privileges.
 * Execute all user defined functions with elevated privileges.
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 [source, cypher, role=noplay]
 ----
 GRANT ALL [[DBMS] PRIVILEGES]

modules/ROOT/pages/access-control/manage-privileges.adoc

@@ -31,6 +31,11 @@ If a user was not also provided with the database `ACCESS` privilege, then acces
 Information about the database access privilege can be found in xref::access-control/database-administration.adoc#access-control-database-administration-access[The ACCESS privilege].
 ====
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 
 [role=enterprise-edition]
 [[access-control-graph-privileges]]

modules/ROOT/pages/access-control/manage-roles.adoc

@@ -17,6 +17,11 @@ When connected to the DBMS over `bolt`, administration commands are automaticall
 [[access-control-role-syntax]]
 == Role management command syntax
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 [cols="<15s,<85"]
 |===
 

modules/ROOT/pages/access-control/manage-users.adoc

@@ -15,6 +15,11 @@ When connected to the DBMS over `bolt`, administration commands are automaticall
 [[access-control-user-syntax]]
 == User management command syntax
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 [cols="<15s,<85"]
 |===
 

modules/ROOT/pages/access-control/privileges-reads.adoc

@@ -15,6 +15,10 @@ There are three separate read privileges:
 * xref::access-control/privileges-reads.adoc#access-control-privileges-reads-read[`READ`] - enables the specified properties of the found entities to be read.
 * xref::access-control/privileges-reads.adoc#access-control-privileges-reads-match[`MATCH`] - combines both `TRAVERSE` and `READ`, enabling an entity to be found and its properties read.
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
 
 [[access-control-privileges-reads-traverse]]
 == The `TRAVERSE` privilege

modules/ROOT/pages/access-control/privileges-writes.adoc

@@ -23,6 +23,10 @@ There are also compound privileges which combine the above specific privileges:
 * xref::access-control/privileges-writes.adoc#access-control-privileges-writes-write[`WRITE`] - allows all `WRITE` operations on an entire graph.
 * xref::access-control/privileges-writes.adoc#access-control-privileges-writes-all[`ALL GRAPH PRIVILEGES`] - allows all `READ` and `WRITE` operations on an entire graph.
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
 
 [[access-control-privileges-writes-create]]
 == The `CREATE` privilege

modules/ROOT/pages/aliases.adoc

@@ -28,6 +28,11 @@ When connected to the DBMS over Bolt, administration commands are automatically
 
 The syntax of the alias management commands is as follows:
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 .Alias management command syntax
 [options="header", width="100%", cols="1m,5a"]
 |===
@@ -117,7 +122,6 @@ DROP ALIAS name [IF EXISTS] FOR DATABASE
 
 |===
 
-
 This is the list of the allowed driver settings for remote aliases.
 
 [[remote-alias-driver-settings]]

modules/ROOT/pages/clauses/listing-functions.adoc

@@ -65,6 +65,11 @@ Is `null` without the xref::access-control/dbms-administration.adoc#access-contr
 
 == Syntax
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 List functions, either all or only built-in or user-defined::
 
 [source, syntax, role="noheader", indent=0]

modules/ROOT/pages/clauses/listing-procedures.adoc

@@ -65,6 +65,11 @@ a| Map of extra output, e.g. if the procedure is deprecated.
 
 == Syntax
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 List all procedures::
 
 [source, syntax, role="noheader", indent=0]

modules/ROOT/pages/clauses/transaction-clauses.adoc

@@ -153,6 +153,11 @@ m|STRING
 
 === Syntax
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 List transactions on the current server::
 
 [source, cypher, role="noheader", indent=0]
@@ -297,6 +302,11 @@ m|STRING
 
 === Syntax
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 Terminate transactions by ID on the current server::
 
 [source, cypher, role="noheader", indent=0]

modules/ROOT/pages/constraints/syntax.adoc

@@ -4,6 +4,10 @@
 = Syntax
 :check-mark: icon:check[]
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
 
 [[administration-constraints-syntax-create]]
 == Syntax for creating constraints
@@ -40,7 +44,6 @@ Non-specified settings have their respective default values.
 Creating a constraint requires the xref::access-control/database-administration.adoc#access-control-database-administration-constraints[`CREATE CONSTRAINT` privilege].
 ====
 
-
 [[administration-constraints-syntax-create-unique]]
 [discrete]
 === Create a unique node property constraint

modules/ROOT/pages/databases.adoc

@@ -15,6 +15,11 @@ These administrative commands are automatically routed to the `system` database
 
 The syntax of the database management commands is as follows:
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 .Database management command syntax
 [options="header", width="100%", cols="1m,5a"]
 |===
@@ -80,7 +85,6 @@ DROP DATABASE name [IF EXISTS] [{DUMP\|DESTROY} [DATA]] [WAIT [n [SEC[OND[S]]]]\
 
 |===
 
-
 [[administration-databases-show-databases]]
 == Listing databases
 

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

@@ -108,6 +108,11 @@ 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.
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 .Syntax for creating fulltext indexes
 [options="header", width="100%", cols="5a, 3, 3a"]
 |===

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

@@ -68,6 +68,11 @@ With `IF NOT EXISTS`, no error is thrown and nothing happens should an index wit
 It may still throw an error if conflicting constraints exist, such as constraints with the same name or schema and backing index type.
 ====
 
+[NOTE]
+====
+The syntax descriptions use xref:access-control/index.adoc#access-control-syntax[the style] from access control.
+====
+
 
 .+Create a single-property index on nodes+ label:deprecated[]
 [options="noheader", width="100%", cols="2, 8a"]