[#7645] enumerate ordered list items implicitly

Author: xabbuh

contributing/code/reproducer.rst

@@ -36,16 +36,16 @@ If the bug is related to the Symfony Framework or if it's too complex to create
 a PHP script, it's better to reproduce the bug by forking the Symfony Standard
 edition. To do so:
 
-1. Go to https://github.com/symfony/symfony-standard and click on the **Fork**
+#. Go to https://github.com/symfony/symfony-standard and click on the **Fork**
    button to make a fork of that repository or go to your already forked copy.
-2. Clone the forked repository into your computer:
+#. Clone the forked repository into your computer:
    ``git clone git://github.com/YOUR-GITHUB-USERNAME/symfony-standard.git``
-3. Browse the project and create a new branch (e.g. ``issue_23567``,
+#. Browse the project and create a new branch (e.g. ``issue_23567``,
    ``reproduce_23657``, etc.)
-4. Now you must add the minimum amount of code to reproduce the bug. This is the
+#. Now you must add the minimum amount of code to reproduce the bug. This is the
    trickiest part and it's explained a bit more later.
-5. Add, commit and push all your changes.
-6. Add a comment in your original issue report to share the URL of your forked
+#. Add, commit and push all your changes.
+#. Add a comment in your original issue report to share the URL of your forked
    project (e.g. ``https://github.com/YOUR-GITHUB-USERNAME/symfony-standard/tree/issue_23567``)
    and, if necessary, explain the steps to reproduce (e.g. "browse this URL",
    "fill in this data in the form and submit it", etc.)
@@ -57,16 +57,16 @@ The key to create a bug reproducer is to solely focus on the feature that you
 suspect is failing. For example, imagine that you suspect that the bug is related
 to a route definition. Then, after forking the Symfony Standard Edition:
 
-1. Don't edit any of the default Symfony configuration options.
-2. Don't copy your original application code and don't use the same structure
+#. Don't edit any of the default Symfony configuration options.
+#. Don't copy your original application code and don't use the same structure
    of bundles, controllers, actions, etc. as in your original application.
-3. Open the default controller class of the AppBundle and add your routing
+#. Open the default controller class of the AppBundle and add your routing
    definition using annotations.
-4. Don't create or modify any other file.
-5. Execute the ``server:run`` command and browse the previously defined route
+#. Don't create or modify any other file.
+#. Execute the ``server:run`` command and browse the previously defined route
    to see if the bug appears or not.
-6. If you can see the bug, you're done and you can already share the code with us.
-7. If you can't see the bug, you must keep making small changes. For example, if
+#. If you can see the bug, you're done and you can already share the code with us.
+#. If you can't see the bug, you must keep making small changes. For example, if
    your original route was defined using XML, forget about the previous route
    annotation and define the route using XML instead. Or maybe your application
    uses bundle inheritance and that's where the real bug is. Then, forget about