diff --git a/.scannerwork/report-task.txt b/.scannerwork/report-task.txt
index b761a5a..04bab9a 100644
--- a/.scannerwork/report-task.txt
+++ b/.scannerwork/report-task.txt
@@ -2,5 +2,5 @@ projectKey=cd_apache
 serverUrl=http://sonarqube.confdroid.com
 serverVersion=7.9.1.27448
 dashboardUrl=http://sonarqube.confdroid.com/dashboard?id=cd_apache
-ceTaskId=AXvPS-uq1C1yMMr1H4D-
-ceTaskUrl=http://sonarqube.confdroid.com/api/ce/task?id=AXvPS-uq1C1yMMr1H4D-
+ceTaskId=AXvPhmQ61C1yMMr1H4EI
+ceTaskUrl=http://sonarqube.confdroid.com/api/ce/task?id=AXvPhmQ61C1yMMr1H4EI
diff --git a/doc/file.README.html b/doc/file.README.html
index 5df2f3d..d7d53fa 100644
--- a/doc/file.README.html
+++ b/doc/file.README.html
@@ -76,13 +76,13 @@ configurations specific to the particular use case.</p>
 
 <h2 id="label-WARNING">WARNING</h2>
 
-<p><code>**__!!! Attention: Never use this puppet module on systems which have
+<p><strong><em>Attention: Never use this puppet module on systems which have
 been previously configured manually. It is impossible to predict how and
 what would have been configured, hence previous configurations outside the
 scope of this module may be overwritten! Automated configurations require a
 test environment to verify that the module suits the purpose intended by
 the user, as well as tune the parameters, before deploying into live
-production!!! __**</code></p>
+production</em></strong></p>
 
 <h2 id="label-Features">Features</h2>
 
diff --git a/doc/index.html b/doc/index.html
index 997a86a..4c7d71a 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -76,13 +76,13 @@ configurations specific to the particular use case.</p>
 
 <h2 id="label-WARNING">WARNING</h2>
 
-<p><code>**__!!! Attention: Never use this puppet module on systems which have
+<p><strong><em>Attention: Never use this puppet module on systems which have
 been previously configured manually. It is impossible to predict how and
 what would have been configured, hence previous configurations outside the
 scope of this module may be overwritten! Automated configurations require a
 test environment to verify that the module suits the purpose intended by
 the user, as well as tune the parameters, before deploying into live
-production!!! __**</code></p>
+production</em></strong></p>
 
 <h2 id="label-Features">Features</h2>