Consistent naming

Liam-Doodson · Liam-Doodson · commit 5e5be2e60165 · 2025-01-09T10:45:21.000Z
diff --git a/modules/ROOT/pages/aura-graphql-data-apis/authentication-providers.adoc b/modules/ROOT/pages/aura-graphql-data-apis/authentication-providers.adoc
@@ -7,7 +7,7 @@ There are advantages and disadvantages of both types. API keys are quick to star
 
 [NOTE]
 ====
-`--data-api-id` is used with the `aura-cli` when working with authentication providers rather than `--graphql-api-id` as you might have expected. Conceptually a graphql api is a type of data api and there may be other types in the future. Using `--data-api-id` allows for flexibility for potential future development work in this area.
+`--data-api-id` is used with the `aura-cli` when working with authentication providers rather than `--graphql-api-id` as you might have expected. Conceptually a GraphQL API is a type of Data API and there may be other types in the future. Using `--data-api-id` allows for flexibility for potential future development work in this area.
 ====
 
 == Create a JWKS Authentication Provider
diff --git a/modules/ROOT/pages/aura-graphql-data-apis/deploy-and-operate.adoc b/modules/ROOT/pages/aura-graphql-data-apis/deploy-and-operate.adoc
@@ -1,19 +1,19 @@
 = Deploy and Operate
 
-== Deploy a GraphQL Data API
+== Deploy a GraphQL API
 
 
-Deploying a GraphQL Data API requires you first to have completed the steps in xref::/aura-graphql-data-apis/prerequisites.adoc[Prerequisites]. Of particular importance is that you have:
+Deploying a GraphQL API requires you first to have completed the steps in xref::/aura-graphql-data-apis/prerequisites.adoc[Prerequisites]. Of particular importance is that you have:
 
 * The ID, username and password for the AuraDB
 * A file containing the type definitions
 
-You are now ready to create the GraphQL Data API with the Aura CLI. Substitute the values in `CAPITALS` to match your setup:
+You are now ready to create the GraphQL API with the Aura CLI. Substitute the values in `CAPITALS` to match your setup:
 
 [source, bash, indent=0]
 ----
-aura-cli data-api graphql create --name YOUR-FRIENDLY-NAME --instance-id YOUR-AURA-INSTANCE-ID --instance-username YOUR-AURA-INSTANCE-USER --instance-password YOUR-AURA-INSTANCE-PASSWORD --type-definitions-file
-FULL-PATH-TO-YOUR-TYPE-DEFS --await
+aura-cli data-api graphql create --name YOUR_FRIENDLY_NAME --instance-id YOUR_AURA_INSTANCE_ID --instance-username YOUR_AURA_INSTANCE_USER --instance-password YOUR_AURA_INSTANCE_PASSWORD --type-definitions-file
+FULL_PATH_TO_YOUR_TYPE_DEFS --await
 ----
 
 [NOTE]
@@ -23,51 +23,51 @@ Make sure to record the API key shown in the response as it will not be displaye
 
 There are other items of note in the response:
 
-* `id`: unique identifier for the GraphQL Data API
-* `status`: tells you if the GraphQL Data API is ready to receive requests
-* `url`: the connection address to access the Data API
+* `id`: unique identifier for the GraphQL API
+* `status`: tells you if the GraphQL API is ready to receive requests
+* `url`: the connection address to access the GraphQL API
 
-To check if the GraphQL Data API is ready for requests, use the Aura CLI again, changing `YOUR-AURA-INSTANCE-ID` for the ID of your aura instance.
+To check if the GraphQL API is ready for requests, use the Aura CLI again, changing `YOUR_AURA_INSTANCE_ID` for the ID of your aura instance.
 
 [source, bash, indent=0]
 ----
-aura-cli data-api graphql list --instance-id YOUR-AURA-INSTANCE-ID
+aura-cli data-api graphql list --instance-id YOUR_AURA_INSTANCE_ID
 ----
 
-When the status changes to `ready`, the GraphQL Data API is available for servicing requests.
+When the status changes to `ready`, the GraphQL API is available for servicing requests.
 
-== Modifying an Existing GraphQL Data API
+== Modifying an Existing GraphQL API
 
