Remove extra whitespace

mjfwebb · mjfwebb · commit 8063f773f18a · 2025-05-05T10:50:29.000+02:00
diff --git a/modules/ROOT/pages/aura-graphql/api-creation.adoc b/modules/ROOT/pages/aura-graphql/api-creation.adoc
@@ -23,7 +23,7 @@ image::aura-graphql/create/details.png[]
 ====
 If you set **Enable introspection** and **Enable field suggestions** for production systems the information they provide can be used by malicious actors to reverse-engineer your GraphQL schema and execute arbitrary operations.
 
-**Enable introspection** allows you to query the schema and discover the available queries, mutations, subscriptions, types and fields in the GraphQL API.  
+**Enable introspection** allows you to query the schema and discover the available queries, mutations, subscriptions, types and fields in the GraphQL API.
 
 **Enable field suggestions** provides suggestions that hint towards GraphQL typos.
 Even with just field suggestions enabled, it is possible for a malicious actor to discover your entire schema.
@@ -32,9 +32,9 @@ Even with just field suggestions enabled, it is possible for a malicious actor t
 . Type definitions
 +
 This is where you describe the graph database in the AuraDB that the GraphQL API will be used with.
-The Type Definitions are the same as those used with Neo4j GraphQL Library with the exception that custom resolvers cannot be used.    
+The Type Definitions are the same as those used with Neo4j GraphQL Library with the exception that custom resolvers cannot be used.
 +
-If you already have data in the AuraDB, a quick way to obtain Type Definitions is to use the https://graphql-toolbox.neo4j.io[Neo4j GraphQL Toolbox].  This facility has the ability to connect to an AuraDB, automatically create Type Definitions and allow GraphQL operations.  
+If you already have data in the AuraDB, a quick way to obtain Type Definitions is to use the https://graphql-toolbox.neo4j.io[Neo4j GraphQL Toolbox]. This facility has the ability to connect to an AuraDB, automatically create Type Definitions and allow GraphQL operations.
 +
 Alternatively you can write your own Type Definition from first principles by following the guidance provided in xref:index.adoc[Neo4j GraphQL Library] documention
 +
@@ -51,13 +51,13 @@ This includes development environments such as node.js, which serves content on
 This also holds for using web-based tooling for GraphQL APIs such as https://studio.apollographql.com/[Apollo Studio].
 +
 This is not needed if a non-browser-based application is using the GraphQL API as CORS does not apply to those.
-For example, if you are trying out GraphQL operations using cURL. 
+For example, if you are trying out GraphQL operations using cURL.
 +
 [NOTE]
 ====
 The URL entered in the CORS policy must be an exact match.
 For example, http://localhost is not the same as http://localhost:3000/.
-Wildcards are not supported. 
+Wildcards are not supported.
 ====
 +
 To add a CORS policy entry, enter the exact URL, including HTTP/S and any port number, in the **Origin box**.
@@ -68,12 +68,12 @@ image::aura-graphql/create/cors-policy.png[]
 . Authentication providers
 +
 All requests to the GraphQL API are authenticated and there are two options for the type of authentication: API key or JSON Web Key Set (JWKS).
-It is possible to use these in combination and have multiples of each.   
+It is possible to use these in combination and have multiples of each.
 +
 After choosing the authentication provider from the dropdown list, enter a friendly name.
 This is all that is needed when using API key.
 The API key will be shown after the GraphQL API key has been created.
-If you are using JWKS, provide a friendly name and the URL from your identity provider that is used to verify JWKS tokens. 
+If you are using JWKS, provide a friendly name and the URL from your identity provider that is used to verify JWKS tokens.
 +
 Add more more providers via **Add authentication provider**.
 +
@@ -92,7 +92,7 @@ A 3rd party identity provider with JWKS provides better security and allows for
 +
 Sizing a GraphQL API is based on the size and complexity of the type definitions and the workload that is serviced.
 Larger sizes have a higher hourly cost.
-If the cost is not displayed, refer to the agreement you have with Neo4j. 
+If the cost is not displayed, refer to the agreement you have with Neo4j.
 +
 image::aura-graphql/create/sizing.png[]
 +
@@ -109,8 +109,8 @@ Store this information securely as it cannot be retrieved again.
 Select **I understand** and then **Close** once you have done this.
 +
 image::aura-graphql/create/save-api-key.png[]
-+ 
-. The GraphQL API will now be provisioned.  
++
+. The GraphQL API will now be provisioned.
 You can see the status via **Data APIs** from the left side navigation.
 When the status changes to "Ready", the API is ready to use.
 If it has a status of 'Error', use the three dots icon and **Edit** from the menu to change the configuration.
@@ -124,7 +124,7 @@ The authentication providers can be modified using subsequent CLI commands.
 
 To create a GraphQL API with the Aura CLI, proceed as follows.
 
-. Find the AuraDB instance ID 
+. Find the AuraDB instance ID
 +
 From the table, locate the ID of the Aura instance that the GraphQL API will be used with.
 +
@@ -135,7 +135,7 @@ aura-cli instance list
 +
 . Save type definitions
 +
-To avoid having to encode type definitions into base64 format to use directly with the Aura CLI, save them in a file.  
+To avoid having to encode type definitions into base64 format to use directly with the Aura CLI, save them in a file.
 +
 . Create
 +
@@ -150,7 +150,7 @@ The response shows information about the new GraphQL API.
 Make sure you note the API Key and ID.
 +
 . Check progress
-+ 
++
 To see if the GraphQL API is ready to use, run the following command:
 +
 [source, bash, indent=0]
@@ -159,4 +159,3 @@ aura-cli data-api graphql get YOUR_GRAPHQL_API_ID --instance-id YOUR_AURA_INSTAN
 ----
 
 If the status is "Ready", the API is ready to use.
-
diff --git a/modules/ROOT/pages/aura-graphql/api-deletion.adoc b/modules/ROOT/pages/aura-graphql/api-deletion.adoc
@@ -6,7 +6,7 @@
 +
 . Locate the GraphQL API that you wish to delete and use the three dots icon, then **Delete**.
 +
-Confirm the deletion by typing the name of the GraphQL API in the dialog and select **Delete** again. 
+Confirm the deletion by typing the name of the GraphQL API in the dialog and select **Delete** again.
 +
 image::aura-graphql/delete/confirm-deletion.png[]
 
@@ -27,7 +27,7 @@ The Aura CLI does not ask for confirmation and processes the command immediately
 === Looking up the IDs
 
 . Find the ID of the AuraDB.
-+ 
++
 Display a list of AuraDBs in a table:
 +
 [source, bash, indent=0]
@@ -45,11 +45,11 @@ Using the AuraDB ID, list any GraphQL API that it may have:
 ----
 aura-cli data-api graphql list --instance-id YOUR_AURA_INSTANCE_ID
 ----
-+ 
++
 From that table, locate the GraphQL API you want to modify and make a note of its ID.
 
 
-=== Delete the GraphQL API  
+=== Delete the GraphQL API
 
 Using both the AuraDB instance ID and the ID of the associated GraphQL API, you can now delete the GraphQL API itself:
 
diff --git a/modules/ROOT/pages/aura-graphql/api-update.adoc b/modules/ROOT/pages/aura-graphql/api-update.adoc
@@ -26,7 +26,7 @@ When the data API has a status of "Ready", the changes have been applied.
 There are three main commands used by the Aura CLI to modify a GraphQL API:
 
 . `update`: Modify the general settings of a GraphQL Data API.
-. `cors-policy`: Change the Cross-Origin Resource Sharing (CORS) policy. 
+. `cors-policy`: Change the Cross-Origin Resource Sharing (CORS) policy.
 . `auth-provider`: Manage the authentication providers used by the GraphQL API.
 
 
@@ -43,7 +43,7 @@ The Aura CLI does not ask for confirmation and processes a command immediately.
 === Looking up the IDs
 
 . Find the ID of the AuraDB.
-+ 
++
 Display a list of AuraDBs in a table:
 +
 [source, bash, indent=0]
@@ -61,7 +61,7 @@ Using the AuraDB ID, list any GraphQL API that it may have:
 ----
 aura-cli data-api graphql list --instance-id YOUR_AURA_INSTANCE_ID
 ----
-+ 
++
 From that table, locate the GraphQL API you want to modify and make a note of its ID.
 
 
@@ -72,7 +72,7 @@ Using the IDs of both AuraDB and the GraphQL API, this is achieved with:
 
 [source, bash, indent=0]
 ----
-aura-cli data-api graphql get YOUR_GRAPHQL_API_ID --instance-id YOUR_AURA_INSTANCE_ID 
+aura-cli data-api graphql get YOUR_GRAPHQL_API_ID --instance-id YOUR_AURA_INSTANCE_ID
 ----
 
 
@@ -108,7 +108,7 @@ The authentication method is stored as an authentication provider.
 
 There are advantages and disadvantages to both types.
 API keys are quickly set up but do not allow for access control and should not be used within a user-facing client application.
-JWKS (JSON Web Key Sets) authentication providers require an external identity provider but allow for fine-grained rules around authentication and authorization as part of a GraphQL API type definitions. 
+JWKS (JSON Web Key Sets) authentication providers require an external identity provider but allow for fine-grained rules around authentication and authorization as part of a GraphQL API type definitions.
 
 [CAUTION]
 ====
@@ -121,17 +121,17 @@ We recommend you to use JWKS authentication providers in user-facing client appl
 +
 [source, bash, indent=0]
 ----
-aura-cli data-api graphql auth-provider list --data-api-id YOUR_GRAPHQL_API_ID --instance-id YOUR_AURA_INSTANCE_ID 
+aura-cli data-api graphql auth-provider list --data-api-id YOUR_GRAPHQL_API_ID --instance-id YOUR_AURA_INSTANCE_ID
 ----
 +
 - Get the details of a specific authentication provider:
 +
 [source, bash, indent=0]
 ----
-aura-cli data-api graphql auth-provider get YOUR_AUTH_PROVIDER_ID --data-api-id YOUR_GRAPHQL_API_ID --instance-id YOUR_AURA_INSTANCE_ID 
+aura-cli data-api graphql auth-provider get YOUR_AUTH_PROVIDER_ID --data-api-id YOUR_GRAPHQL_API_ID --instance-id YOUR_AURA_INSTANCE_ID
 ----
 +
-- Add a new API key. 
+- Add a new API key.
   You can create a new API key and mark it as disabled to prevent its use.
   To do that, add `--disabled` to the command.
   It is only possible to enable the key via the Console.
@@ -163,13 +163,13 @@ aura-cli data-api graphql auth-provider delete --name YOUR_FRIENDLY_NAME --type
 
 === `cors-policy`
 
-You can add or remove allowed origins for the CORS policy of the GraphQL API.  
+You can add or remove allowed origins for the CORS policy of the GraphQL API.
 
 - Display the existing allowed origins:
 +
 [source, bash, indent=0]
 ----
-aura-cli data-api graphql get YOUR_GRAPHQL_API_ID --instance-id YOUR_AURA_INSTANCE_ID 
+aura-cli data-api graphql get YOUR_GRAPHQL_API_ID --instance-id YOUR_AURA_INSTANCE_ID
 ----
 +
 - Add a new origin:
diff --git a/modules/ROOT/pages/aura-graphql/aura-cli-configuration.adoc b/modules/ROOT/pages/aura-graphql/aura-cli-configuration.adoc
@@ -15,11 +15,11 @@ To get the credentials, follow these steps depending on which version of the con
 +
 image::aura-graphql/aura-cli/account-dropdown.png[]
 +
-. The menu shows existing API keys if you already have any. 
+. The menu shows existing API keys if you already have any.
 +
 image::aura-graphql/aura-cli/api-keys.png[]
 +
-. Use **Create**, then enter a a name for the API key and confirm with **Create**. 
+. Use **Create**, then enter a a name for the API key and confirm with **Create**.
 +
 image::aura-graphql/aura-cli/api-keys-create.png[]
 +
diff --git a/modules/ROOT/pages/aura-graphql/index.adoc b/modules/ROOT/pages/aura-graphql/index.adoc
@@ -2,4 +2,4 @@
 
 Welcome to GraphQL for Neo4j AuraDB.
 
-If you would like to provide feedback, use our `#graphql` channel on our link:https://discord.gg/M8mTADEJ[Discord Community], or our link:https://community.neo4j.com/c/drivers-stacks/graphql/33[forums] to report issues, suggest improvements, or ask questions.
+If you would like to provide feedback, use our `#graphql` channel on our link:https://discord.gg/M8mTADEJ[Discord Community], or our link:https://community.neo4j.com/c/drivers-stacks/graphql/33[forums] to report issues, suggest improvements, or ask questions.

Original file line number	Diff line number	Diff line change
`@@ -23,7 +23,7 @@ image::aura-graphql/create/details.png[]`
`23`	`23`	`====`
`24`	`24`	`If you set Enable introspection and Enable field suggestions for production systems the information they provide can be used by malicious actors to reverse-engineer your GraphQL schema and execute arbitrary operations.`
`25`	`25`
`26`		`-Enable introspection allows you to query the schema and discover the available queries, mutations, subscriptions, types and fields in the GraphQL API.`
	`26`	`+Enable introspection allows you to query the schema and discover the available queries, mutations, subscriptions, types and fields in the GraphQL API.`
`27`	`27`
`28`	`28`	`Enable field suggestions provides suggestions that hint towards GraphQL typos.`
`29`	`29`	`Even with just field suggestions enabled, it is possible for a malicious actor to discover your entire schema.`
`@@ -32,9 +32,9 @@ Even with just field suggestions enabled, it is possible for a malicious actor t`
`32`	`32`	`. Type definitions`
`33`	`33`	`+`
`34`	`34`	`This is where you describe the graph database in the AuraDB that the GraphQL API will be used with.`
`35`		`-The Type Definitions are the same as those used with Neo4j GraphQL Library with the exception that custom resolvers cannot be used.`
	`35`	`+The Type Definitions are the same as those used with Neo4j GraphQL Library with the exception that custom resolvers cannot be used.`
`36`	`36`	`+`
`37`		`-If you already have data in the AuraDB, a quick way to obtain Type Definitions is to use the https://graphql-toolbox.neo4j.io[Neo4j GraphQL Toolbox]. This facility has the ability to connect to an AuraDB, automatically create Type Definitions and allow GraphQL operations.`
	`37`	`+If you already have data in the AuraDB, a quick way to obtain Type Definitions is to use the https://graphql-toolbox.neo4j.io[Neo4j GraphQL Toolbox]. This facility has the ability to connect to an AuraDB, automatically create Type Definitions and allow GraphQL operations.`
`38`	`38`	`+`
`39`	`39`	`Alternatively you can write your own Type Definition from first principles by following the guidance provided in xref:index.adoc[Neo4j GraphQL Library] documention`
`40`	`40`	`+`
`@@ -51,13 +51,13 @@ This includes development environments such as node.js, which serves content on`
`51`	`51`	`This also holds for using web-based tooling for GraphQL APIs such as https://studio.apollographql.com/[Apollo Studio].`
`52`	`52`	`+`
`53`	`53`	`This is not needed if a non-browser-based application is using the GraphQL API as CORS does not apply to those.`
`54`		`-For example, if you are trying out GraphQL operations using cURL.`
	`54`	`+For example, if you are trying out GraphQL operations using cURL.`
`55`	`55`	`+`
`56`	`56`	`[NOTE]`
`57`	`57`	`====`
`58`	`58`	`The URL entered in the CORS policy must be an exact match.`
`59`	`59`	`For example, http://localhost is not the same as http://localhost:3000/.`
`60`		`-Wildcards are not supported.`
	`60`	`+Wildcards are not supported.`
`61`	`61`	`====`
`62`	`62`	`+`
`63`	`63`	`To add a CORS policy entry, enter the exact URL, including HTTP/S and any port number, in the Origin box.`
`@@ -68,12 +68,12 @@ image::aura-graphql/create/cors-policy.png[]`
`68`	`68`	`. Authentication providers`
`69`	`69`	`+`
`70`	`70`	`All requests to the GraphQL API are authenticated and there are two options for the type of authentication: API key or JSON Web Key Set (JWKS).`
`71`		`-It is possible to use these in combination and have multiples of each.`
	`71`	`+It is possible to use these in combination and have multiples of each.`
`72`	`72`	`+`
`73`	`73`	`After choosing the authentication provider from the dropdown list, enter a friendly name.`
`74`	`74`	`This is all that is needed when using API key.`
`75`	`75`	`The API key will be shown after the GraphQL API key has been created.`
`76`		`-If you are using JWKS, provide a friendly name and the URL from your identity provider that is used to verify JWKS tokens.`
	`76`	`+If you are using JWKS, provide a friendly name and the URL from your identity provider that is used to verify JWKS tokens.`
`77`	`77`	`+`
`78`	`78`	`Add more more providers via Add authentication provider.`
`79`	`79`	`+`
`@@ -92,7 +92,7 @@ A 3rd party identity provider with JWKS provides better security and allows for`
`92`	`92`	`+`
`93`	`93`	`Sizing a GraphQL API is based on the size and complexity of the type definitions and the workload that is serviced.`
`94`	`94`	`Larger sizes have a higher hourly cost.`
`95`		`-If the cost is not displayed, refer to the agreement you have with Neo4j.`
	`95`	`+If the cost is not displayed, refer to the agreement you have with Neo4j.`
`96`	`96`	`+`
`97`	`97`	`image::aura-graphql/create/sizing.png[]`
`98`	`98`	`+`
`@@ -109,8 +109,8 @@ Store this information securely as it cannot be retrieved again.`
`109`	`109`	`Select I understand and then Close once you have done this.`
`110`	`110`	`+`
`111`	`111`	`image::aura-graphql/create/save-api-key.png[]`
`112`		`-+`
`113`		`-. The GraphQL API will now be provisioned.`
	`112`	`++`
	`113`	`+. The GraphQL API will now be provisioned.`
`114`	`114`	`You can see the status via Data APIs from the left side navigation.`
`115`	`115`	`When the status changes to "Ready", the API is ready to use.`
`116`	`116`	`If it has a status of 'Error', use the three dots icon and Edit from the menu to change the configuration.`
`@@ -124,7 +124,7 @@ The authentication providers can be modified using subsequent CLI commands.`
`124`	`124`
`125`	`125`	`To create a GraphQL API with the Aura CLI, proceed as follows.`
`126`	`126`
`127`		`-. Find the AuraDB instance ID`
	`127`	`+. Find the AuraDB instance ID`
`128`	`128`	`+`
`129`	`129`	`From the table, locate the ID of the Aura instance that the GraphQL API will be used with.`
`130`	`130`	`+`
`@@ -135,7 +135,7 @@ aura-cli instance list`
`135`	`135`	`+`
`136`	`136`	`. Save type definitions`
`137`	`137`	`+`
`138`		`-To avoid having to encode type definitions into base64 format to use directly with the Aura CLI, save them in a file.`
	`138`	`+To avoid having to encode type definitions into base64 format to use directly with the Aura CLI, save them in a file.`
`139`	`139`	`+`
`140`	`140`	`. Create`
`141`	`141`	`+`
`@@ -150,7 +150,7 @@ The response shows information about the new GraphQL API.`
`150`	`150`	`Make sure you note the API Key and ID.`
`151`	`151`	`+`
`152`	`152`	`. Check progress`
`153`		`-+`
	`153`	`++`
