A bunch of spelling fixes across site docs (#39)

Author: nutharsh

content/documentation/master/execution.md

@@ -330,7 +330,7 @@ to the caller.
 
 ## Asynchronous Execution
 
-graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompleteableFuture`` to results by calling
+graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompletableFuture`` to results by calling
 ``executeAsync()`` like this
 
 {{< highlight java "linenos=table" >}}
@@ -436,7 +436,7 @@ strategies for most cases.
 ## AsyncExecutionStrategy
 
 By default the "query" execution strategy is ``graphql.execution.AsyncExecutionStrategy`` which will dispatch
-each field as ``CompleteableFuture`` objects and not care which ones complete first.  This strategy allows for the most
+each field as ``CompletableFuture`` objects and not care which ones complete first.  This strategy allows for the most
 performant execution.
 
 The data fetchers invoked can themselves return ``CompletionStage`` values and this will create

content/documentation/v10/execution.md

@@ -316,7 +316,7 @@ to the caller.
 
 ## Asynchronous Execution
 
-graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompleteableFuture`` to results by calling
+graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompletableFuture`` to results by calling
 ``executeAsync()`` like this
 
 {{< highlight java "linenos=table" >}}
@@ -416,7 +416,7 @@ strategies for most cases.
 ## AsyncExecutionStrategy
 
 By default the "query" execution strategy is ``graphql.execution.AsyncExecutionStrategy`` which will dispatch
-each field as ``CompleteableFuture`` objects and not care which ones complete first.  This strategy allows for the most
+each field as ``CompletableFuture`` objects and not care which ones complete first.  This strategy allows for the most
 performant execution.
 
 The data fetchers invoked can themselves return ``CompletionStage`` values and this will create

content/documentation/v11/execution.md

@@ -316,7 +316,7 @@ to the caller.
 
 ## Asynchronous Execution
 
-graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompleteableFuture`` to results by calling
+graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompletableFuture`` to results by calling
 ``executeAsync()`` like this
 
 {{< highlight java "linenos=table" >}}
@@ -416,7 +416,7 @@ strategies for most cases.
 ## AsyncExecutionStrategy
 
 By default the "query" execution strategy is ``graphql.execution.AsyncExecutionStrategy`` which will dispatch
-each field as ``CompleteableFuture`` objects and not care which ones complete first.  This strategy allows for the most
+each field as ``CompletableFuture`` objects and not care which ones complete first.  This strategy allows for the most
 performant execution.
 
 The data fetchers invoked can themselves return ``CompletionStage`` values and this will create

content/documentation/v12/execution.md

@@ -331,7 +331,7 @@ to the caller.
 
 ## Asynchronous Execution
 
-graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompleteableFuture`` to results by calling
+graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompletableFuture`` to results by calling
 ``executeAsync()`` like this
 
 {{< highlight java "linenos=table" >}}
@@ -437,7 +437,7 @@ strategies for most cases.
 ## AsyncExecutionStrategy
 
 By default the "query" execution strategy is ``graphql.execution.AsyncExecutionStrategy`` which will dispatch
-each field as ``CompleteableFuture`` objects and not care which ones complete first.  This strategy allows for the most
+each field as ``CompletableFuture`` objects and not care which ones complete first.  This strategy allows for the most
 performant execution.
 
 The data fetchers invoked can themselves return ``CompletionStage`` values and this will create

content/documentation/v13/execution.md

@@ -331,7 +331,7 @@ to the caller.
 
 ## Asynchronous Execution
 
-graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompleteableFuture`` to results by calling
+graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompletableFuture`` to results by calling
 ``executeAsync()`` like this
 
 {{< highlight java "linenos=table" >}}
@@ -437,7 +437,7 @@ strategies for most cases.
 ## AsyncExecutionStrategy
 
 By default the "query" execution strategy is ``graphql.execution.AsyncExecutionStrategy`` which will dispatch
-each field as ``CompleteableFuture`` objects and not care which ones complete first.  This strategy allows for the most
+each field as ``CompletableFuture`` objects and not care which ones complete first.  This strategy allows for the most
 performant execution.
 
 The data fetchers invoked can themselves return ``CompletionStage`` values and this will create

content/documentation/v14/execution.md

@@ -331,7 +331,7 @@ to the caller.
 
 ## Asynchronous Execution
 
-graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompleteableFuture`` to results by calling
+graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompletableFuture`` to results by calling
 ``executeAsync()`` like this
 
 {{< highlight java "linenos=table" >}}
@@ -437,7 +437,7 @@ strategies for most cases.
 ## AsyncExecutionStrategy
 
 By default the "query" execution strategy is ``graphql.execution.AsyncExecutionStrategy`` which will dispatch
-each field as ``CompleteableFuture`` objects and not care which ones complete first.  This strategy allows for the most
+each field as ``CompletableFuture`` objects and not care which ones complete first.  This strategy allows for the most
 performant execution.
 
 The data fetchers invoked can themselves return ``CompletionStage`` values and this will create

content/documentation/v15/execution.md

@@ -330,7 +330,7 @@ to the caller.
 
 ## Asynchronous Execution
 
-graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompleteableFuture`` to results by calling
+graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompletableFuture`` to results by calling
 ``executeAsync()`` like this
 
 {{< highlight java "linenos=table" >}}
@@ -436,7 +436,7 @@ strategies for most cases.
 ## AsyncExecutionStrategy
 
 By default the "query" execution strategy is ``graphql.execution.AsyncExecutionStrategy`` which will dispatch
-each field as ``CompleteableFuture`` objects and not care which ones complete first.  This strategy allows for the most
+each field as ``CompletableFuture`` objects and not care which ones complete first.  This strategy allows for the most
 performant execution.
 
 The data fetchers invoked can themselves return ``CompletionStage`` values and this will create

content/documentation/v9/execution.md

@@ -316,7 +316,7 @@ to the caller.
 
 ## Asynchronous Execution
 
-graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompleteableFuture`` to results by calling
+graphql-java uses fully asynchronous execution techniques when it executes queries.  You can get the ``CompletableFuture`` to results by calling
 ``executeAsync()`` like this
 
 {{< highlight java "linenos=table" >}}
@@ -416,7 +416,7 @@ strategies for most cases.
 ## AsyncExecutionStrategy
 
 By default the "query" execution strategy is ``graphql.execution.AsyncExecutionStrategy`` which will dispatch
-each field as ``CompleteableFuture`` objects and not care which ones complete first.  This strategy allows for the most
+each field as ``CompletableFuture`` objects and not care which ones complete first.  This strategy allows for the most
 performant execution.
 
 The data fetchers invoked can themselves return ``CompletionStage`` values and this will create

themes/hugo-sustain/layouts/contact/list.html

@@ -11,7 +11,7 @@
                         <div class="block">
                             <div class="contact-content">
                                 {{ .Content }}
-                                <p>You can also send us a direct message bellow</p>
+                                <p>You can also send us a direct message below</p>
                             </div>
                             <div class="contact-form">
                                 <form id="contact-form" name="contact" method="POST" role="form" netlify>