Fix documentation typo (#3453)

Author: stuartleeks

docs/client-concepts/low-level/getting-started.asciidoc

@@ -51,7 +51,7 @@ There are many other <<configuration-options,configuration options>> on `Connect
 * whether HTTP compression support should be enabled on the client
 
 [float]
-==== Connecton pools
+==== Connection pools
 
 `ConnectionConfiguration` is not restricted to being passed a single address for Elasticsearch. There are several different
 types of <<connection-pooling,Connection pool>> available, each with different characteristics that can be used to
@@ -99,10 +99,10 @@ var person = new Person
     LastName = "Laarman"
 };
 
-var indexResponse = lowlevelClient.Index<BytesResponse>("people", "person", "1", PostData.Serializable(person)); <1>
+var indexResponse = lowlevelClient.Index<BytesResponse>("people", "person", "1", PostData.Serializable(person)); <1>
 byte[] responseBytes = indexResponse.Body;
 
-var asyncIndexResponse = await lowlevelClient.IndexAsync<StringResponse>("people", "person", "1", PostData.Serializable(person)); <2>
+var asyncIndexResponse = await lowlevelClient.IndexAsync<StringResponse>("people", "person", "1", PostData.Serializable(person)); <2>
 string responseString = asyncIndexResponse.Body;
 ----
 <1> synchronous method that returns an `IIndexResponse`
@@ -238,8 +238,8 @@ is successful
 ----
 var searchResponse = lowlevelClient.Search<BytesResponse>("people", "person", PostData.Serializable(new { match_all = new {} }));
 
-var success = searchResponse.Success; <1>
-var successOrKnownError = searchResponse.SuccessOrKnownError; <2>
+var success = searchResponse.Success; <1>
+var successOrKnownError = searchResponse.SuccessOrKnownError; <2>
 var exception = searchResponse.OriginalException; <3>
 ----
 <1> Response is in the 200 range, or an expected response for the given request

src/Tests/Tests/ClientConcepts/LowLevel/GettingStarted.doc.cs

@@ -64,7 +64,7 @@ public void UsingConnectionSettings()
          * - whether HTTP compression support should be enabled on the client
 		 *
 		 * [float]
-		 * ==== Connecton pools
+		 * ==== Connection pools
 		 *
 		 * `ConnectionConfiguration` is not restricted to being passed a single address for Elasticsearch. There are several different
 		 * types of <<connection-pooling,Connection pool>> available, each with different characteristics that can be used to