linting

Signed-off-by: alexmerlin <alex.merlin.1985@gmail.com>

Author: alexmerlin

docs/book/v4/extra/cookie.md

@@ -2,11 +2,11 @@
 
 Looking at `dot-errorhandler`'s config file, the array found at `CookieProvider::class` allows you to configure the behaviour of this provider:
 
-* **enabled**: enabled/disable this provider
-* **processor**: an array configuring the data processor to be used by the **CookieProvider**:
-  * **class**: data processor class implementing `Dot\ErrorHandler\Extra\Processor\ProcessorInterface`
-  * **replacementStrategy**: whether to replace specific cookie values completely or partially
-  * **sensitiveParameters**: an array of cookies names that may contain sensitive information so their value should be masked partially/completely
+- **enabled**: enabled/disable this provider
+- **processor**: an array configuring the data processor to be used by the **CookieProvider**:
+    - **class**: data processor class implementing `Dot\ErrorHandler\Extra\Processor\ProcessorInterface`
+    - **replacementStrategy**: whether to replace specific cookie values completely or partially
+    - **sensitiveParameters**: an array of cookies names that may contain sensitive information so their value should be masked partially/completely
 
 ## Configure provider
 

docs/book/v4/log-files.md

@@ -9,13 +9,13 @@ By default, log activities are formatted with JSON, so each row should be a deco
 
 Each row in a log file should contain the following values:
 
-* **timestamp**: string representation of the date and time when the error occurred
-* **priority**: numeric representation of the error level
-* **priorityName**: string representation of the error level
-* **message**: error message describing the error
-* **extra**: an array of extra information that may help the developer debug the error:
-  * **file**: the file in which the error occurred
-  * **line**: the line from **file** where the error occurred
+- **timestamp**: string representation of the date and time when the error occurred
+- **priority**: numeric representation of the error level
+- **priorityName**: string representation of the error level
+- **message**: error message describing the error
+- **extra**: an array of extra information that may help the developer debug the error:
+    - **file**: the file in which the error occurred
+    - **line**: the line from **file** where the error occurred
 
 By leveraging `dot-errorhandler`'s extra providers, you can also log additional request parameters.
 Learn more about what additional parameters are available on the [extra data](extra/introduction.md) page.