Skip to content

Updated some cookbook titles to match the usual format #1725

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.

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
Show file tree
Hide file tree
Changes from all commits
Commits
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
6 changes: 3 additions & 3 deletions cookbook/doctrine/event_listeners_subscribers.rst
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,8 @@

.. _doctrine-event-config:

Registering Event Listeners and Subscribers
===========================================
How to Register Event Listeners and Subscribers
===============================================

Doctrine packages a rich event system that fires events when almost anything
happens inside the system. For you, this means that you can create arbitrary
Expand Down Expand Up @@ -114,4 +114,4 @@ specific type of entity (e.g. a ``Product`` entity but not a ``BlogPost``
entity), you should check for the class name of the entity in your method
(as shown above).

.. _`The Event System`: http://docs.doctrine-project.org/projects/doctrine-orm/en/2.1/reference/events.html
.. _`The Event System`: http://docs.doctrine-project.org/projects/doctrine-orm/en/2.1/reference/events.html
6 changes: 3 additions & 3 deletions cookbook/routing/method_parameters.rst
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
.. index::
single: Routing; _method

Using HTTP Methods beyond GET and POST in Routes
================================================
How to use HTTP Methods beyond GET and POST in Routes
=====================================================

The HTTP method of a request is one of the requirements that can be checked
when seeing if it matches a route. This is introduced in the routing chapter
Expand Down Expand Up @@ -111,4 +111,4 @@ Likewise the delete form could be changed to look like this:
<input type="submit" value="Delete" />
</form>

It will then match the ``blog_delete`` route.
It will then match the ``blog_delete`` route.