Skip to content

Commit 139a0a0

Browse files
committed
Merge pull request #93 from alexisvincent/alexisvincent-readme-grammar
Improved grammar for the Introduction and Technical Preview Contents
2 parents f97320a + f92f798 commit 139a0a0

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -16,20 +16,20 @@ The reference implementation provides base libraries in JavaScript that would
1616
provide the basis for full GraphQL implementations and tools. It is not a fully
1717
standalone GraphQL server that a client developer could use to start
1818
manipulating and querying data. Most importantly it provides no mapping to a
19-
functioning, production-ready backend. The only “backend” we have targeted for
20-
this early preview are in-memory stubs in test cases.
19+
functioning, production-ready backend. The only “backend” that we have targeted for
20+
this early preview, are in-memory stubs in test cases.
2121

22-
We are releasing this now because after GraphQL was first discussed publicly,
22+
We are releasing this now, because after GraphQL was first discussed publicly,
2323
many engineers used this information to implement the parts of the system that
2424
we discussed publicly. We want to support those engineers by providing both a
2525
formal specification and a reference implementation for the system as a whole.
2626

27-
To that end the target audience is not the client developer, but those who have
28-
or are actively interested in building their own GraphQL implementations and
29-
tools. Critically we also want feedback on system and to incorporate that
27+
To that end the target audience is not the client developer, but those who have,
28+
or are actively interested in, building their own GraphQL implementations and
29+
tools. Critically we also want feedback on the system and to incorporate that
3030
feedback in our final release.
3131

32-
In order to be broadly adopted GraphQL will have to target a wide
32+
In order to be broadly adopted, GraphQL will have to target a wide
3333
variety of backends, frameworks, and languages, which will necessitate a
3434
collaborative effort across projects and organizations. This technical preview
3535
marks the beginning of that process.

0 commit comments

Comments
 (0)