Merge pull request #550 from paigecook/docs-cleanup

Fixes to typos, formatting, verbiage, naming conventions, etc.

Author: Mpdreamz

new_docs/contents/elasticsearch-net/building-requests.md

@@ -7,7 +7,7 @@ menuitem: esnet-building-requests
 
 # Building Requests
 
-This section decribes how to build requests to elasticsearch.
+This section decribes how to build requests to Elasticsearch.
 
 ## Calling an API endpoint
 

new_docs/contents/elasticsearch-net/cluster-failover.md

@@ -7,7 +7,7 @@ menuitem: esnet-cluster-failover
 
 # Connection pooling & Cluster failover
 
-One of the major benefits of `elasticsearch` is that it can handle dying and respawning  nodes. 
+One of the major benefits of `Elasticsearch` is that it can handle dying and respawning  nodes. 
 As long as enough nodes agree that the cluster is healthy, the cluster will continue to operate.
 `Elasticsearch.net` comes with builtin support to handle falling over to a different node when the requested node failed.
 
@@ -38,7 +38,7 @@ Sets the timeout before a node is retried. The default `DateTimeProvider` will i
 Sets the maximum time a node may be marked dead.
 
 #### DisablePings()
-By default before a previously dead node is retried a short ping will be send to the node to make sure the node will respond. 
+By default before a previously dead node is retried a short ping will be sent to the node to make sure the node will respond. 
 The reason for a separate call is that a ping will call an elasticsearch endpoint that won't stress the JVM. If a node is having issues retrying a possible heavy search operation on it might cause the request to fail later rather then asap. This setting allows you to disable these pings before retries.
 
 #### SetMaxRetries(int retries)

new_docs/contents/elasticsearch-net/errors.md

@@ -7,7 +7,7 @@ menuitem: esnet-errors
 
 # Errors
 
-`Elasticsearch.Net` will not throw if gets a http response other then 200 from Elasticsearch. The response object's `Success` property will be false and `.Error` will contain information on the failed response.
+`Elasticsearch.Net` will not throw if it gets an http response other then 200 from Elasticsearch. The response object's `Success` property will be false and `.Error` will contain information on the failed response.
 
 You can throw custom exceptions if you need too by specifying a custom connectionhandler
 
@@ -20,7 +20,7 @@ You can throw custom exceptions if you need too by specifying a custom connectio
 
 ## Exceptions
 
-If a request has been retried the maximum amount of times a `MaxRetryException` is thrown. Note that requests are only retried when elasticsearch responds with a `503` or an unspecified connection exception (i.e timeout) occured on a node. 
+If a request has been retried the maximum amount of times a `MaxRetryException` is thrown. Note that requests are only retried when elasticsearch responds with a `503` or an unspecified connection exception (i.e timeout) has occured on a node. 
 
 `MaxRetryException` will hold the original exception as `.InnerException`.
 

new_docs/contents/elasticsearch-net/quick-start.md

@@ -7,7 +7,7 @@ menuitem: esnet-quick-start
 
 # Quick Start
 
-`Elasticsearch.Net` is a low level client to talk to elasticsearch.
+`Elasticsearch.Net` is a low level client to talk to Elasticsearch.
 
 ## Installing
 

new_docs/contents/index.md

@@ -7,7 +7,7 @@ menuitem: introduction
 
 # Introduction
 
-You've reached the documentation page for `Elasticsearch.Net` and `NEST`. Two .net clients to talk with elasticsearch. So why two clients I hear you say?
+You've reached the documentation page for `Elasticsearch.Net` and `NEST`. Two .net clients to talk with Elasticsearch. So why two clients I hear you say?
 
 `Elasticsearch.Net` is a very low level, dependency free, client that has no opinions how you build and represent your requests and responses. It has abstracted 
 enough so that **all** the elasticsearch API endpoints are represented as methods but not too much to get in the way of how you want to build your json/request/response objects. It also comes with builtin, configurable/overridable, cluster failover retry mechanisms. Elasticsearch is elastic so why not your client?
@@ -20,9 +20,9 @@ Please read the getting started guide for both.
 ## Who's using Nest
 * [stackoverflow.com](http://www.stackoverflow.com) (and the rest of the stackexchange family).
 * [7digital.com](http://www.7digital.com) (run NEST on mono).
-* [rijksmuseum.nl](https://www.rijksmuseum.nl/en) (elasticsearch is the only datastorage hit for each page).
+* [rijksmuseum.nl](https://www.rijksmuseum.nl/en) (Elasticsearch is the only datastorage hit for each page).
 * [Kiln](http://www.fogcreek.com/kiln/) FogCreek's version control & code review tooling. 
-  They are so pleased with elasticsearch that [they made a video about how pleased they are!](http://blog.fogcreek.com/kiln-powered-by-elasticsearch/)
+  They are so pleased with Elasticsearch that [they made a video about how pleased they are!](http://blog.fogcreek.com/kiln-powered-by-elasticsearch/)
 
 
 ## Other resources

new_docs/contents/nest/cluster/health.markdown

@@ -11,7 +11,7 @@ Get cluster health simple
 
     var r = this._client.Health(HealthLevel.Cluster);
 
-Cluster health just for one (or more) index
+Cluster health for one (or more) indexes
 
     var r = this._client.Health(new[] { Test.Default.DefaultIndex }, HealthLevel.Cluster);
 

new_docs/contents/nest/cluster/nodes-stats.markdown

@@ -12,7 +12,7 @@ var r = this._client.NodeInfo(NodesInfo.All);
 
             var node = r.Nodes.First();
 
-you can than traverse the node info objects i.e:
+You can than traverse the node info objects i.e:
 
             node.Value.OS.Cpu.CacheSizeInBytes;
 

new_docs/contents/nest/connecting.markdown

@@ -30,12 +30,12 @@ If you want a failover client instead of passing a `Uri` pass an `IConnectionPoo
 
 ## Changing the underlying connection 
 
-By default NEST will use HTTP to chat with elasticsearch, alternative implementation of the transport layer can be injected in the constructors optional second parameter
+By default NEST will use HTTP to chat with elasticsearch, alternative implementation of the transport layer can be injected using the constructors optional second parameter
 
 	var client = new ElasticClient(settings, new ThriftConnection(settings));
 
-Nest comes with a Htpp connection `HttpConnection`, Thrift Connection `ThriftConnection` 
-and an in memory connection that nevers hits elasticsearch `InMemoryConnection`.
+NEST comes with an Http Connection `HttpConnection`, Thrift Connection `ThriftConnection` 
+and an In-Memory Connection `InMemoryConnection`, that nevers hits elasticsearch.
 
 ## Settings
 
@@ -50,8 +50,8 @@ The easiest way to pass `IConnectionSettingsValues` is to instantiate `Connectio
         .PluralizeTypeNames();
 
 ####AddContractJsonConverters
-Add a custom JsonConverter to the build in json serialization by passing
-in a predicate for a type.  This way they will be part of the cached Json.net contract for a type.
+Add a custom JsonConverter to the built in JSON serialization by passing
+in a predicate for a type.  This way they will be part of the cached Json.NET contract for a type.
 
     settings.AddContractJsonConverters(t => 
         typeof (Enum).IsAssignableFrom(t) 
@@ -74,15 +74,15 @@ Index to default to when no index is specified.
 ####SetDefaultPropertyNameInferrer
 By default NEST camelCases property names (EmailAddress => emailAddress)
 that do not have an explicit propertyname either via an ElasticProperty attribute
-or because they are part of Dictionary where the keys should be treated verbatim.
+or because they are part of a Dictionary where the keys should be treated verbatim.
 Here you can register a function that transforms propertynames (default
 casing, pre- or suffixing)
 
 ####SetDefaultTypeNameInferrer
-Allows you to override how type names should be reprented, the default will
+Allows you to override how type names should be represented, the default will
 call .ToLowerInvariant() on the type's name.
 
 ####SetJsonSerializerSettingsModifier
-Allows you to update internal the json.net serializer settings to your liking.
-Do not use this to add custom json converters use `AddContractJsonConverters` instead.
+Allows you to update the internal Json.NET Serializer settings to your liking.
+Do not use this to add custom JSON converters use `AddContractJsonConverters` instead.
 

new_docs/contents/nest/core/bulk.markdown

@@ -8,7 +8,7 @@ menuitem: bulk
 
 # Bulk
 
-Nest long supported bulk index and deletes (through `IndexMany()` and `DeleteMany()`) but this shielded you from all that the elasticsearch `_bulk` api enpoint has to offer. Now you can use `Bulk()` to create any bulk request you'd like. E.g if you want to do index/create/delete's in a certain order.
+NEST long supported bulk index and deletes (through `IndexMany()` and `DeleteMany()`) but this shielded you from all that the Elasticsearch `_bulk` api enpoint has to offer. Now you can use `Bulk()` to create any bulk request you'd like. E.g if you want to do index/create/delete's in a certain order.
 
 # Examples
 
@@ -18,7 +18,7 @@ Nest long supported bulk index and deletes (through `IndexMany()` and `DeleteMan
 		.Delete<ElasticSearchProject>(i => i.Object(new ElasticSearchProject { Id = 4 }))
 	);
 
-Each bulk operation can also be anotated with the right behaviours:
+Each bulk operation can also be annotated with the right behaviours:
 
 	.Index<ElasticSearchProject>(i => i
 		.Routing(...)

new_docs/contents/nest/core/count.markdown

@@ -13,7 +13,7 @@ The count API allows to easily execute a query and get the number of matches for
 	var countResults = this._client.CountAll(q=>q.MatchAll());
 	Assert.True(countResults.Count > 0);
 
-The above will do a count query across all indices. (The result type here is not)
+The above will do a count query across all indices. (The result type here is not limited)
 
 If you want to limit the scope to just the default index for the type: