Skip to content

[Reference][DI Tags] Fix typos and formatting #3154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 5, 2013
Merged

[Reference][DI Tags] Fix typos and formatting #3154

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions reference/dic_tags.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ In order to add a new worker, first create a class::

}

And then add register it as a tagged service:
And then register it as a tagged service:

.. configuration-block::

Expand Down Expand Up @@ -299,7 +299,7 @@ the interface directly::
}

In order for Symfony to know about your form extension and use it, give it
the `form.type_extension` tag:
the ``form.type_extension`` tag:

.. configuration-block::

Expand Down Expand Up @@ -370,7 +370,7 @@ service class::

}

Then register this class and tag it with ``kernel.cache:clearer``:
Then register this class and tag it with ``kernel.cache_clearer``:

.. configuration-block::

Expand Down Expand Up @@ -431,7 +431,7 @@ The ``isOptional`` method should return true if it's possible to use the
application without calling this cache warmer. In Symfony 2.0, optional warmers
are always executed anyways, so this function has no real effect.

To register your warmer with Symfony, give it the kernel.cache_warmer tag:
To register your warmer with Symfony, give it the ``kernel.cache_warmer`` tag:

.. configuration-block::

Expand Down Expand Up @@ -486,7 +486,7 @@ core Symfony listeners and their priorities.

All listeners listed here may not be listening depending on your environment,
settings and bundles. Additionally, third-party bundles will bring in
additional listener not listed here.
additional listeners not listed here.

kernel.request
..............
Expand Down Expand Up @@ -606,7 +606,7 @@ configuration, and tag it with ``kernel.event_subscriber``:
kernel.fragment_renderer
------------------------

**Purpose**: Add a new HTTP content rendering strategy.
**Purpose**: Add a new HTTP content rendering strategy

To add a new rendering strategy - in addition to the core strategies like
``EsiFragmentRenderer`` - create a class that implements
Expand Down Expand Up @@ -1091,7 +1091,7 @@ configuration, and tag it with ``twig.extension``:

For information on how to create the actual Twig Extension class, see
`Twig's documentation`_ on the topic or read the cookbook article:
:doc:`/cookbook/templating/twig_extension`
:doc:`/cookbook/templating/twig_extension`.

Before writing your own extensions, have a look at the
`Twig official extension repository`_ which already includes several
Expand Down