Correct spellings

Author: russcam

src/Tests/ClientConcepts/ConnectionPooling/BuildingBlocks/DateTimeProviders.Doc.cs

@@ -29,8 +29,8 @@ [U] public void DefaultNowBehaviour()
 		[U] public void DeadTimeoutCalculation()
 		{
 			var dateTimeProvider = DateTimeProvider.Default;
-			/**
-			* The default timeout calculation is: `min(timeout * 2 ^ (attempts * 0.5 -1), maxTimeout)`, where the
+			/**  
+			* The default timeout calculation is: `min(timeout * 2 ^ (attempts * 0.5 -1), maxTimeout)`, where the 
 			* default values for `timeout` and `maxTimeout` are
 			*/
 			var timeout = TimeSpan.FromMinutes(1);
@@ -40,8 +40,8 @@ [U] public void DeadTimeoutCalculation()
 			* Plotting these defaults looks as followed:
 			*
 			*[[timeout]]
-			*.Default formula, y-axis time in minutes, x-axis number of attempts to revive
-			*image::timeoutplot.png[dead timeout]
+			*.Default formula, x-axis number of attempts to revive, y-axis time in minutes
+			*image::timeoutplot.png[dead timeout]	
 			*
 			* The goal here is that whenever a node is resurrected and is found to still be offline, we send it
 			* _back to the doghouse_ for an ever increasingly long period, until we hit a bounded maximum.
@@ -52,7 +52,7 @@ [U] public void DeadTimeoutCalculation()
 
 			foreach (var increasedTimeout in timeouts.Take(10))
 				increasedTimeout.Should().BeWithin(maxTimeout);
-
+			
 		}
 
 	}

src/Tests/ClientConcepts/ConnectionPooling/Pinging/FirstUsage.doc.cs

@@ -77,7 +77,7 @@ await audit.TraceCalls(
 					} }
 				},
 				/** The 2nd call does a ping on 9201 because its used for the first time.
-				* It fails and so we ping 9202 which also fails. We then ping 9203 becuase
+				* It fails and so we ping 9202 which also fails. We then ping 9203 because
 				* we haven't used it before and it succeeds */
 				new ClientCall {
 					{ PingFailure, 9201},

src/Tests/ClientConcepts/ConnectionPooling/RoundRobin/RoundRobin.doc.cs

@@ -19,7 +19,7 @@ public class RoundRobin
 		/** === GetNext
 		* `GetNext` is implemented in a lock free thread safe fashion, meaning each callee gets returned its own cursor to advance
 		* over the internal list of nodes. This to guarantee each request that needs to fall over tries all the nodes without
-		* suffering from noisy neighboors advancing a global cursor.
+		* suffering from noisy neighbours advancing a global cursor.
 		*/
 		protected int NumberOfNodes = 10;
 

src/Tests/ClientConcepts/ConnectionPooling/RoundRobin/SkipDeadNodes.doc.cs

@@ -19,7 +19,7 @@ public class SkippingDeadNodes
 		* === GetNext
 		* GetNext is implemented in a lock free thread safe fashion, meaning each callee gets returned its own cursor to advance
 		* over the internal list of nodes. This to guarantee each request that needs to fall over tries all the nodes without
-		* suffering from noisy neighboors advancing a global cursor.
+		* suffering from noisy neighbours advancing a global cursor.
 		*/
 		protected int NumberOfNodes = 3;
 

src/Tests/ClientConcepts/ConnectionPooling/Sniffing/OnConnectionFailure.doc.cs

@@ -31,7 +31,7 @@ [U] public async Task DoesASniffAfterConnectionFailure()
 				.ClientCalls(r => r.SucceedAlways())
 				.ClientCalls(r => r.OnPort(9201).Fails(Once))
 				/**
-				* When the call fails on 9201 the sniff succeeds and returns a new cluster of healty nodes
+				* When the call fails on 9201 the sniff succeeds and returns a new cluster of healthy nodes
 				* this cluster only has 3 nodes and the known masters are 9200 and 9202 but a search on 9201
 				* still fails once
 				*/

src/Tests/ClientConcepts/ConnectionPooling/Sniffing/OnStaleClusterState.doc.cs

@@ -13,7 +13,7 @@ public class OnStaleClusterState
 		/**== Sniffing periodically
 		*
 		* Connection pools that return true for `SupportsReseeding` can be configured to sniff periodically.
-		* In addition to sniffing on startup and sniffing on failures, sniffing periodically can benefit scenerio's where
+		* In addition to sniffing on startup and sniffing on failures, sniffing periodically can benefit scenarios where
 		* clusters are often scaled horizontally during peak hours. An application might have a healthy view of a subset of the nodes
 		* but without sniffing periodically it will never find the nodes that have been added to help out with load
 		*/

src/Tests/ClientConcepts/ConnectionPooling/Sticky/SkipDeadNodes.doc.cs

@@ -46,7 +46,7 @@ public void EachViewSeesNextButSkipsTheDeadNode()
 				node = pool.CreateView().First();
 				node.Uri.Port.Should().Be(9201);
 			}
