Trivial changes made by the formatter [skip ci]

Author: harawata

src/site/markdown/logging.md

@@ -53,7 +53,7 @@ To see MyBatis logging statements you may enable logging on a package, a mapper
 
 Again, how you do this is dependent on the logging implementation in use. We'll show how to do it with SLF4J(Logback). Configuring the logging services is simply a matter of including one or more extra configuration files (e.g. `logback.xml`) and sometimes a new JAR file. The following example configuration will configure full logging services using SLF4J(Logback) as a provider. There are 2 steps.
 
-#### Step 1: Add the SLF4J + Logback JAR files 
+#### Step 1: Add the SLF4J + Logback JAR files
 
 Because we are using SLF4J(Logback), we will need to ensure its JAR file is available to our application. To use SLF4J(Logback), you need to add the JAR file to your application classpath.
 
@@ -69,7 +69,7 @@ If you use the maven, you can download jar files by adding following settings on
 </dependency>
 ```
 
-#### Step 2: Configure Logback 
+#### Step 2: Configure Logback
 
 Configuring Logback is simple. Suppose you want to enable the log for this mapper:
 
@@ -166,7 +166,7 @@ Yes, as you may have noticed, there is no difference in configuring logging for
 
 The remaining configuration in the `logback.xml` file is used to configure the appenders, which is beyond the scope of this document. However, you can find more information at the [Logback](https://logback.qos.ch/) website. Or, you could simply experiment with it to see what effects the different configuration options have.
 
-#### Configuration example for Log4j 2 
+#### Configuration example for Log4j 2
 
 ```xml
 <!-- pom.xml -->
@@ -198,7 +198,7 @@ The remaining configuration in the `logback.xml` file is used to configure the a
 </Configuration>
 ```
 
-#### Configuration example for Log4j 
+#### Configuration example for Log4j
 
 ```xml
 <!-- pom.xml -->
@@ -220,7 +220,7 @@ log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
 log4j.appender.stdout.layout.ConversionPattern=%5p [%t] - %m%n
 ```
 
-#### Configuration example for JDK logging 
+#### Configuration example for JDK logging
 
 ```properties
 # logging.properties

src/site/markdown/sqlmap-xml.md

@@ -220,7 +220,7 @@ As an irregular case, some databases allow INSERT, UPDATE or DELETE statement to
   insert into Author (username, password, email, bio)
   values (#{username}, #{password}, #{email}, #{bio})
   returning id, username, password, email, bio
-</select>        
+</select>
 ```
 
 ### sql
@@ -334,7 +334,7 @@ Despite all of these powerful options, most of the time you'll simply specify th
 #{lastName}
 ```
 
-#### String Substitution 
+#### String Substitution
 
 By default, using the `#{}` syntax will cause MyBatis to generate `PreparedStatement` properties and set the values safely against the `PreparedStatement` parameters (e.g. ?). While this is safer, faster and almost always preferred, sometimes you just want to directly inject an unmodified string into the SQL Statement. For example, for ORDER BY, you might use something like this:
 
@@ -648,7 +648,7 @@ In order to inject the results into the constructor, MyBatis needs to identify t
 </constructor>
 ```
 
-When you are dealing with a constructor with many parameters, maintaining the order of arg elements is error-prone.  
+When you are dealing with a constructor with many parameters, maintaining the order of arg elements is error-prone.
 Since 3.4.3, by specifying the name of each parameter, you can write arg elements in any order. To reference constructor parameters by their names, you can either add `@Param` annotation to them or compile the project with '-parameters' compiler option and enable `useActualParamName` (this option is enabled by default). The following example is valid for the same constructor even though the order of the second and the third parameters does not match with the declared order.
 
 ```xml