From 669288e658eb7997747f517ba0835c04bebf780b Mon Sep 17 00:00:00 2001 From: Natzy Date: Tue, 26 Aug 2014 19:31:16 +0530 Subject: [PATCH] Spelling mistake correction! From deserilaized to deserialized. --- docs/errors.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/errors.asciidoc b/docs/errors.asciidoc index 3fe1cbb1a..e10d6f843 100644 --- a/docs/errors.asciidoc +++ b/docs/errors.asciidoc @@ -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. \ No newline at end of file +`Generic`:: Elasticsearch responded with a status that does not map to it's own error type.