bug #13240 [Validator] Fix lists in Sequentially doc (ogizanagi)

This PR was merged into the master branch.

Discussion
----------

[Validator] Fix lists in Sequentially doc

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/roadmap for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `master` for features of unreleased versions).

-->

It's not rendering properly on https://symfony.com/doc/master/reference/constraints/Sequentially.html

Commits
-------

7562f64 [Validator] Fix list in Sequentially doc

Author: wouterj

reference/constraints/Sequentially.rst

@@ -25,17 +25,19 @@ Basic Usage
 
 Suppose that you have a ``Place`` object with an ``$address`` property which
 must match the following requirements:
-- it's a non-blank string
-- of at least 10 chars long
-- with a specific format
-- and geolocalizable using an external service
+
+* it's a non-blank string
+* of at least 10 chars long
+* with a specific format
+* and geolocalizable using an external service
 
 In such situations, you may encounter three issues:
-- the ``Length`` or ``Regex`` constraints may fail hard with a :class:`Symfony\\Component\\Validator\\Exception\\UnexpectedValueException`
-exception if the actual value is not a string, as enforced by ``Type``.
-- you may end with multiple error messages for the same property
-- you may perform a useless and heavy external call to geolocalize the address,
-while the format isn't valid.
+
+* the ``Length`` or ``Regex`` constraints may fail hard with a :class:`Symfony\\Component\\Validator\\Exception\\UnexpectedValueException`
+  exception if the actual value is not a string, as enforced by ``Type``.
+* you may end with multiple error messages for the same property
+* you may perform a useless and heavy external call to geolocalize the address,
+  while the format isn't valid.
 
 You can validate each of these constraints sequentially to solve these issues: