8000 Fixed typos spotted by @cordoval · symfony/symfony-docs@a7b916e · GitHub
[go: up one dir, main page]

Skip to content

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit a7b916e

Browse files
author
Loïc Chardonnet
committed
Fixed typos spotted by @cordoval
1 parent a055140 commit a7b916e

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

cookbook/console/console_command.rst

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ Register Commands in the Service Container
7171
Support for registering commands in the service container was added in
7272
version 2.4.
7373

74-
By default, Symfony will take a look in the ``Command`` directory of you
74+
By default, Symfony will take a look in the ``Command`` directory of your
7575
bundles and automatically register your commands. For the ones implementing
7676
the ``ContainerAwareCommand`` interface, Symfony will even inject the container.
7777

@@ -114,9 +114,10 @@ the ``console.command`` tag:
114114
115115
.. tip::
116116

117-
Command as a service can be usefull in few situations:
117+
Commands as services can be useful in few situations:
118118

119-
* If you need your commands to be defined somewhere else than ``Command``;
119+
* if you need your commands to be defined somewhere else than in the
120+
``Command`` folder;
120121
* if you need to access services or configuration parameters in the
121122
``configure`` method.
122123

0 commit comments

Comments
 (0)
0