diff --git a/docs/error-messaging.md b/docs/error-messaging.md
index d8909d3e..0835b81d 100644
--- a/docs/error-messaging.md
+++ b/docs/error-messaging.md
@@ -43,7 +43,7 @@ type LoginResult {
 
 Depending on success or failure, your mutation resolver may return either an `error` message to be displayed to the user, or `user` that has been logged in. Your API result-handling logic may then interpret the response based on the content of those two keys, only falling back to the main `errors` key to make sure there wasn't an error in query syntax, connection or application.
 
-Likewise, your `Query` resolvers may return `None` instead of requested object, which client developers may interpret as a signal from API to display "Requested item doesn't exist" message the user in place of the requested resource.
+Likewise, your `Query` resolvers may return `None` instead of the requested object, which client developers may interpret as a signal from the API to display a "Requested item doesn't exist" message to the user in place of the requested resource.
 
 
 ## Debugging errors
diff --git a/website/versioned_docs/version-0.11.0/error-messaging.md b/website/versioned_docs/version-0.11.0/error-messaging.md
index f66cc7b9..02e126ee 100644
--- a/website/versioned_docs/version-0.11.0/error-messaging.md
+++ b/website/versioned_docs/version-0.11.0/error-messaging.md
@@ -44,7 +44,7 @@ type LoginResult {
 
 Depending on success or failure, your mutation resolver may return either an `error` message to be displayed to the user, or `user` that has been logged in. Your API result-handling logic may then interpret the response based on the content of those two keys, only falling back to the main `errors` key to make sure there wasn't an error in query syntax, connection or application.
 
-Likewise, your `Query` resolvers may return `None` instead of requested object, which client developers may interpret as a signal from API to display "Requested item doesn't exist" message the user in place of the requested resource.
+Likewise, your `Query` resolvers may return `None` instead of the requested object, which client developers may interpret as a signal from the API to display a "Requested item doesn't exist" message to the user in place of the requested resource.
 
 
 ## Debugging errors
diff --git a/website/versioned_docs/version-0.4.0/error-messaging.md b/website/versioned_docs/version-0.4.0/error-messaging.md
index d84b0873..979d9d9d 100644
--- a/website/versioned_docs/version-0.4.0/error-messaging.md
+++ b/website/versioned_docs/version-0.4.0/error-messaging.md
@@ -44,7 +44,7 @@ type_def = """
 
 Depending on success or failure, your mutation resolver may return either an `error` message to be displayed to the user, or `user` that has been logged in. Your API result handling logic may then interpret the response based on the content of those two keys, only falling back to the main `errors` key to make sure there wasn't an error in query syntax, connection or application.
 
-Likewise, your `Query` resolvers may return `None` instead of requested object, which client developers may interpret as a signal from API to display "Requested item doesn't exist" message the user in place of the requested resource.
+Likewise, your `Query` resolvers may return `None` instead of the requested object, which client developers may interpret as a signal from the API to display a "Requested item doesn't exist" message to the user in place of the requested resource.
 
 
 ## Debugging errors
diff --git a/website/versioned_docs/version-0.6.0/error-messaging.md b/website/versioned_docs/version-0.6.0/error-messaging.md
index 68284547..2cadad74 100644
--- a/website/versioned_docs/version-0.6.0/error-messaging.md
+++ b/website/versioned_docs/version-0.6.0/error-messaging.md
@@ -44,7 +44,7 @@ type_def = """
 
 Depending on success or failure, your mutation resolver may return either an `error` message to be displayed to the user, or `user` that has been logged in. Your API result-handling logic may then interpret the response based on the content of those two keys, only falling back to the main `errors` key to make sure there wasn't an error in query syntax, connection or application.
 
-Likewise, your `Query` resolvers may return `None` instead of requested object, which client developers may interpret as a signal from API to display "Requested item doesn't exist" message the user in place of the requested resource.
+Likewise, your `Query` resolvers may return `None` instead of the requested object, which client developers may interpret as a signal from the API to display a "Requested item doesn't exist" message to the user in place of the requested resource.
 
 
 ## Debugging errors