Tweaks for v6

Author: darrellwarde

modules/ROOT/pages/security/authentication.adoc

@@ -65,7 +65,7 @@ Authentication can be configured for an entire type:
 
 [source, graphql, indent=0]
 ----
-type User @authentication {
+type User @authentication @node {
     id: ID!
     name: String!
     password: String!
@@ -89,7 +89,7 @@ Authentication can be configured on a per-field basis, for example:
 
 [source, graphql, indent=0]
 ----
-type User {
+type User @node {
     id: ID!
     name: String!
     password: String! @authentication

modules/ROOT/pages/security/authorization.adoc

@@ -181,7 +181,7 @@ For example, consider a `User` type with a `password` field:
 
 [source, graphql, indent=0]
 ----
-type User {
+type User @node {
     id: ID!
     username: String!
     password: String! @authorization(where: [{ operations: [READ, UPDATE], where: { node: { id: "$jwt.sub" } } }])

modules/ROOT/pages/security/operations.adoc

@@ -68,9 +68,11 @@ For an aggregation query, rules with `AGGREGATE` in the operations are evaluated
 [source, graphql, indent=0]
 ----
 query {
-    moviesAggregate { # AGGREGATE ON OBJECT Movie
-        title {       # AGGREGATE ON FIELD_DEFINITION Movie.title
-            longest
+    moviesConnection { 
+        aggregate {     # AGGREGATE ON OBJECT Movie
+            title {     # AGGREGATE ON FIELD_DEFINITION Movie.title
+                longest
+            }
         }
     }
 }
@@ -82,10 +84,12 @@ The same logic applies to aggregations of nested nodes:
 ----
 query {
     movies {
-        actorsAggregate {   # AGGREGATE ON OBJECT Actor
-            node {
-                name {      # AGGREGATE ON FIELD_DEFINITION Actor.name
-                    longest
+        actorsConnection {
+            aggregate {         # AGGREGATE ON OBJECT Actor
+                node {
+                    name {      # AGGREGATE ON FIELD_DEFINITION Actor.name
+                        longest
+                    }
                 }
             }
         }