Apply suggestion to doc/user/project/pipelines/settings.mdtip-for-ansi-colors

1 files changed, 12 insertions, 5 deletions

diff --git a/doc/user/project/pipelines/settings.md b/doc/user/project/pipelines/settings.md
index 72f0e5b9050..9fd78389bae 100644
--- a/doc/user/project/pipelines/settings.md
+++ b/doc/user/project/pipelines/settings.md
@@ -89,11 +89,18 @@ in the jobs table.
 A few examples of known coverage tools for a variety of languages can be found
 in the pipelines settings page.
 
-Note that some test coverage tools output with ANSI color codes which won't be
-parsed correctly by the regular expression and will cause coverage parsing to
-not work. If your coverage tool doesn't provide an option to disable color
-codes in the output you can pipe the output of the coverage tool through a 
-small one line script that will strip the color codes off. For example:
+### Removing color codes
+
+Some test coverage tools output with ANSI color codes that won't be
+parsed correctly by the regular expression and will cause coverage 
+parsing to fail. 
+
+If your coverage tool doesn't provide an option to disable color
+codes in the output, you can pipe the output of the coverage tool through a 
+small one line script that will strip the color codes off.
+
+For example:
+
 ```bash
 lein cloverage | perl -pe 's/\e\[?.*?[\@-~]//g'
 ```