Update documentation, resolve #11

Author: vitalijr2

changelog.md

@@ -4,8 +4,9 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## Unreleased
+## 2.1.1 - 2022-08-14
 - Update dependencies
+- Update documentation
 
 ## 2.1.0 - 2022-08-01
 ### Changed

pom.xml

@@ -89,21 +89,18 @@
     <source-plugin.version>3.2.1</source-plugin.version>
     <site-plugin.version>3.12.1</site-plugin.version>
     <docs-maven-skin.version>2.2.7</docs-maven-skin.version>
-    <info-reports-plugin.version>3.4.0</info-reports-plugin.version>
+    <info-reports-plugin.version>3.4.1</info-reports-plugin.version>
     <sign-plugin.version>1.0.1</sign-plugin.version>
     <nexus-staging-plugin.version>1.6.13</nexus-staging-plugin.version>
     <!-- test -->
     <junit-jupiter.version>5.9.0</junit-jupiter.version>
-    <mockito.version>4.6.1</mockito.version>
+    <mockito.version>4.7.0</mockito.version>
     <hamcrest.version>2.2</hamcrest.version>
     <system-stubs.version>2.0.1</system-stubs.version>
     <commons-text.version>1.9</commons-text.version>
     <!-- dependencies -->
     <jetbrains-annotations.version>23.0.0</jetbrains-annotations.version>
     <slf4j.version>1.7.36</slf4j.version>
-    <!-- other -->
-    <package.registry.url>https://gitlab.com/bot-by/slf4j-aws-lambda/-/packages
-    </package.registry.url>
   </properties>
 
   <dependencies>

src/site/markdown/index.md

@@ -10,7 +10,10 @@ An [SLF4J][] Logger implementation for [AWS Lambda][lambda].
 Yet another SLF4J Simple, isn't it?
 
 No, it isn't. This implementation supports MDC to print out **AWS request ID** in start of every
-logging record. This implementation does not currently support Markers.
+logging record. This implementation supports Markers too.
+
+And last point: it resolves the [CRLF issue](https://twitter.com/ben11kehoe/status/1264597451010433025),
+you don't have to prepare logging messages and stacktraces to log them on CloudWatch Logs.
 
 The sample code, see the folder **[example][]** :