@@ -182,7 +182,7 @@ SSL and Authentication
182182~~~~~~~~~~~~~~~~~~~~~~
183183
184184You can configure the client to use ``SSL `` for connecting to your
185- elasticsearch cluster, including certificate verification and http auth::
185+ elasticsearch cluster, including certificate verification and HTTP auth::
186186
187187 from elasticsearch import Elasticsearch
188188
@@ -245,12 +245,12 @@ Environment considerations
245245When using the client there are several limitations of your environment that
246246could come into play.
247247
248- When using an http load balancer you cannot use the :ref: `sniffing `
248+ When using an HTTP load balancer you cannot use the :ref: `sniffing `
249249functionality - the cluster would supply the client with IP addresses to
250250directly connect to the cluster, circumventing the load balancer. Depending on
251251your configuration this might be something you don't want or break completely.
252252
253- In some environments (notably on Google App Engine) your http requests might be
253+ In some environments (notably on Google App Engine) your HTTP requests might be
254254restricted so that ``GET `` requests won't accept body. In that case use the
255255``send_get_body_as `` parameter of :class: `~elasticsearch.Transport ` to send all
256256bodies via post::
@@ -260,13 +260,13 @@ bodies via post::
260260
261261Compression
262262~~~~~~~~~~~
263- When using capacity constrained networks (low throughput), it may be handy to enable
263+ When using capacity- constrained networks (low throughput), it may be handy to enable
264264compression. This is especially useful when doing bulk loads or inserting large
265265documents. This will configure compression on the *request *.
266266::
267267
268268 from elasticsearch import Elasticsearch
269- es = Elasticsearch(hosts, http_compress = True)
269+ es = Elasticsearch(hosts, http_compress= True)
270270
271271
272272Running on AWS with IAM
0 commit comments