Update documentation

Author: russcam

docs/aggregations/bucket/terms/terms-aggregation-usage.asciidoc

@@ -380,8 +380,8 @@ s => s
 .Aggregations(a => a
     .Terms("commits", st => st
         .Field(p => p.NumberOfCommits)
-        .Include(partition: 0, numberOfPartitions: 50)
-        .Size(2)
+        .Include(partition: 0, numberOfPartitions: 10)
+        .Size(5)
     )
 )
 ----
@@ -396,8 +396,8 @@ new SearchRequest<Project>
     Aggregations = new TermsAggregation("commits")
     {
         Field = Infer.Field<Project>(p => p.NumberOfCommits),
-        Include = new TermsInclude(0, 50),
-        Size = 2
+        Include = new TermsInclude(0, 10),
+        Size = 5
     }
 }
 ----
@@ -411,10 +411,10 @@ new SearchRequest<Project>
     "commits": {
       "terms": {
         "field": "numberOfCommits",
-        "size": 2,
+        "size": 5,
         "include": {
           "partition": 0,
-          "num_partitions": 50
+          "num_partitions": 10
         }
       }
     }

docs/aggregations/writing-aggregations.asciidoc

@@ -144,7 +144,6 @@ return s => s
     );
 ----
 <1> a list of aggregation functions to apply
-
 <2> Using LINQ's `Aggregate()` function to accumulate/apply all of the aggregation functions
 
 Combining multipe `AggregationDescriptor`'s is also possible using the bitwise `&` operator
@@ -212,6 +211,5 @@ var maxPerChild = childAggregation.Max("max_per_child");
 maxPerChild.Should().NotBeNull(); <2>
 ----
 <1> Do something with the average per child. Here we just assert it's not null
-
 <2> Do something with the max per child. Here we just assert it's not null
 

docs/client-concepts/certificates/working-with-certificates.asciidoc

@@ -17,25 +17,31 @@ please modify the original csharp file found at the link and submit the PR with
 
 === Server Certificates
 
-If you've enabled SSL on elasticsearch with x-pack or through a proxy in front of elasticsearch and the Certificate Authority (CA)
+If you've enabled SSL on Elasticsearch with x-pack or through a proxy in front of elasticsearch and the Certificate Authority (CA)
 That generated the certificate is trusted by the machine running the client code there should be nothing you'll have to do to to talk
 to over https with the client. If you are using your own CA which is not trusted .NET won't allow you to make https calls to that endpoint.
 
-.NET allows you to preempt this though through a custom validation through the the global static `ServicePointManager.ServerCertificateValidationCallback`.
+In .NET, you can preempt this though through a custom validation through the the global static `ServicePointManager.ServerCertificateValidationCallback`.
 Most examples you will find on the .NET will simply return `true` from this delegate and call it quits. This is not advisable as this will allow any HTTPS
 traffic in the current AppDomain and not run any validations. Imagine you deploy a web app that talks to Elasticsearch over HTTPS but also some third party
-SOAP/WSDL endpoint setting `ServicePointManager.ServerCertificateValidationCallback += (sender, cert, chain, errors) => true;` will skip validation of BOTH
-Elasticsearch and that external web service.
+SOAP/WSDL endpoint setting 
 
-.NET also allows you to set that callback per service endpoint and Elasticsearch.NET/NEST exposes this through connection settings.
-You can do your own validation in that handler or simply assign baked in handler that we ship with out of the box on the static
-class `CertificateValidations`.
+[source,csharp]
+----
+ServicePointManager.ServerCertificateValidationCallback += (sender, cert, chain, errors) => true; 
+----
+
+will skip validation for *both* Elasticsearch *and* that external web service.
 
