Spelling corrections

jeffgbutler · jeffgbutler · commit f86d11d68498 · 2019-07-08T10:48:46.000-04:00
diff --git a/src/site/markdown/docs/complexQueries.md b/src/site/markdown/docs/complexQueries.md
@@ -1,5 +1,5 @@
 # Complex Queries
-Enhancements in version 1.1.2 make it easier to code complex queries. The Select DSL is implemented as a set of related objects. As the select statement is built, intermediate objects of various types are returned from the various methods that implement the DSL. The select statement can be completed by calling the `build()` method many of the intermediate objects. Prior to version 1.1.2, it was necessary to call `build()` on the **last** intermediate object. This restriction has been removed and it is now possible to call `build()` on **any** intermedtae object. This, along with several other enhancements, has simplified the coding of complex queries.
+Enhancements in version 1.1.2 make it easier to code complex queries. The Select DSL is implemented as a set of related objects. As the select statement is built, intermediate objects of various types are returned from the various methods that implement the DSL. The select statement can be completed by calling the `build()` method many of the intermediate objects. Prior to version 1.1.2, it was necessary to call `build()` on the **last** intermediate object. This restriction has been removed and it is now possible to call `build()` on **any** intermediate object. This, along with several other enhancements, has simplified the coding of complex queries.
 
 For example, suppose you want to code a complex search on a Person table. The search parameters are id, first name, and last name. The rules are:
 
diff --git a/src/site/markdown/docs/conditions.md b/src/site/markdown/docs/conditions.md
@@ -84,7 +84,7 @@ For example, you could code a search like this:
 
 In this example, the three conditions will only be rendered if the values passed to them are not null. If all three values are null, then no where clause will be generated.
 
-Each of the conditions accepts a lamba expression that can be used to determine if the condition should render or not. The lambas will all be of standard JDK types (either `java.util.function.BooleanSupplier`, `java.util.function.Predicate`, or `java.util.function.BiPredicate` depending on the type of condition). The following table lists the optional conditions and shows how to use them: 
+Each of the conditions accepts a lambda expression that can be used to determine if the condition should render or not. The lambdas will all be of standard JDK types (either `java.util.function.BooleanSupplier`, `java.util.function.Predicate`, or `java.util.function.BiPredicate` depending on the type of condition). The following table lists the optional conditions and shows how to use them: 
 
 | Condition | Example | Rendering Rules |
 |-----------|---------|-----------------|
diff --git a/src/site/markdown/docs/spring.md b/src/site/markdown/docs/spring.md
@@ -13,7 +13,7 @@ The SQL statement objects are created in exactly the same way as for MyBatis - o
 ```
 
 ## Executing Select Statements
-The Spring Named Parameter JDBC template expects an SQL statement with parameter markers in the Spring format, and a set of matched parameters.  MyBatis Dynamic SQL will generate both.  The parameters returned from the generated SQL statement can be wrapped in a Spring `MapSqlParameterSource`.  Spring also expects you to provide a row mapper for creating the returned objects.  The followin code shows a complete example:
+The Spring Named Parameter JDBC template expects an SQL statement with parameter markers in the Spring format, and a set of matched parameters.  MyBatis Dynamic SQL will generate both.  The parameters returned from the generated SQL statement can be wrapped in a Spring `MapSqlParameterSource`.  Spring also expects you to provide a row mapper for creating the returned objects.  The following code shows a complete example:
 
 ```java
     NamedParameterJdbcTemplate template = getTemplate();
diff --git a/src/site/markdown/docs/update.md b/src/site/markdown/docs/update.md
@@ -36,7 +36,7 @@ For example:
             .set(animalName).equalToNull()
             .build()
             .render(RenderingStrategy.MYBATIS3);
-``` 
+```
 
 ## Annotated Mapper for Update Statements
 
@@ -52,7 +52,6 @@ import org.mybatis.dynamic.sql.util.SqlProviderAdapter;
     @UpdateProvider(type=SqlProviderAdapter.class, method="update")
     int update(UpdateStatementProvider updateStatement);
 ...
-
 ```
 
 ## XML Mapper for Update Statements
diff --git a/src/site/markdown/docs/whereClauses.md b/src/site/markdown/docs/whereClauses.md
@@ -142,4 +142,4 @@ In this mapper method there are three parameters.  So in this case it will be ne
 ```
 Notice that the string `whereClauseProvider` is used both as the parameter name in the mapper `@Param` annotation and the parameter name in the `render` method.
 
-The render method also has an override that accepts a TableAliasCalculator and a parameter name.
+The render method also has an override that accepts a TableAliasCalculator and a parameter name.
