minor #1335 [Doc] Fixed a minor issue in a code example (javiereguiluz)

This PR was merged into the 6.2-dev branch.

Discussion
----------

[Doc] Fixed a minor issue in a code example

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no
| Doc update?   | yes
| BC breaks?    | no
| Deprecations? | no
| Fixed tickets | -
| License       | MIT

Commits
-------

0aaa0c6 [Doc] Fixed a minor issue in a code example

doc/messages.rst

@@ -479,11 +479,13 @@ Mailer will throw a ``Swift_RfcComplianceException``.
 If you add recipients automatically based on a data source that may contain
 invalid email addresses, you can prevent possible exceptions by validating the
 addresses using::
-        use Egulias\EmailValidator\EmailValidator;
-        use Egulias\EmailValidator\Validation\RFCValidation;
 
-        $validator = new EmailValidator();
-        $validator->isValid("example@example.com", new RFCValidation()); //true
+    use Egulias\EmailValidator\EmailValidator;
+    use Egulias\EmailValidator\Validation\RFCValidation;
+
+    $validator = new EmailValidator();
+    $validator->isValid("example@example.com", new RFCValidation()); //true
+
 and only adding addresses that validate. Another way would be to wrap your ``setTo()``, ``setCc()`` and
 ``setBcc()`` calls in a try-catch block and handle the
 ``Swift_RfcComplianceException`` in the catch block.