`154`	`154`	`To see if the GraphQL API is ready to use, run the following command:`
`155`	`155`	`+`
`156`	`156`	`[source, bash, indent=0]`
`@@ -159,4 +159,3 @@ aura-cli data-api graphql get YOUR_GRAPHQL_API_ID --instance-id YOUR_AURA_INSTAN`
`159`	`159`	`----`
`160`	`160`
`161`	`161`	`If the status is "Ready", the API is ready to use.`
`162`		`-`
Original file line number	Diff line number	Diff line change
`@@ -6,7 +6,7 @@`
`6`	`6`	`+`
`7`	`7`	`. Locate the GraphQL API that you wish to delete and use the three dots icon, then Delete.`
`8`	`8`	`+`
`9`		`-Confirm the deletion by typing the name of the GraphQL API in the dialog and select Delete again.`
	`9`	`+Confirm the deletion by typing the name of the GraphQL API in the dialog and select Delete again.`
`10`	`10`	`+`
`11`	`11`	`image::aura-graphql/delete/confirm-deletion.png[]`
`12`	`12`
`@@ -27,7 +27,7 @@ The Aura CLI does not ask for confirmation and processes the command immediately`
`27`	`27`	`=== Looking up the IDs`
`28`	`28`
`29`	`29`	`. Find the ID of the AuraDB.`
`30`		`-+`
	`30`	`++`
`31`	`31`	`Display a list of AuraDBs in a table:`
`32`	`32`	`+`
`33`	`33`	`[source, bash, indent=0]`
`@@ -45,11 +45,11 @@ Using the AuraDB ID, list any GraphQL API that it may have:`
`45`	`45`	`----`
`46`	`46`	`aura-cli data-api graphql list --instance-id YOUR_AURA_INSTANCE_ID`
`47`	`47`	`----`
`48`		`-+`
	`48`	`++`
`49`	`49`	`From that table, locate the GraphQL API you want to modify and make a note of its ID.`
`50`	`50`
`51`	`51`
`52`		`-=== Delete the GraphQL API`
	`52`	`+=== Delete the GraphQL API`
`53`	`53`
`54`	`54`	`Using both the AuraDB instance ID and the ID of the associated GraphQL API, you can now delete the GraphQL API itself:`
`55`	`55`
Original file line number	Diff line number	Diff line change
`@@ -15,11 +15,11 @@ To get the credentials, follow these steps depending on which version of the con`
`15`	`15`	`+`
`16`	`16`	`image::aura-graphql/aura-cli/account-dropdown.png[]`
`17`	`17`	`+`
`18`		`-. The menu shows existing API keys if you already have any.`
	`18`	`+. The menu shows existing API keys if you already have any.`
`19`	`19`	`+`
`20`	`20`	`image::aura-graphql/aura-cli/api-keys.png[]`
`21`	`21`	`+`
`22`		`-. Use Create, then enter a a name for the API key and confirm with Create.`
	`22`	`+. Use Create, then enter a a name for the API key and confirm with Create.`
`23`	`23`	`+`
`24`	`24`	`image::aura-graphql/aura-cli/api-keys-create.png[]`
`25`	`25`	`+`
Original file line number	Diff line number	Diff line change
`@@ -2,4 +2,4 @@`
`2`	`2`
`3`	`3`	`Welcome to GraphQL for Neo4j AuraDB.`
`4`	`4`
`5`		-If you would like to provide feedback, use our `#graphql` channel on our link:https://discord.gg/M8mTADEJ[Discord Community], or our link:https://community.neo4j.com/c/drivers-stacks/graphql/33[forums] to report issues, suggest improvements, or ask questions.
	`5`	+If you would like to provide feedback, use our `#graphql` channel on our link:https://discord.gg/M8mTADEJ[Discord Community], or our link:https://community.neo4j.com/c/drivers-stacks/graphql/33[forums] to report issues, suggest improvements, or ask questions.