-The two most basic ones are `AllowAll` and `DenyAll` which does accept or deny any ssl trafic to our nodes`:
+You can also set a callback per service endpoint with .NET, and Elasticsearch.NET/NEST exposes this through the
+connection settings; You can do your own validation in that handler or simply assign one of the baked in handlers 
+that we ship with out of the box, on the static class `CertificateValidations`.
 
-If your client application however has access to the public CA certificate locally Elasticsearch.NET/NEST ships with handy helpers that assert
-that the certificate that the server presented was one that came from our local CA certificate. If you use x-pack's `certgen` tool to
-[generate SSL certificates] https://www.elastic.co/guide/en/x-pack/current/ssl-tls.html)[] the generated node certificate does not include the CA in the
+The two most basic ones are `AllowAll` and `DenyAll`, which accept or deny any SSL traffic to our nodes, respectively
+
+If your client application however has access to the public CA certificate locally, Elasticsearch.NET/NEST ships with handy helpers that assert
+that the certificate that the server presented was one that came from our local CA certificate. If you use X-Pack's `certgen` tool to
+{xpack_current}/ssl-tls.html[generate SSL certificates], the generated node certificate does not include the CA in the
 certificate chain. This to cut back on SSL handshake size. In those case you can use `CertificateValidations.AuthorityIsRoot` and pass it your local copy
 of the CA public key to assert that the certificate the server presented was generated off that.
 
@@ -47,9 +53,9 @@ generate the servers key.
 
 === Client Certificates
 
-X-Pack also allows you to configure a [PKI realm] https://www.elastic.co/guide/en/x-pack/current/pki-realm.html)[] to enable user authentication
+X-Pack also allows you to configure a {xpack_current}/pki-realm.html[PKI realm] to enable user authentication
 through client certificates. The `certgen` tool included with X-Pack allows you to
-[generate client certificates as well] https://www.elastic.co/guide/en/x-pack/current/ssl-tls.html#CO13-4)[] and assign the distinguished name (DN) of the
+{xpack_current}/ssl-tls.html#CO13-4[generate client certificates as well] and assign the distinguished name (DN) of the
 certificate as a user with a certain role.
 
 certgen by default only generates a public certificate `.cer`) and a private key `.key`. To authenticate with client certificates you need to present both
@@ -63,15 +69,13 @@ You can set Client Certificates to use on all connections on `ConnectionSettings
 
 Or per request on `RequestConfiguration` which will take precedence over the ones defined on `ConnectionConfiguration`
 
-=== Object Initializer Syntax Example
-
 [source,csharp]
 ----
 new RootNodeInfoRequest
 {
     RequestConfiguration = new RequestConfiguration
     {
-        ClientCertificates = new X509Certificate2Collection { new X509Certificate2(this.BadCertificate) }
+        ClientCertificates = new X509Certificate2Collection { new X509Certificate2(this.Certificate) }
     }
 }
 ----
@@ -82,8 +86,7 @@ new RootNodeInfoRequest
 ----
 s => s
 .RequestConfiguration(r => r
-    .ClientCertificate(this.BadCertificate)
-
+    .ClientCertificate(this.Certificate)
 )
 ----
 

docs/client-concepts/high-level/inference/field-inference.asciidoc

@@ -523,13 +523,9 @@ class Precedence
 }
 ----
 <1> Even though this property has a NEST property mapping _and_ a `JsonProperty` attribute, We are going to provide a hard rename for it on ConnectionSettings later that should win.
-
 <2> This property has both a NEST attribute and a `JsonProperty`, NEST should win.
-
 <3> We should take the json property into account by itself
-
 <4> This property we are going to special case in our custom serializer to resolve to ask
-
 <5> We are going to register a DefaultFieldNameInferrer on ConnectionSettings that will uppercase all properties.
 
 Here we create a custom serializer that renames any property named `AskSerializer` to `ask`

docs/client-concepts/high-level/inference/indices-paths.asciidoc

