Skip to content

Commit f5aa8f6

Browse files
committed
Coherent code and explanation
Fixes #1805
1 parent a4c453a commit f5aa8f6

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

website/src/pages/docs/data/mutations.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -218,7 +218,7 @@ class PostComponent {
218218

219219
constructor(private readonly apollo: Apollo) {}
220220

221-
upvote({ postId, title }) {
221+
changePostTitle({ postId, title }) {
222222
this.apollo
223223
.mutate({
224224
mutation: CHANGE_POST_TITLE,
@@ -238,9 +238,9 @@ class PostComponent {
238238
```
239239

240240
For the example above, it is easy to construct an optimistic response, since we know the shape of
241-
the new comment and can approximately predict the created date. The optimistic response doesn't have
242-
to be exactly correct because it will always will be replaced with the real result from the server,
243-
but it should be close enough to make users feel like there is no delay.
241+
the new post and can predict the new title. The optimistic response doesn't have to be exactly
242+
correct because it will always be replaced with the real result from the server, but it should be
243+
close enough to make users feel like there is no delay.
244244

245245
<Callout>
246246
As this comment is *new* and not visible in the UI before the mutation, it won't appear

0 commit comments

Comments
 (0)