Skip to content

Commit 4d500e9

Browse files
committed
minor #15297 [Runtime] Minor fixes (javiereguiluz)
This PR was merged into the 5.3-dev branch. Discussion ---------- [Runtime] Minor fixes These are really minor tweaks because the article is excellent and explain things in great detail. Commits ------- ec1920e [Runtime] Minor fixes
2 parents d7d3f7c + ec1920e commit 4d500e9

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

components/runtime.rst

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ the component. This file runs the following logic:
4646

4747
#. It instantiates a :class:`Symfony\\Component\\Runtime\\RuntimeInterface`;
4848
#. The callable (returned by ``public/index.php``) is passed to the Runtime, whose job
49-
is to resolve the arguments (in this example: ``array $content``);
49+
is to resolve the arguments (in this example: ``array $context``);
5050
#. Then, this callable is called to get the application (``App\Kernel``);
5151
#. At last, the Runtime is used to run the application (i.e. calling
5252
``$kernel->handle(Request::createFromGlobals())->send()``).
@@ -172,12 +172,12 @@ a number of different applications are supported::
172172
The ``SymfonyRuntime`` can handle these applications:
173173

174174
:class:`Symfony\\Component\\HttpKernel\\HttpKernelInterface`
175-
The application will be run with :class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\HttpKernelRunner``
175+
The application will be run with :class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\HttpKernelRunner`
176176
like a "standard" Symfony application.
177177

178178
:class:`Symfony\\Component\\HttpFoundation\\Response`
179179
The Response will be printed by
180-
:class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\ResponseRunner``::
180+
:class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\ResponseRunner`::
181181

182182
<?php
183183
// public/index.php
@@ -191,7 +191,7 @@ The ``SymfonyRuntime`` can handle these applications:
191191

192192
:class:`Symfony\\Component\\Console\\Command\\Command`
193193
To write single command applications. This will use the
194-
:class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\ConsoleApplicationRunner``::
194+
:class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\ConsoleApplicationRunner`::
195195

196196
<?php
197197

@@ -211,7 +211,7 @@ The ``SymfonyRuntime`` can handle these applications:
211211

212212
:class:`Symfony\\Component\\Console\\Application`
213213
Useful with console applications with more than one command. This will use the
214-
:class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\ConsoleApplicationRunner``::
214+
:class:`Symfony\\Component\\Runtime\\Runner\\Symfony\\ConsoleApplicationRunner`::
215215

216216
<?php
217217

@@ -361,7 +361,7 @@ class will have more control and can fix bugs and add features.
361361

362362
.. note::
363363

364-
Before Symfony 5.3, the Symfony boostrap logic was part of a Flex recipe.
364+
Before Symfony 5.3, the Symfony bootstrap logic was part of a Flex recipe.
365365
Since recipes are rarely updated by users, bug patches would rarely be
366366
installed.
367367

@@ -377,7 +377,7 @@ application outside of the global state in 6 steps:
377377
represents the application.
378378
#. This *application object* is passed to ``RuntimeInterface::getRunner()``, which
379379
returns a :class:`Symfony\\Component\\Runtime\\RunnerInterface`: an instance
380-
that knows how to "run" the appliction object.
380+
that knows how to "run" the application object.
381381
#. The ``RunnerInterface::run(object $application)`` is called and it returns the
382382
exit status code as `int`.
383383
#. The PHP engine is exited with this status code.

0 commit comments

Comments
 (0)