@@ -79,9 +79,7 @@ ISearchRequest singleTypedRequest = new SearchDescriptor<Project>().Index(single
 var invalidSingleString = Index("name1, name2"); <3>
 ----
 <1> specifying a single index using a string
-
 <2> specifying a single index using a type
-
 <3> an **invalid** single index name
 
 ==== Specifying multiple indices
@@ -113,9 +111,7 @@ manyStringRequest = new SearchDescriptor<Project>().Type(new[] { "name1", "name2
 ((IUrlParameter)manyStringRequest.Type).GetString(this.Client.ConnectionSettings).Should().Be("name1,name2");
 ----
 <1> specifying multiple indices using strings
-
 <2> specifying multiple indices using types
-
 <3> The index names here come from the Connection Settings passed to `TestClient`. See the documentation on <<index-name-inference, Index Name Inference>> for more details.
 
 ==== Specifying All Indices

docs/client-concepts/low-level/connecting.asciidoc

@@ -91,9 +91,7 @@ var client = new ElasticLowLevelClient(config);
 var result = client.Search<SearchResponse<object>>(new { size = 12 });
 ----
 <1> Disable automatic proxy detection. When called, defaults to `true`.
-
 <2> Enable compressed request and responses from Elasticsearch (Note that nodes need to be configured to allow this. See the {ref_current}/modules-http.html[http module settings] for more info).
-
 <3> By default responses are deserialized directly from the response stream to the object you tell it to. For debugging purposes, it can be very useful to keep a copy of the raw response on the result object, which is what calling this method will do.
 
 `.ResponseBodyInBytes` will only have a value if the client configuration has `DisableDirectStreaming` set 
@@ -131,13 +129,9 @@ config = config
     .BasicAuthentication("username", "password");
 ----
 <1> Allows you to set querystring parameters that have to be added to every request. For instance, if you use a hosted elasticserch provider, and you need need to pass an `apiKey` parameter onto every request.
-
 <2> Sets proxy information on the connection.
-
 <3> [[request-timeout]] Sets the global maximum time a connection may take. Please note that this is the request timeout, the builtin .NET `WebRequest` has no way to set connection timeouts (see http://msdn.microsoft.com/en-us/library/system.net.httpwebrequest.timeout(v=vs.110).aspx[the MSDN documentation on `HttpWebRequest.Timeout` Property]).
-
 <4> As an alternative to the C/go like error checking on `response.IsValid`, you can instead tell the client to <<thrown-exceptions, throw exceptions>>.
-
 <5> forces all serialization to be indented and appends `pretty=true` to all the requests so that the responses are indented as well
 
 NOTE: Basic authentication credentials can alternatively be specified on the node URI directly:
@@ -359,8 +353,6 @@ public class MyJsonNetSerializer : JsonNetSerializer
 }
 ----
 <1> Call this constructor if you only need access to `JsonSerializerSettings` without local state (properties on MyJsonNetSerializer)
-
 <2> Call OverwriteDefaultSerializers if you need access to `JsonSerializerSettings` with local state
-
 <3> You can inject contract resolved converters by implementing the ContractConverters property. This can be much faster then registering them on `JsonSerializerSettings.Converters`
 

docs/query-dsl/joining/parent-id/parent-id-usage.asciidoc

@@ -27,7 +27,7 @@ q
 .ParentId(p => p
     .Name("named_query")
     .Type<Developer>()
-    .Id(Project.Projects.First().Name)
+    .Id(Project.First.Name)
 )
 ----
 
@@ -39,7 +39,7 @@ new ParentIdQuery
 {
     Name = "named_query",
     Type = Infer.Type<Developer>(),
-    Id = Project.Projects.First().Name
+    Id = Project.First.Name
 }
 ----
 

docs/search/request/search-after-usage.asciidoc

@@ -25,8 +25,8 @@ s => s
     .Descending(p => p.Name)
 )
 .SearchAfter(
-    Project.Projects.FirstOrDefault().NumberOfCommits,
-    Project.Projects.FirstOrDefault().Name
+    Project.First.NumberOfCommits,
+    Project.First.Name
 )
 ----
 
@@ -43,8 +43,8 @@ new SearchRequest<Project>
     },
     SearchAfter = new List<object>
     {
-        Project.Projects.FirstOrDefault().NumberOfCommits,
-        Project.Projects.FirstOrDefault().Name,
+        Project.First.NumberOfCommits,
+        Project.First.Name,
     }
 }
 ----
@@ -67,7 +67,7 @@ new SearchRequest<Project>
   ],
   "search_after": [
     775,
-    "Dickinson - Beier"
+    "Lesch Group"
   ]
 }
 ----

docs/search/request/suggest-usage.asciidoc

@@ -42,7 +42,7 @@ s => s
     .Completion("my-completion-suggest", c => c
         .Contexts(ctxs => ctxs
             .Context("color",
-                ctx => ctx.Context(Project.Projects.First().Suggest.Contexts.Values.SelectMany(v => v).First())
+                ctx => ctx.Context(Project.First.Suggest.Contexts.Values.SelectMany(v => v).First())
             )
         )
         .Fuzzy(f => f
@@ -110,7 +110,7 @@ new SearchRequest<Project>
             {
                 Contexts = new Dictionary<string, IList<ISuggestContextQuery>>
                 {
-                    { "color", new List<ISuggestContextQuery> { new SuggestContextQuery { Context = Project.Projects.First().Suggest.Contexts.Values.SelectMany(v => v).First() } } }
+                    { "color", new List<ISuggestContextQuery> { new SuggestContextQuery { Context = Project.First.Suggest.Contexts.Values.SelectMany(v => v).First() } } }
                 },
                 Fuzzy = new FuzzySuggester
                 {
@@ -247,6 +247,6 @@ option.Contexts.Should().NotBeNull().And.NotBeEmpty();
 option.Contexts.Should().ContainKey("color");
 var colorContexts = option.Contexts["color"];
 colorContexts.Should().NotBeNull().And.HaveCount(1);
-colorContexts.First().Category.Should().Be((Project.Projects.First().Suggest.Contexts.Values.SelectMany(v => v).First()));
+colorContexts.First().Category.Should().Be((Project.First.Suggest.Contexts.Values.SelectMany(v => v).First()));
 ----