Skip to content

Commit bd30fe1

Browse files
authored
Update Section 7 -- Response.md
1 parent 9c62584 commit bd30fe1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

spec/Section 7 -- Response.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ If the `data` entry in the response is present (including if it is the value
6363
{null}), the `errors` entry in the response may contain any field errors that
6464
were raised during execution.
6565

66-
**Request errors**
66+
**Request Errors**
6767

6868
Request errors are raised before execution begins. This may occur due to a parse
6969
grammar or validation error in the request document, an inability to determine
@@ -74,7 +74,7 @@ Request errors are typically the fault of the requesting client.
7474
If a request error is raised, execution does not begin and the `data` entry in
7575
the response must not be present. The `errors` entry must include the error.
7676

77-
**Field errors**
77+
**Field Errors**
7878

7979
Field errors are raised during execution from a particular field. This may occur
8080
due to an internal error during value resolution or failure to coerce the
@@ -87,7 +87,7 @@ is produced (see [Handling Field Errors](#sec-Handling-Field-Errors)). The
8787
`data` entry in the response must be present. The `errors` entry should include
8888
all raised field errors.
8989

90-
**Error result format**
90+
**Error Result Format**
9191

9292
Every error must contain an entry with the key `message` with a string
9393
description of the error intended for the developer as a guide to understand and

0 commit comments

Comments
 (0)