clean-up

modules/ROOT/pages/directives/index.adoc

@@ -11,7 +11,7 @@ The Neo4j GraphQL Library provides the following directives to be used whilst de
 |===
 | Directive | Description
 
-| xref::/security/authentication.adoc#_authentication[`@authentication`]
+| xref::/security/authentication.adoc[`@authentication`]
 | Requires authentication checks when accessing the type.
 
 | xref::/security/authorization.adoc[`@authorization`]

modules/ROOT/pages/security/authentication.adoc

@@ -9,10 +9,6 @@ Explicit authentication, configured with the `@authentication` directive, is onl
 Unauthenticated requests with queries requiring authentication never reach the database.
 ====
 
-== Definition
-
-// tba
-
 == Operations
 
 Authentication can be configured to only be validated on certain operations:

modules/ROOT/pages/security/index.adoc

@@ -10,4 +10,4 @@ auth/authorization/where.adoc, authentication-and-authorization/index.adoc
 * xref::/security/authorization.adoc[Authorization] - Rule-based authorization filtering and validation with the `@authorization` directive. 
 * xref::/security/subscriptions-authorization.adoc[Subscriptions authorization] - Rule-based authorization for subscriptions with the `@subscriptionsAuthorization` directive.
 * xref::/security/impersonation-and-user-switching.adoc[Impersonation and user switching] - How to set up impersonation and user switching features.
-* xref::/security/operations.adoc[Operations] - GraphQL query examples on how to trigger the evaluation of different authentication and authorization rules.
+* xref::/security/operations.adoc[Operation examples] - GraphQL query examples on how to trigger the evaluation of different authentication and authorization rules.

modules/ROOT/pages/security/operations.adoc

@@ -1,4 +1,4 @@
-= Operations
+= Operation examples
 //:page-aliases: /authentication-and-authorization/reference/operations.adoc, /security/reference/operations.adoc
 :description: This page describes how to set up authorization operations in the Neo4j GraphQL Library.
 
@@ -21,9 +21,7 @@ This also applies if the directive has no arguments because `operations` default
 
 The following examples apply to the `@authentication` directive, and also any rules within an `@authorization` directive.
 
-== Examples
-
-=== Query
+== Query
 
 For a simple query, rules with `READ` in the operations are evaluated for any type being read:
 
@@ -39,7 +37,7 @@ query {
 }
 ----
 
-=== Mutation
+== Mutation
 
 For `create` mutations, `CREATE` rules on the object are evaluated for each node created, as well as field definition rules:
 
@@ -105,7 +103,7 @@ mutation {
 }
 ----
 
-=== Subscription
+== Subscription
 
 For a simple subscription to creation events, both `SUBSCRIBE` and `READ` operations trigger rules: