Skip to content

Commit 689affa

Browse files
committed
unified use of 'GraphQL Library'
1 parent 3c80358 commit 689affa

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

modules/ROOT/pages/deprecations.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,11 @@ The following products and applications are deprecated:
99
1010
== GRANDstack starter app
1111

12-
The main purpose of the GRANDstack starter app was to demonstrate how the Neo4j Labs GraphQL library could be used in the context of a full-stack application using React and Apollo client.
12+
The main purpose of the GRANDstack starter app was to demonstrate how the Neo4j Labs GraphQL Library could be used in the context of a full-stack application using React and Apollo client.
1313
It allowed developers to build applications more quickly and with a bigger focus on functionality, while also helping users who already had an existing frontend and needed a new back end.
1414

1515
Over time, the GRANDstack starter app grew to support other frameworks such as Flutter and Angular, thus the need to revisit its scope.
16-
The intention is to replace this project with a new starter application product, which will focus on the back end and the configuration of the GraphQL library, as well as help developers with their frontend.
16+
The intention is to replace this project with a new starter application product, which will focus on the back end and the configuration of the GraphQL Library, as well as help developers with their frontend.
1717

1818
In the meantime, the `create-grandstack-app` npm package has been marked as deprecated.
1919
It can still be used to skeleton a GRANDstack app, but the user will be warned that the package is deprecated.

modules/ROOT/pages/migration/index.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ The following deprecated `NOT` filters are removed from the schema since they ar
3434
- `edge_NOT`
3535

3636

37-
To achieve the same in version 6.x of the GraphQL library, use the xref:/queries-aggregations/filtering.adoc#_boolean_operators[boolean `NOT` operator] instead.
37+
To achieve the same in version 6.x of the GraphQL Library, use the xref:/queries-aggregations/filtering.adoc#_boolean_operators[boolean `NOT` operator] instead.
3838

3939
[cols="1,1"]
4040
|===
@@ -68,7 +68,7 @@ The following deprecated `_NOT` filters on `@relationship` are removed and no lo
6868
- `actors_NOT`
6969
- `actorsConnection_NOT`
7070

71-
To achieve the same in version 6.x of the GraphQL library, use the `NONE` quantifier.
71+
To achieve the same in version 6.x of the GraphQL Library, use the `NONE` quantifier.
7272

7373
[cols="1,1"]
7474
|===

modules/ROOT/pages/queries-aggregations/filtering.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -440,7 +440,7 @@ query {
440440

441441
== Aggregation filtering
442442

443-
The Neo4j GraphQL library offers an aggregation key inside the `where` argument of each relationship.
443+
The Neo4j GraphQL Library offers an aggregation key inside the `where` argument of each relationship.
444444
You can use it both on the `node` and `edge` of a relationship.
445445

446446
Here are some examples on how to apply this kind of filtering:

0 commit comments

Comments
 (0)