docs: refactor in markdown

Author: awxiaoxian2020

pom.xml

@@ -419,6 +419,9 @@
             </configuration>
           </execution>
         </executions>
+        <configuration>
+          <escapeString>\</escapeString>
+        </configuration>
       </plugin>
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>

src/site/markdown/configuration.md

@@ -11,13 +11,11 @@ The Dynamic SQL elements should be familiar to anyone who has used JSTL or any s
 - trim (where, set)
 - foreach
 
-
-
 ### if
 
 The most common thing to do in dynamic SQL is conditionally include a part of a where clause. For example:
 
-```
+```xml
 <select id="findActiveBlogWithTitleLike"
      resultType="Blog">
   SELECT * FROM BLOG
@@ -69,8 +67,6 @@ Let’s use the example above, but now let’s search only on title if one is pr
 </select>
 ```
 
-
-
 ### trim, where, set
 
 The previous examples have been conveniently dancing around a notorious dynamic SQL challenge. Consider what would happen if we return to our "if" example, but this time we make "ACTIVE = 1" a dynamic condition as well.
@@ -160,7 +156,7 @@ Here, the *set* element will dynamically prepend the SET keyword, and also elimi
 
 Alternatively, you can achieve the same effect by using *trim* element:
 
-```
+```xml
 <trim prefix="SET" suffixOverrides=",">
   ...
 </trim>
@@ -195,7 +191,7 @@ This wraps up the discussion regarding the XML configuration file and XML mappin
 
 For using dynamic SQL in annotated mapper class, *script* element can be used. For example:
 
-```xml
+```java
     @Update({"<script>",
       "update Author",
       "  <set>",

src/site/markdown/dynamic-sql.md

@@ -20,7 +20,7 @@ Every MyBatis application centers around an instance of SqlSessionFactory. A Sql
 
 Building a SqlSessionFactory instance from an XML file is very simple. It is recommended that you use a classpath resource for this configuration, but you could use any InputStream instance, including one created from a literal file path or a file:// URL. MyBatis includes a utility class, called Resources, that contains a number of methods that make it simpler to load resources from the classpath and other locations.
 
-```
+```java
 String resource = "org/mybatis/example/mybatis-config.xml";
 InputStream inputStream = Resources.getResourceAsStream(resource);
 SqlSessionFactory sqlSessionFactory =
@@ -39,10 +39,10 @@ The configuration XML file contains settings for the core of the MyBatis system,
     <environment id="development">
       <transactionManager type="JDBC"/>
       <dataSource type="POOLED">
-        <property name="driver" value="${driver}"/>
-        <property name="url" value="${url}"/>
-        <property name="username" value="${username}"/>
-        <property name="password" value="${password}"/>
+        <property name="driver" value="\${driver}"/>
+        <property name="url" value="\${url}"/>
+        <property name="username" value="\${username}"/>
+        <property name="password" value="\${password}"/>
       </dataSource>
     </environment>
   </environments>
@@ -195,7 +195,7 @@ Using this pattern consistently throughout your code will ensure that all databa
 
 Mappers are interfaces that you create to bind to your mapped statements. Instances of the mapper interfaces are acquired from the SqlSession. As such, technically the broadest scope of any mapper instance is the same as the SqlSession from which they were requested. However, the best scope for mapper instances is method scope. That is, they should be requested within the method that they are used, and then be discarded. They do not need to be closed explicitly. While it's not a problem to keep them around throughout a request, similar to the SqlSession, you might find that managing too many resources at this level will quickly get out of hand. Keep it simple, keep Mappers in the method scope. The following example demonstrates this practice.
 
-```
+```java
 try (SqlSession session = sqlSessionFactory.openSession()) {
   BlogMapper mapper = session.getMapper(BlogMapper.class);
   // do work

src/site/markdown/getting-started.md

@@ -50,8 +50,6 @@ 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 
 
 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.
@@ -68,8 +66,6 @@ If you use the maven, you can download jar files by adding following settings on
 </dependency>
 ```
 
-
-
 #### Step 2: Configure Logback 
 
 Configuring Logback is simple. Suppose you want to enable the log for this mapper:
@@ -167,18 +163,18 @@ 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 
 
 ```xml
-pom.xml
+<!-- pom.xml -->
 <dependency>
   <groupId>org.apache.logging.log4j</groupId>
   <artifactId>log4j-core</artifactId>
   <version>2.x.x</version>
 </dependency>
-log4j2.xml
+```
+```xml
+<!-- log4j2.xml -->
 <?xml version="1.0" encoding="UTF-8"?>
 <Configuration xmlns="http://logging.apache.org/log4j/2.0/config">
 
@@ -198,18 +194,18 @@ log4j2.xml
 </Configuration>
 ```
 
-
-
 #### Configuration example for Log4j 
 
-```properties
-pom.xml
+```xml
+<!-- pom.xml -->
 <dependency>
   <groupId>log4j</groupId>
   <artifactId>log4j</artifactId>
   <version>1.2.17</version>
 </dependency>
-log4j.properties
+```
+```properties
+# log4j.properties
 log4j.rootLogger=ERROR, stdout
 
 log4j.logger.org.mybatis.example.BlogMapper=TRACE
@@ -219,12 +215,10 @@ log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
 log4j.appender.stdout.layout.ConversionPattern=%5p [%t] - %m%n
 ```
 
-
-
 #### Configuration example for JDK logging 
 
 ```properties
-logging.properties
+# logging.properties
 handlers=java.util.logging.ConsoleHandler
 .level=SEVERE