@@ -13,7 +13,7 @@ JavaScript that implements that draft, GraphQL.js.
13
13
The reference implementation provides base libraries in JavaScript that would
14
14
provide the basis for full GraphQL implementations and tools. It is not a fully
15
15
standalone GraphQL server that a client developer could use to start
16
- manipulating and querying data. Most importantly it provides no mapping to a
16
+ manipulating and querying data. Most importantly, it provides no mapping to a
17
17
functioning, production-ready backend. The only “backend” we have targeted for
18
18
this early preview are in-memory stubs in test cases.
19
19
@@ -22,12 +22,12 @@ many engineers used this information to implement the parts of the system that
22
22
we discussed publicly. We want to support those engineers by providing both a
23
23
formal specification and a reference implementation for the system as a whole.
24
24
25
- To that end the target audience is not the client developer, but those who have built
26
- or are actively interested in building their own GraphQL implementations and
27
- tools. Critically we also want feedback on the system and to incorporate that
25
+ To that end, the target audience is not the client developer, but those who have
26
+ built or are actively interested in building their own GraphQL implementations and
27
+ tools. Critically, we also want feedback on the system and to incorporate that
28
28
feedback in our final release.
29
29
30
- In order to be broadly adopted GraphQL will have to target a wide
30
+ In order to be broadly adopted, GraphQL will have to target a wide
31
31
variety of backends, frameworks, and languages, which will necessitate a
32
32
collaborative effort across projects and organizations. This technical preview
33
33
marks the beginning of that process.
0 commit comments