-It is possible to change the configuration of an existing GraphQL Data API. The following properties can be modified:
+It is possible to change the configuration of an existing GraphQL API. The following properties can be modified:
 
-* Friendly name of the GraphQL Data API
+* Friendly name of the GraphQL API
 * Username and/or password for the associated Aura instance
 * Type definitions
 
-To do this, use the Aura CLI update command which requires IDs of the GraphQL Data API and it’s linked AuraDB instance. The format of this Aura CLI command is as follows:
+To do this, use the Aura CLI update command which requires IDs of the GraphQL API and it’s linked AuraDB instance. The format of this Aura CLI command is as follows:
 
 [source, bash, indent=0]
 ----
-aura-cli data-api graphql update YOUR-DATA-API-ID --instance-id YOUR-AURA-INSTANCE-ID <flags>
+aura-cli data-api graphql update YOUR_GRAPHQL_API_ID --instance-id YOUR_AURA_INSTANCE_ID <flags>
 ----
 
-As the change takes a few moments to fully implement, you should check the status of the GraphQL Data API after performing this operation; if the status is `updating` then the change is still being processed. When the change is committed, the status will return to `ready`.
+As the change takes a few moments to fully implement, you should check the status of the GraphQL API after performing this operation; if the status is `updating` then the change is still being processed. When the change is committed, the status will return to `ready`.
 
 
-Additionally, it is possible to modify the authentication providers of a GraphQL Data APIs. More on what these are and how to do this xref::/aura-graphql-data-apis/authentication-providers.adoc[here].
+Additionally, it is possible to modify the authentication providers of GraphQL APIs. More on what these are and how to do this xref::/aura-graphql-data-apis/authentication-providers.adoc[here].
 
-== Deleting a GraphQL Data API
+== Deleting a GraphQL API
 
-When you no longer require the GraphQL Data API then delete it by using the Aura CLI delete command. This will require the Aura instance ID and ID of the GraphQL Data API.
+When you no longer require the GraphQL API then delete it by using the Aura CLI delete command. This will require the Aura instance ID and ID of the GraphQL API.
 
 The format of this command is as follows:
 
 [source, bash, indent=0]
 ----
-aura-cli data-api graphql delete YOUR-DATA-API-ID --instance-id YOUR-AURA-INSTANCE-ID
+aura-cli data-api graphql delete YOUR_GRAPHQL_API_ID --instance-id YOUR_AURA_INSTANCE_ID
 ----
 
 [NOTE]
 ====
-There is no additional confirmation - the GraphQL Data API will start to be deleted as soon as you press the Enter key!
+There is no additional confirmation - the GraphQL API will start to be deleted as soon as you press the Enter key!
 ====
diff --git a/modules/ROOT/pages/aura-graphql-data-apis/index.adoc b/modules/ROOT/pages/aura-graphql-data-apis/index.adoc
@@ -2,13 +2,13 @@
 
 == Foreword
 
-Welcome to the beta release of *GraphQL Data APIs for Neo4j AuraDB*.
+Welcome to the beta release of *GraphQL for Neo4j AuraDB*.
 
 We are thrilled to have you join us at this exciting stage of our journey. Participating is more than just trying out this feature – your feedback and insights will directly influence how we refine and evolve its future to meet the needs of users like you.
 
-This beta release is designed to give you a first look at *GraphQL Data APIs for Neo4j AuraDB*. While we’ve worked hard to ensure a functional and valuable experience, there is the chance that you may encounter suboptimal behavior. We see these occasions as chances to listen, learn, and improve before *GraphQL for Neo4j AuraDB* is released to all of our customers.
+This beta release is designed to give you a first look at *GraphQL for Neo4j AuraDB*. While we’ve worked hard to ensure a functional and valuable experience, there is the chance that you may encounter suboptimal behavior. We see these occasions as chances to listen, learn, and improve before *GraphQL for Neo4j AuraDB* is released to all of our customers.
 
-Here’s how you can help us get *GraphQL Data APIs for Neo4j AuraDB* ready for production:
+Here’s how you can help us get *GraphQL for Neo4j AuraDB* ready for production:
 
 - *Dive in*: Explore and test its features to your heart’s content.
 - *Break stuff*: We’d rather discover weak areas at this stage – go for it, don’t hold back.
diff --git a/modules/ROOT/pages/aura-graphql-data-apis/prerequisites.adoc b/modules/ROOT/pages/aura-graphql-data-apis/prerequisites.adoc
@@ -4,7 +4,7 @@ Management of the beta of GraphQL for Neo4j AuraDB is performed using the Aura C
 
 == Read This Before you Start
 
-Using the Data API during the Open Beta will be at no cost to you. Usage of the associated AuraDB instance will be charged as normal unless you’re using Aura Pro Trials which, as the name suggests, is a zero-cost option.
+Using the GraphQL API during the Open Beta will be at no cost to you. Usage of the associated AuraDB instance will be charged as normal unless you’re using Aura Pro Trials which, as the name suggests, is a zero-cost option.
 
 At the end of the beta period, all running GraphQL endpoints will be terminated and destroyed in preparation for the full release. Notification of this will be sent out two weeks before GraphQL endpoints are withdrawn.
 
@@ -57,7 +57,7 @@ image::aura-graphql-data-apis/console-classic-api-keys.png[]
 +
 [NOTE]
 ====
-We advise using at least version 1.1.0 for managing your GraphQL Data APIs
+We advise using at least version 1.1.0 for managing your GraphQL APIs
 ====
 +
 . Download the compressed file that matches your computer. Make a note of the folder where the file is located
@@ -138,7 +138,7 @@ aura-cli data-api graphql
 +
 [source, bash, indent=0]
 ----
-Allows you to programmatically provision and manage your GraphQL Data APIs
+Allows you to programmatically provision and manage your GraphQL APIs
 
 Usage:
   aura-cli data-api graphql [command]
@@ -167,7 +167,7 @@ Use "aura-cli data-api graphql [command] --help" for more information about a co
 
 == Author GraphQL Type Definitions
 
-Before you create a GraphQL Data API for use with an Aura instance, you must have type definitions ready for use.
+Before you create a GraphQL API for use with an Aura instance, you must have type definitions ready for use.
 
 If you already have type definitions from an existing GraphQL implementation these can be used but some exceptions need to be dealt with as these are not currently supported.
 
@@ -178,10 +178,10 @@ Using the https://graphql-toolbox.neo4j.io/[Neo4j GraphQL Toolbox] is an easy wa
 
 [NOTE]
 ====
-The *Neo4j GraphQL Toolbox* currently, supports version 6 of the `@neo4j/graphql` library. However, GraphQL Data APIs run the version 7 alpha. As a result, type definitions created via the toolbox may not be valid with a GraphQL Data API. You can find a list of the breaking changes https://github.com/neo4j/graphql/releases?q=%40neo4j%2Fgraphql%407.0.0-alpha&expanded=true[here].
+The *Neo4j GraphQL Toolbox* currently, supports version 6 of the `@neo4j/graphql` library. However, GraphQL APIs run the version 7 alpha. As a result, type definitions created via the toolbox may not be valid with a GraphQL API. You can find a list of the breaking changes https://github.com/neo4j/graphql/releases?q=%40neo4j%2Fgraphql%407.0.0-alpha&expanded=true[here].
 ====
 
-When your type definitions are ready, save them to a file. They will be used with the Aura CLI to create the GraphQL Data API.
+When your type definitions are ready, save them to a file. They will be used with the Aura CLI to create the GraphQL API.
 
 == Select the AuraDB Instance To Use
 
@@ -192,6 +192,6 @@ At the command prompt, type:
 aura-cli instance list
 ----
 
-Your AuraDB instances will be displayed along with their IDs. Make a note of the ID for the AuraDB instance that you will use with the GraphQL Data API.
+Your AuraDB instances will be displayed along with their IDs. Make a note of the ID for the AuraDB instance that you will use with the GraphQL API.
 
 After choosing an AuraDB to use and obtaining it’s ID, you must also have its username and password to use for authentication. For AuraDB, the username will likely be neo4j and the password would have been shown when it was created. If you do not have this information you cannot proceed with this instance.
