8000 minor #8230 Some typos (ThomasLandauer) · symfony/symfony-docs@1b6aaab · GitHub
[go: up one dir, main page]

Skip to content

Commit 1b6aaab

Browse files
committed
minor #8230 Some typos (ThomasLandauer)
This PR was squashed before being merged into the 3.3 branch (closes #8230). Discussion ---------- Some typos Commits ------- 3ba8715 Some typos
2 parents 2eedbc6 + 3ba8715 commit 1b6aaab

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

service_container/3.3-di-changes.rst

Lines changed: 3 additions & 3 deletions
5611
Original file line numberDiff line numberDiff line change
@@ -360,7 +360,7 @@ The third big change is that, in a new Symfony 3.3 project, your controllers are
360360
But, you might not even notice this. First, your controllers *can* still extend
361361
the same base ``Controller`` class or a new :ref:`AbstractController <controller-abstract-versus-controller>`.
362362
This means you have access to all of the same shortcuts as before. Additionally,
363-
the ``@Route`` annotation and ``_controller`` syntax (e.g.``AppBundle:Default:homepage``)
363+
the ``@Route`` annotation and ``_controller`` syntax (e.g. ``AppBundle:Default:homepage``)
364364
used in routing will automatically use your controller as a service (as long as its
365365
service id matches its class name, which it *does* in this case). See :doc:`/controller/service`
366366
for more details. You can even create :ref:`invokable controllers <controller-service-invoke>`
@@ -433,7 +433,7 @@ In this case, you've created a class that implements ``EventSubscriberInterface`
433433
and registered it as a service. This is more than enough for the container to know
434434
that you want this to be used as an event subscriber: more configuration is not needed.
435435
And the tags system is its own, Symfony-specific mechanism. And of course, you can
436-
always default ``autoconfigure`` to false in ``services.yml``, or disable it for a specific
436+
always set ``autoconfigure`` to ``false`` in ``services.yml``, or disable it for a specific
437437
service.
438438

439439
Does this mean tags are dead? Does this work for all tags?
@@ -449,7 +449,7 @@ see what it autoconfigures.
449449

450450
Many autoconfigured tags have an optional priority. If you need to specify a priority
451451
(or any other optional tag attribute), no problem! Just :ref:`manually configure your service <services-manually-wire-args>`
452-
and add the tag. Your tag will take precedent over the one added by auto-configuration.
452+
and add the tag. Your tag will take precedence over the one added by auto-configuration.
453453

454454
What about Performance
455455
----------------------

0 commit comments

Comments
 (0)
0