@@ -212,7 +212,7 @@ shifts the burden of fixing that deprecation to any contributor that
212212happens to submit a pull request shortly after a new vendor release is
213213made with that deprecation. To mitigate this, you can either use tighter
214214requirements, in the hope that dependencies will not introduce
215- deprecations in a patch version, or even commit theComposer lock file,
215+ deprecations in a patch version, or even commit the`` composer. lock`` file,
216216which would create another class of issues. Libraries will often use
217217``SYMFONY_DEPRECATIONS_HELPER=max[total]=999999 `` because of this. This
218218has the drawback of allowing contributions that introduce deprecations
@@ -227,7 +227,7 @@ be accounted for seperately, while deprecations triggered from a library
227227inside it will not (unless you reach 999999 of these), giving you
228228the best of both worlds.
229229
230- Direct andindirect deprecations
230+ Direct andIndirect Deprecations
231231................................
232232
233233When working on a project, you might be more interested in
@@ -258,7 +258,7 @@ Here is a summary that should help you pick the right configuration:
258258| | cannot afford to use one of the modes above.|
259259+------------------------+-----------------------------------------------------+
260260
261- Disabling theverbose output
261+ Disabling theVerbose Output
262262~~~~~~~~~~~~~~~~~~~~~~~~~~~~
263263
264264By default, the bridge will display a detailed output with the number of