Skip to content

Commit b36cd7d

Browse files
mandiwisebenjie
andauthored
Apply suggestions from code review.
Co-authored-by: Benjie <[email protected]>
1 parent e02ac49 commit b36cd7d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/pages/learn/index.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,11 @@ import { Callout } from "nextra/components"
44

55
<p className="learn-subtitle">Learn about GraphQL, how it works, and how to use it</p>
66

7-
GraphQL is a query language for your API, and a server-side runtime for executing queries using a type system you define for your data. The [GraphQL specification](https://spec.graphql.org/) was open-sourced in 2015 and has since been implemented in a variety of programming languages. GraphQL also isn't tied to any specific database or storage engine and is instead backed by your existing code and data.
7+
GraphQL is a query language for your API, and a server-side runtime for executing queries using a type system you define for your data. The [GraphQL specification](https://spec.graphql.org/) was open-sourced in 2015 and has since been implemented in a variety of programming languages. GraphQL isn't tied to any specific database or storage engine—it is backed by your existing code and data.
88

99
## Describe your API with a type system
1010

11-
A GraphQL service is created by [defining types and their fields](/learn/schema/), and then writing functions that [provide data for each field](/learn/execution/). For example, a GraphQL service that tells you the name of a logged-in user might look like this:
11+
A GraphQL service is created by [defining types and their fields](/learn/schema/), and then writing a function for each field to [provide the required data](/learn/execution/). For example, a GraphQL service that tells you the name of a logged-in user might look like this:
1212

1313
```graphql
1414
type Query {
@@ -78,7 +78,7 @@ type User {
7878
}
7979
```
8080

81-
GraphQL will continue to provide data as expected for the deprecated `name` field until it's determined that clients have updated their existing queries and the older field can be safely removed.
81+
Client tooling will encourage developers to use the new fields and remove usage of the deprecated `name` field. The field can be removed once it is determined it is no longer used; in the meantime GraphQL will continue to provide its data as expected.
8282

8383
## Try it out!
8484

0 commit comments

Comments
 (0)