symfony
diff --git a/‎contributing/documentation/overview.rst
Lines changed: 0 additions & 5 deletions b/‎contributing/documentation/overview.rst
Lines changed: 0 additions & 5 deletions
diff --git a/‎workflow/state-machines.rst
Lines changed: 5 additions & 2 deletions b/‎workflow/state-machines.rst
Lines changed: 5 additions & 2 deletions
diff --git a/‎workflow/usage.rst
Lines changed: 15 additions & 8 deletions b/‎workflow/usage.rst
Lines changed: 15 additions & 8 deletions
@@ -284,10 +284,6 @@ If you don't use Docker, follow these steps to build the docs locally:
 
 The generated documentation is available in the ``_build/html`` directory.
 
-.. tip::
-
-    You can also use `Docker`_ that wraps all this for you!
-
 Frequently Asked Questions
 --------------------------
 
@@ -350,4 +346,3 @@ 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
@@ -216,8 +216,11 @@ 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::
+Symfony automatically creates 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 ``workflow.pull_request``
+or ``state_machine.pull_request`` respectively in your service definitions
+to access the proper service::
 
     // ...
     use Symfony\Component\Workflow\StateMachine;
 
@@ -43,7 +43,7 @@ like this:
                     audit_trail:
                         enabled: true
                     marking_store:
-                        type: 'multiple_state' # or 'single_state', 'method' ('method' was added in 4.3)
+                        type: 'multiple_state' # one of 'single_state', 'multiple_state', 'method'
                         arguments:
                             - 'currentPlace'
                     supports:
@@ -126,7 +126,7 @@ like this:
                         'enabled' => true
                     ],
                     'marking_store' => [
-                        'type' => 'multiple_state', // or 'single_state', 'method' ('method' was added in 4.3)
+                        'type' => 'multiple_state', // one of 'single_state', 'multiple_state', 'method'
                         'arguments' => ['currentPlace'],
                     ],
                     'supports' => ['App\Entity\BlogPost'],
@@ -170,6 +170,10 @@ As configured, the following property is used by the marking store::
     A single state marking store does not support a model being on multiple places
     at the same time.
 
+    versionadded:: 4.3
+
+        The ``method`` marking store type was introduced in Symfony 4.3.
+
 .. tip::
 
     The ``type`` (default value ``single_state``) and ``arguments`` (default
@@ -245,14 +249,17 @@ you can get the workflow by injecting the Workflow registry service::
     The :method:`Symfony\\Component\\Workflow\\Registry::all` method was
     introduced in Symfony 4.1.
 
-.. versionadded:: 4.3
+You can pass some context as the second argument of the ``apply()`` method.
+This can be useful when the subject not only needs to apply a transition,
 but for example you also want to log the context in which the switch happened.
 
-    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.
+This context is forwarded to the :method:`Symfony\\Component\\Workflow\\MarkingStore\\MarkingStoreInterface::setMarking`
+method of the marking store.
+
+.. versionadded:: 4.3
 
-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.
+    The ``$context`` argument of the :method:`Symfony\\Component\\Workflow\\Workflow::apply`
+    method was introduced in Symfony 4.3.
 
 .. tip::