@@ -162,15 +162,15 @@ handler level or at the channel level instead of registering it globally
162162..tip ::
163163
164164 ..versionadded ::4.2
165- Processors can be autoconfigured since Symfony 4.2.
166-
167- Processors implementing :class: ` Symfony \\ Bridge \\ Monolog \\ Processor \\ ProcessorInterface `
168- can have their `` monolog.processor `` tag added for you by Symfony when autoconfiguration
169- is enabled. In this situation, this means creating a processor class might be all you
170- need do to to have it up and running. It also means enabling the
171- :class: `Symfony\\ Bridge\\ Monolog\\ Processor\\ TokenProcessor `or the
172- :class: `Symfony\\ Bridge\\ Monolog\\ Processor\\ WebProcessor `in your Flex-enabled app is a
173- one-liner :
165+ The autoconfiguration of Monolog processors was introduced in Symfony 4.2.
166+
167+ If you're using the :ref: ` default services.yaml configuration < service-container-services-load-example >`,
168+ processors implementing :class: ` Symfony\\ Bridge \\ Monolog \\ Processor \\ ProcessorInterface `
169+ are automatically registered as services and tagged with `` monolog. processor``,
170+ so you can use them without adding any configuration. The same applies to the
171+ built-in :class: `Symfony\\ Bridge\\ Monolog\\ Processor\\ TokenProcessor `and
172+ :class: `Symfony\\ Bridge\\ Monolog\\ Processor\\ WebProcessor `processors, which
173+ can be enabled as follows :
174174
175175 ..code-block ::yaml
176176