habsi/elasticsearch-js
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Typo fixes, mainly misuse of [it’s][oatmeal-1]/[its][oatmeal-2].

Browse Source 
[oatmeal-1]: http://s3.amazonaws.com/theoatmeal-img/comics/apostrophe/4.png
[oatmeal-2]: http://s3.amazonaws.com/theoatmeal-img/comics/apostrophe/5.png
This commit is contained in:
Mat Gadd
2014-12-30 12:05:23 +00:00
parent 3df3b09d3a
commit 0d2c36c8f8
11 changed files with 20 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/errors.asciidoc
View File

@ -7,7 +7,7 @@ These are the standard Error types which may be passed back from the client. To
`ConnectionFault`:: The connection was unable to initiate or complete a request with the Elasticsearch node.
`NoConnections`:: All of the connections in the ConnectionPool are dead.
`RequestTimeout`:: The request timed-out.
`Serialization`:: The response received from Elasticsearch could not be deserilaized.
`Serialization`:: The response received from Elasticsearch could not be deserialized.
`503` or `ServiceUnavailable`:: Elasticsearch responded with a 503 status.
`500` or `InternalServerError`:: Elasticsearch responded with a 500 status.
`412` or `PreconditionFailed`:: Elasticsearch responded with a 412 status.
@ -15,4 +15,4 @@ These are the standard Error types which may be passed back from the client. To
`403` or `Forbidden`:: Elasticsearch responded with a 403 status.
`404` or `NotFound`:: Elasticsearch responded with a 404 status.
`400` or `BadRequest`:: Elasticsearch responded with a 400 status.
`Generic`:: Elasticsearch responded with a status that does not map to it's own error type.
`Generic`:: Elasticsearch responded with a status that does not map to its own error type.