Review

Author: noniagriconomie

contributing/documentation/overview.rst

@@ -270,7 +270,9 @@ purposes following these steps:
 
 The generated documentation is available in the ``_build/html`` directory.
 
-You can also use Docker that wraps all this for you, please visit https://github.com/symfony/symfony-docs#docker.
+.. tip::
+
+    You can also use `Docker`_ that wraps all this for you!
 
 Frequently Asked Questions
 --------------------------
@@ -334,3 +336,4 @@ definitely don't want you to waste your time!
 .. _`pip installation`: https://pip.pypa.io/en/stable/installing/
 .. _`Sphinx`: http://sphinx-doc.org/
 .. _`Sphinx Extensions for PHP and Symfony`: https://github.com/fabpot/sphinx-php
+.. _`Docker`: https://github.com/symfony/symfony-docs#docker

workflow.rst

@@ -8,8 +8,8 @@ best kept away from your models and should be defined in configuration.
 
 A **definition** of a workflow consist of places and actions to get from one
 place to another. The actions are called **transitions**. A workflow does also
-need to know each object's position in the workflow. This is the goal of the
-**marking store** that writes to a property of the object, or somewhere else, the current **place(s)**
+need to know each position an object can be in the workflow. This is the goal of the
+**marking store** that reads from and writes to a property of the object, or somewhere else, the current **place(s)**
 to remember.
 
 .. note::

workflow/state-machines.rst

@@ -217,9 +217,7 @@ you can get this state machine by injecting the Workflow registry service::
     }
 
 Symfony also creates automatically for you a service for each workflow (:class:`Symfony\\Component\\Workflow\\Workflow`) or state machine (:class:`Symfony\\Component\\Workflow\\StateMachine`) you have defined in your configuration.
-This means that you can use respectively ``workflow.pull_request`` or ``state_machine.pull_request`` in your service definition to have directly the proper service.
-
-::
+This means that you can use respectively ``workflow.pull_request`` or ``state_machine.pull_request`` in your service definition to have directly the proper service::
 
     // ...
     use Symfony\Component\Workflow\StateMachine;
@@ -236,7 +234,7 @@ This means that you can use respectively ``workflow.pull_request`` or ``state_ma
         public function someMethod($subject)
         {
             $this->stateMachine->apply($subject, 'wait_for_review', [
-                'log_comment' => 'My logging comment for the wait for review transition.'
+                'log_comment' => 'My logging comment for the wait for review transition.',
             ]);
             // ...
         }

workflow/usage.rst

@@ -225,7 +225,7 @@ you can get the workflow by injecting the Workflow registry service::
             // to the whole workflow process
             try {
                 $workflow->apply($post, 'publish', [
-                    'log_comment' => 'My logging comment for the publish transition.'
+                    'log_comment' => 'My logging comment for the publish transition.',
                 ]);
             } catch (TransitionException $exception) {
                 // ... if the transition is not allowed
@@ -237,33 +237,34 @@ you can get the workflow by injecting the Workflow registry service::
     }
 
 .. versionadded:: 4.1
+
     The :class:`Symfony\\Component\\Workflow\\Exception\\TransitionException`
     class was introduced in Symfony 4.1.
 
 .. versionadded:: 4.1
+
     The :method:`Symfony\\Component\\Workflow\\Registry::all` method was
     introduced in Symfony 4.1.
 
 .. versionadded:: 4.3
+
     The :method:`Symfony\\Component\\Workflow\\Workflow::apply` has now a new parameter ``$context``
     that is passed to the :class:`Symfony\\Component\\Workflow\\MarkingStore\\MarkingStoreInterface`
     :method:`Symfony\\Component\\Workflow\\MarkingStore\\MarkingStoreInterface::setMarking` method.
 
-An example of usage with the ``$context`` parameter can be when you need, in addition of marking your object
-in its new place, to contextualize this change.
+An example of usage with the ``$context`` parameter can be when you need,
+in addition of marking your object in its new place, to contextualize this change.
 
 .. tip::
 
     Configure the ``type`` as ``method`` of the ``marking_store`` option to use this feature
-    without implementing your own marking store (``method`` was added in 4.3).
+    without implementing your own marking store.
 
 You can also use this ``$context`` in your own marking store implementation.
 A simple implementation example is when you want to store the place as integer instead of string in your object.
 
 Lets say your object has a status property, stored as an integer in your storage, and you want to log an optional
-comment any time the status changes.
-
-.. code-block:: php
+comment any time the status changes::
 
     // your own implementation class, to define in the configuration "marking_store"
 
@@ -299,7 +300,7 @@ comment any time the status changes.
     }
 
     // the StatusLog class can have a createdAt, a username,
-    // the new status, and finally your optional comment retrived from the workflow context.
+    // the new status, and finally your optional comment retrieved from the workflow context.
 
 Using Events
 ------------