clean up some sphinx warnings

[dcaegen2.git] / docs / sections / services / mapper / troubleshooting.rst

diff --git a/docs/sections/services/mapper/troubleshooting.rst b/docs/sections/services/mapper/troubleshooting.rst
index 5d524e5..7ac4f9c 100644 (file)
--- a/docs/sections/services/mapper/troubleshooting.rst
+++ b/docs/sections/services/mapper/troubleshooting.rst
@@ -34,7 +34,7 @@ Error and warning logs contain also:
 **Do not rely on exact log messages or their presence, as they are often subject to change.**
 
 Deployment/Installation errors
---------------------
+------------------------------
 
 **Missing Default Config File in case of using local config instead of Consul**
 
@@ -45,8 +45,8 @@ Deployment/Installation errors
    |13:04:37.537 [main] ERROR errorLogger - Application stoped due to missing default Config file
    |13:04:37.538 [main] INFO  o.s.s.c.ThreadPoolTaskExecutor - Shutting down ExecutorService 'applicationTaskExecutor'
    |15:40:43.982 [main] WARN  debugLogger - All Smooks objects closed
-**These log messages are printed when the default configuration file "kv.json", was not present.**
 
+**These log messages are printed when the default configuration file "kv.json", was not present.**
 
 
 **Invalid Default Config File in case of using local config instead of Consul**
@@ -78,4 +78,4 @@ If Default Config File  is an invalid json file, we will get below exception
 
 **Invalid Smooks mapping file**
 
-If VES-Mapper blueprint or local config file contains invalid Smooks mapping file, then we will get below SAXException / JsonProcessingException / JsonSyntaxException / JsonParseException while processing the incoming notifications and the notification will be dropped without converting into required VES event. All such dropped notifications will be logged in error log file.
\ No newline at end of file
+If VES-Mapper blueprint or local config file contains invalid Smooks mapping file, then we will get below SAXException / JsonProcessingException / JsonSyntaxException / JsonParseException while processing the incoming notifications and the notification will be dropped without converting into required VES event. All such dropped notifications will be logged in error log file.