-			/** After we marke the first node alive again we expect it to be hit again*/
+			/** After we mark the first node alive again we expect it to be hit again*/
 			seeds.First().MarkAlive();
 			for (var i = 0; i < 20; i++)
 			{

src/Tests/ClientConcepts/HighLevel/Inference/DocumentPaths.doc.cs

@@ -10,8 +10,8 @@ public class DocumentPaths
 		/**== Document Paths
 		 *
 		 * Many API's in Elasticsearch describe a path to a document. In NEST, besides generating a constructor that takes
-		 * and Index, Type and Id seperately, we also generate a constructor taking a `DocumentPath` that allows you to describe the path
-		 * to your document more succintly
+		 * and Index, Type and Id separately, we also generate a constructor taking a `DocumentPath` that allows you to describe the path
+		 * to your document more succinctly
 		 */
 
 		/** === Creating new instances */

src/Tests/ClientConcepts/HighLevel/Inference/FeaturesInference.doc.cs

@@ -29,7 +29,7 @@ [U] public void Serializes()
 		public void ImplicitConversion()
 		{
 			/**
-			* Here we new an GET index elasticsearch request whichs takes Indices and Features.
+			* Here we new an GET index elasticsearch request which takes Indices and Features.
 			* Notice how we can use the Feature enum directly.
 			*/
 			var request = new GetIndexRequest(All, Feature.Settings);

src/Tests/ClientConcepts/HighLevel/Inference/FieldInference.doc.cs

@@ -20,9 +20,9 @@ namespace Tests.ClientConcepts.HighLevel.Inference
 	public class FieldInference
 	{
 		/**== Field Inference
-		 * 
+		 *
 		 * Several places in the Elasticsearch API expect the path to a field from your original source document as a string.
-		 * NEST allows you to use C# expressions to strongly type these field path strings. 
+		 * NEST allows you to use C# expressions to strongly type these field path strings.
 		 *
 		 * These expressions are assigned to a type called `Field` and there are several ways to create an instance of one
 		 */
@@ -133,7 +133,7 @@ public void UsingStaticPropertyField()
 			/** You can specify boosts in the field using a string */
 			fieldString = "name^2.1";
 			fieldString.Boost.Should().Be(2.1);
-			
+
 			/** As well as using `Nest.Infer.Field` */
 			fieldExpression = Field<Project>(p => p.Name, 2.1);
 			Expect("name^2.1")
@@ -229,7 +229,7 @@ public void ComplexFieldNameExpressions()
 				Field<Project>(p => p.Metadata[variable].Created.Suffix(suffix)));
 		}
 
-		/** 
+		/**
 		* Suffixes can also be appended to expressions using `.AppendSuffix()`. This is useful in cases where you want to apply the same suffix
 		* to a list of fields.
 		*/
@@ -246,7 +246,7 @@ public void AppendingSuffixToExpressions()
 			};
 
 			/** and we want to append the suffix "raw" to each */
-			var fieldExpressions = 
+			var fieldExpressions =
 				expressions.Select<Expression<Func<Project, object>>, Field>(e => e.AppendSuffix("raw")).ToList();
 
 			Expect("name.raw").WhenSerializing(fieldExpressions[0]);
@@ -256,7 +256,7 @@ public void AppendingSuffixToExpressions()
 		}
 
 		/**=== Attribute based naming
-		* 
+		*
 		* Using NEST's property attributes you can specify a new name for the properties
 		*/
 		public class BuiltIn
@@ -270,7 +270,7 @@ public void BuiltInAnnotiatons()
 			Expect("naam").WhenSerializing(Field<BuiltIn>(p => p.Name));
 		}
 
-		/** 
+		/**
 		* Starting with NEST 2.x, we also ask the serializer if it can resolve a property to a name.
 		* Here we ask the default `JsonNetSerializer` to resolve a property name and it takes
 		* the `JsonPropertyAttribute` into account
@@ -286,7 +286,7 @@ public void SerializerSpecificAnnotations()
 			Expect("nameInJson").WhenSerializing(Field<SerializerSpecific>(p => p.Name));
 		}
 
-		/** 
+		/**
 		* If both a NEST property attribute and a serializer specific attribute are present on a property,
 		* **NEST attributes take precedence**
 		*/
@@ -330,7 +330,7 @@ public void ExpressionsAreCachedButSeeDifferentTypes()
 			var fieldNameOnB = client.Infer.Field(Field<B>(p => p.C.Name));
 
 			/**
-			* Here we have to similary shaped expressions on coming from A and on from B
+			* Here we have two similarly shaped expressions, one coming from A and one from B
 			* that will resolve to the same field name, as expected
 			*/
 
@@ -355,7 +355,7 @@ public void ExpressionsAreCachedButSeeDifferentTypes()
 			fieldNameOnA.Should().Be("d.name");
 			fieldNameOnB.Should().Be("c.name");
 
-			/** however we didn't break inferrence on the first client instance using its separate connection settings */
+			/** however we didn't break inference on the first client instance using its separate connection settings */
 			fieldNameOnA = client.Infer.Field(Field<A>(p => p.C.Name));
 			fieldNameOnB = client.Infer.Field(Field<B>(p => p.C.Name));
 
@@ -369,7 +369,7 @@ public void ExpressionsAreCachedButSeeDifferentTypes()
 		*
 		* . A hard rename of the property on connection settings using `.Rename()`
 		* . A NEST property mapping
-		* . Ask the serializer if the property has a verbatim value e.g it has an explicit JsonPropery attribute.
+		* . Ask the serializer if the property has a verbatim value e.g it has an explicit JsonProperty attribute.
 		* . Pass the MemberInfo's Name to the DefaultFieldNameInferrer which by default camelCases
 		*
 		* The following example class will demonstrate this precedence
@@ -393,7 +393,7 @@ class Precedence
 			public string DefaultFieldNameInferrer { get; set; } //<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`
 		*/
 		class CustomSerializer : JsonNetSerializer