8000 minor #5862 Fixes done automatically by the docbot (WouterJ) · symfony/symfony-docs@1e9c1c9 · GitHub
[go: up one dir, main page]
Skip to content

Commit 1e9c1c9

Browse files
weaverryanweaverryan
committed
minor #5862 Fixes done automatically by the docbot (WouterJ)
This PR was merged into the 2.3 branch. Discussion ---------- Fixes done automatically by the docbot Started working on the docbot again this week and these are the first results (to be honest: I did remove some invalid changes from this PR). You can see the new docbot code (which is far from perfect) in wouterj/docbot#14 | Q | A | --- | --- | Doc fix? | yes | New docs? | no | Applies to | 2.3+ | Fixed tickets | - Commits ------- 4dd3b8a Fixes done automatically by the docbot
2 parents 9d56e24 + 4dd3b8a commit 1e9c1c9

8 files changed

+8
-8
lines changed

‎create_framework/dependency-injection.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ them. Objects will be created on-demand when you access them from the
132132
container or when the container needs them to create other objects.
133133

134134
For instance, to create the router listener, we tell Symfony that its class
135-
name is ``Symfony\Component\HttpKernel\EventListener\RouterListener``, and
135+
name is ``Symfony\Component\HttpKernel\EventListener\RouterListener`` and
136136
that its constructor takes a matcher object (``new Reference('matcher')``). As
137137
you can see, each object is referenced by a name, a string that uniquely
138138
identifies each object. The name allows us to get an object and to reference

‎create_framework/event-dispatcher.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -154,7 +154,7 @@ event (``response``); the event name must be the same as the one used in the
154154
``dispatch()`` call.
155155

156156
In the listener, we add the Google Analytics code only if the response is not
157-
a redirection, if the requested format is HTML, and if the response content
157+
a redirection, if the requested format is HTML and if the response content
158158
type is HTML (these conditions demonstrate the ease of manipulating the
159159
Request and Response data from your code).
160160

‎create_framework/front-controller.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ And for the "Goodbye" page::
5757

5858
We have indeed moved most of the shared code into a central place, but it does
5959
not feel like a good abstraction, does it? We still have the ``send()`` method
60-
for all pages, our pages do not look like templates, and we are still not able
60+
for all pages, our pages do not look like templates and we are still not able
6161
to test this code properly.
6262

6363
Moreover, adding a new page means that we need to create a new PHP script,

‎create_framework/http-foundation.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -299,7 +299,7 @@ the wheel.
299299
I've almost forgot to talk about one added benefit: using the HttpFoundation
300300
component is the start of better interoperability between all frameworks and
301301
applications using it (like `Symfony`_, `Drupal 8`_, `phpBB 4`_, `ezPublish
302-
5`_, `Laravel`_, `Silex`_, and `more`_).
302+
5`_, `Laravel`_, `Silex`_ and `more`_).
303303

304304
.. _`Twig`: http://twig.sensiolabs.org/
305305
.. _`HTTP specification`: http://tools.ietf.org/wg/httpbis/

‎create_framework/http-kernel-httpkernel-class.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ There should be an easier way, right?
1111

1212
Enter the ``HttpKernel`` class. Instead of solving the same problem over and
1313
over again and instead of reinventing the wheel each time, the ``HttpKernel``
14-
class is a generic, extensible, and flexible implementation of
14+
class is a generic, extensible and flexible implementation of
1515
``HttpKernelInterface``.
1616

1717
This class is very similar to the framework class we have written so far: it

‎create_framework/routing.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ of default values for route attributes (``array('name' => 'World')``).
8282
:doc:`Routing component documentation </components/routing/introduction>` to
8383
learn more about its many features like URL generation, attribute
8484
requirements, HTTP method enforcements, loaders for YAML or XML files,
85-
dumpers to PHP or Apache rewrite rules for enhanced performance, and much
85+
dumpers to PHP or Apache rewrite rules for enhanced performance and much
8686
more.
8787

8888
Based on the information stored in the ``RouteCollection`` instance, a

‎create_framework/separation-of-concerns.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ class. It would bring us better *reusability* and easier testing to name just
88
a few benefits.
99

1010
If you have a closer look at the code, ``front.php`` has one input, the
11-
Request, and one output, the Response. Our framework class will follow this
11+
Request and one output, the Response. Our framework class will follow this
1212
simple principle: the logic is about creating the Response associated with a
1313
Request.
1414

‎create_framework/templating.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ rendered::
5050

5151
As ``render_template`` is used as an argument to the PHP ``call_user_func()``
5252
function, we can replace it with any valid PHP `callbacks`_. This allows us to
53-
use a function, an anonymous function, or a method of a class as a
53+
use a function, an anonymous function or a method of a class as a
5454
controller... your choice.
5555

5656
As a convention, for each route, the associated controller is configured via

0 commit comments

Comments
 (0)
0