Skip to content

Commit 0487e6f

Browse files
committed
Update subheads.
1 parent ddd7d8c commit 0487e6f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/pages/learn/mutations.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ On this page, you'll learn how to use mutation operations to create, update, and
1818
All of the features of GraphQL operations that apply to queries also apply to mutations, so review the [Queries](/learn/queries/) page first before proceeding.
1919
</Callout>
2020

21-
## Creating data
21+
## Add new data
2222

2323
When creating new data with a REST API, you would send a `POST` request to a specific endpoint and include information about the entities to be created in the body of the request. GraphQL takes a different approach.
2424

@@ -73,7 +73,7 @@ Mutation: {
7373

7474
You can learn more about GraphQL provides data for fields on the [Execution page](/learn/execution).
7575

76-
## Updating data
76+
## Update existing data
7777

7878
Similarly, we use mutations to update existing data. To change a human's name, we'll define a new mutation field and set that field's output type to the `Human` type so we can return the updated human's information to client after the server successfully writes the data:
7979

@@ -101,7 +101,7 @@ Purpose-built mutation fields can help make a schema more expressive by allowing
101101

102102
Schemas should be designed to help clients get the data that they need from the GraphQL API, so the fields defined in a schema should be informed by those use cases.
103103

104-
## Deleting data
104+
## Remove existing data
105105

106106
Just as we can send a `DELETE` request to delete a resource with a REST API, we can use mutations to delete some existing data as well by defining another field on the `Mutation` type:
107107

0 commit comments

Comments
 (0)