Update README.md

README.md

@@ -31,9 +31,11 @@ https://code.vereign.com/light/documentation/-/blob/master/Validation.md#normali
 - Put `sent.eml` and `received.eml` files into the `<test-case-dir>`
   - `sent.eml` contains MIME string logged by integrator application during the sending routine.
   - `received.eml` contains MIME string extracted manually from email client or logged by the integrator application.
+    
     For outlook.com - extract MIME string by logging it in the application itself.
     _Do not do export MIME via the web client using `Show message source` action.
     It breaks spacing of the quoted-printable parts and parsing/validation of such MIME might fail._
+    
     For mail.google.com - use `Show original` -> `Download original` actions in web client.
     _Don't copy contents provided by just `Show original` action because they miss base64 strings of the attachments_
 - Create three test suites to cover html, plain and htmltext (pseudoplain) normalisation. E.g:
@@ -82,9 +84,7 @@ https://code.vereign.com/light/documentation/-/blob/master/Validation.md#normali
   ```
 
 - Tests are using both JSDOM and custom Vereign [DOM parser](https://code.vereign.com/code/js-toolbox/gsdom).
-  Vereign DOM parser has been developed to support MIME normalisation in Google Add-on and is a must for testing.
-
-      Whenever you develop a new normalisation logic, ensure that Vereign DOM parser support functions that you are applying.
+  Vereign DOM parser has been developed to support MIME normalisation in Google Add-on and is a must for testing. Whenever you develop a new normalisation logic, ensure that Vereign DOM parser support functions that you are applying.
 
 ### Coverage