review suggestions

Author: rsill-neo4j

modules/ROOT/pages/directives/custom-logic.adoc

@@ -498,6 +498,11 @@ type Journal implements Publication @node {
 
 == `@populatedBy`
 
+[NOTE]
+====
+Data APIs created in Aura Console currently do not support the `@populatedBy` directive. 
+====
+
 This directive is used to specify a callback function, which is executed during GraphQL query parsing,
 to populate fields which have not been provided within the input.
 

modules/ROOT/pages/directives/indexes-and-constraints.adoc

@@ -168,6 +168,11 @@ query {
 [#_vector_index_search]
 == `@vector`
 
+[NOTE]
+====
+Data APIs created in Aura Console currently do not support the `@vector` directive. 
+====
+
 With the `@vector` GraphQL directive you can query your database to perform a vector index search.
 Queries are performed by passing in either a vector index or a query phrase.
 

modules/ROOT/pages/getting-started/graphql-aura.adoc

@@ -11,6 +11,7 @@ In the Aura Console, select **Data services** > **Data APIs** from the left side
 === Details
 
 Provide a name for your new API as well the instance data for the instance you want to use under **Details**.
+Also do **Enable introspection** and **Enable field suggestions** for use with xref:#_via_apollo_server[Apollo Server].
 
 [CAUTION]
 ====

modules/ROOT/pages/getting-started/toolbox.adoc

@@ -40,6 +40,11 @@ type Category @node {
 
 image::toolbox-schema-view.png[GraphQL Toolbox schema view]
 
+[NOTE]
+====
+If you modified your database after following the xref:getting-started/graphql-self-hosted.adoc[self-hosted GraphQL tutorial], you may see different introspection results.
+====
+
 
 == Build the schema and query the database
 

modules/ROOT/pages/index.adoc

@@ -25,17 +25,14 @@ The Neo4j GraphQL Library features:
 - xref::/types/index.adoc[Types], including temporal and spatial.
 - Support for both node and relationship properties.
 - Extensibility through the xref::/directives/custom-logic.adoc#_cypher[`@cypher` directive] and/or xref::/directives/custom-logic.adoc#_customresolver[Custom Resolvers].
-- Extensive xref::filtering.adoc[Filtering] and xref::queries-aggregations/sorting.adoc[Sorting] options.
+- Extensive xref::filtering.adoc[Filtering], xref::queries-aggregations/sorting.adoc[Sorting] and xref::/queries-aggregations/pagination.adoc[Pagination] options.
 - Options for xref::/directives/database-mapping.adoc[Database mapping] and value xref::/directives/autogeneration.adoc[Autogeneration].
-- xref::/queries-aggregations/pagination.adoc[Pagination] options.
 - xref::/security/index.adoc[Security options] and additional xref::schema-configuration/index.adoc[Schema Configuration].
 - A xref::getting-started/toolbox.adoc[Toolbox] (UI) to experiment with your Neo4j GraphQL API on Neo4j Desktop.
 
 
 == Interaction
 
-// Modify link below and add info about aura graphql
-
 In xref::getting-started/graphql-aura.adoc[] as well as xref::getting-started/graphql-self-hosted.adoc[], a GraphQL server is used to serve the GraphQL schema, so you can interact directly with your API with no frontend.
 In case you prefer to use frontend frameworks, these are some clients that interact with GraphQL APIs:
 
@@ -47,8 +44,11 @@ In case you prefer to use frontend frameworks, these are some clients that inter
 == Deployment
 
 There are a variety of methods for deploying GraphQL APIs.
-In the xref::getting-started/index.adoc[Getting Started] guide, Apollo Server is being used for demonstration.
-You can check their own documentation about https://www.apollographql.com/docs/apollo-server/deployment[Deployment] for more details.
+
+With Aura Console, you can create and use a GraphQL API, see xref::getting-started/graphql-aura.adoc[].
+
+The xref::getting-started/graphql-self-hosted.adoc[] guide uses Apollo Server.
+You can check the Apollo documentation on https://www.apollographql.com/docs/apollo-server/deployment[Deployment] for more details.
 
 
 == Versioning

modules/ROOT/pages/security/subscriptions-authorization.adoc

@@ -2,6 +2,11 @@
 :description: This page describes how to set up authorization features for subscriptions in the Neo4j GraphQL Library.
 = Subscriptions authorization
 
+[NOTE]
+====
+Data APIs created in Aura Console currently do not support the `subscriptionsAuthorization` directive. 
+====
+
 Subscriptions require their own authorization rules, which are configured with the `@subscriptionsAuthorization` directive.
 These rules are different to authorization rules for queries and mutations because they use filtering rules available for subscriptions events. 
 These filtering rules can only be used to filter against the properties of the nodes impacted by the events.