Fix typo (#608)

[skip ci]

Author: nakamura-to

docs/config.rst

@@ -6,7 +6,7 @@ Configuration
    :depth: 3
 
 The configurable items must be returned from the methods of the implementation class of
-the ``org.seasar.doma.jdbc.Confing`` interface.
+the ``org.seasar.doma.jdbc.Config`` interface.
 
 Configurable items
 ==================

docs/entity.rst

@@ -251,7 +251,7 @@ In advance, define the database primary key as IDENTITY.
 
 .. warning::
 
-  All RDBMS does't support the IDENTITY function.
+  All RDBMS doesn't support the IDENTITY function.
 
 Id generation by SEQUENCE
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -273,7 +273,7 @@ correspond the properties within the ``@SequenceGenerator`` annotation.
 
 .. warning::
 
-  All RDBMS does't support the SEQUENCE.
+  All RDBMS doesn't support the SEQUENCE.
 
 Id generation by TABLE
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -327,7 +327,7 @@ Tenant Id
 ------------------------------
 
 The tenant id fields are represented with the ``@TenantId`` annotation.
-The column corresponding to the annotated field is included in the WHERE clause of UPDATE and DELETE stetements.
+The column corresponding to the annotated field is included in the WHERE clause of UPDATE and DELETE statements.
 
 .. code-block:: java
 

docs/query/insert.rst

@@ -140,7 +140,7 @@ Also, ``exclude`` element and ``include`` element and ``excludeNull`` element of
 Unique constraint violation
 ===========================
 
-``UniqueConstraintException`` is thrown regardless with or without using sql file if unique constraint violation is occured.
+``UniqueConstraintException`` is thrown regardless with or without using sql file if unique constraint violation is occurred.
 
 Query timeout
 ==================

docs/query/script.rst

@@ -172,7 +172,7 @@ Following script is valid for Oracle Database:
   insert into EMPLOYEE (ID, NAME) values (1, 'SMITH');
 
   /*
-   * procedure creatiton block
+   * procedure creation block
    */
   create or replace procedure proc
   ( cur out sys_refcursor,

docs/query/select.rst

@@ -23,7 +23,7 @@ There is no feature that auto generating search SQL.
 
   You need creating entity class **depending on search result**.
   For example, result set including column in EMPLOYEE table is accepted Employee class if the Employee class that correspond EMPLOYEE table is declared.
-  But, you need different class from the Employee entity class(For example EmmployeeDepartment class) for result set that is get by joining EMPLOYEE table and DEPARTMENT table.
+  But, you need different class from the Employee entity class(For example EmployeeDepartment class) for result set that is get by joining EMPLOYEE table and DEPARTMENT table.
 
 Query condition
 =================
@@ -85,7 +85,7 @@ You can specify multiple parameter.
 Mapping to IN clauses by using Iterable.
 -----------------------------------------
 
-You use subtype of ``java.lang.Iterable`` if excute searching by using IN clauses.
+You use subtype of ``java.lang.Iterable`` if execute searching by using IN clauses.
 
 .. code-block:: java
 
@@ -147,7 +147,7 @@ But if `Ensure of search result`_ is enabled, exception is thrown if search coun
 Stream search
 ==============
 
-You can use stream search if  handle all record at one try as ``java.util.stream.Stream`` rather than recieve as ``java.util.List``.
+You can use stream search if  handle all record at one try as ``java.util.stream.Stream`` rather than receiving as ``java.util.List``.
 
 There are two kind in stream search such as return the return value and pass ``Stream`` to ``java.util.Function``.
 

docs/sql.rst

@@ -292,7 +292,7 @@ The following example is the pair of a DAO method and an SQL template:
 
 .. code-block:: java
 
-  List<Employee> selectAll(BigDecimal salary, String orderyBy);
+  List<Employee> selectAll(BigDecimal salary, String orderBy);
 
 .. code-block:: sql
 

docs/transaction.rst

@@ -23,8 +23,8 @@ To use local transaction, these conditions are required:
 * Use the ``LocalTransactionManager`` above to control database access
 
 There are several ways to generate and get the ``LocalTransactionManager``,
-but the simplest way is to generate it in the constructor of ``Config`` implementaion class
-and make the ``Config`` implementaiton class singleton.
+but the simplest way is to generate it in the constructor of ``Config`` implementation class
+and make the ``Config`` implementation class singleton.
 
 Here is an example: