Skip to content

Commit 34287db

Browse files
sandobajaviereguiluz
authored andcommitted
Fix ~20 typos in different sections of the documentation
1 parent ab7ede7 commit 34287db

20 files changed

+30
-30
lines changed

best_practices.rst

+3-3
Original file line numberDiff line numberDiff line change
@@ -245,7 +245,7 @@ the fact that a controller should always return a ``Response`` object.
245245
Use Dependency Injection to Get Services
246246
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
247247

248-
If you extend the base ``AbstractController``, you can only access to the most
248+
If you extend the base ``AbstractController``, you can only get access to the most
249249
common services (e.g ``twig``, ``router``, ``doctrine``, etc.), directly from the
250250
container via ``$this->container->get()``.
251251
Instead, you must use dependency injection to fetch services by
@@ -289,7 +289,7 @@ Define your Forms as PHP Classes
289289

290290
Creating :ref:`forms in classes <creating-forms-in-classes>` allows to reuse
291291
them in different parts of the application. Besides, not creating forms in
292-
controllers simplify the code and maintenance of the controllers.
292+
controllers simplifies the code and maintenance of the controllers.
293293

294294
Add Form Buttons in Templates
295295
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -388,7 +388,7 @@ Use Webpack Encore to Process Web Assets
388388
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
389389

390390
Web assets are things like CSS, JavaScript and image files that make the
391-
frontend of your site looks and works great. `Webpack`_ is the leading JavaScript
391+
frontend of your site look and work great. `Webpack`_ is the leading JavaScript
392392
module bundler that compiles, transforms and packages assets for usage in a browser.
393393

394394
:doc:`Webpack Encore </frontend>` is a JavaScript library that gets rid of most

components/browser_kit.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -174,7 +174,7 @@ provides access to the form properties (e.g. ``$form->getUri()``,
174174
Custom Header Handling
175175
~~~~~~~~~~~~~~~~~~~~~~
176176

177-
The optional HTTP headers passed to the ``request()`` method follows the FastCGI
177+
The optional HTTP headers passed to the ``request()`` method follow the FastCGI
178178
request format (uppercase, underscores instead of dashes and prefixed with ``HTTP_``).
179179
Before saving those headers to the request, they are lower-cased, with ``HTTP_``
180180
stripped, and underscores converted into dashes.

components/console/helpers/progressbar.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -293,7 +293,7 @@ to display it can be customized::
293293
.. caution::
294294

295295
For performance reasons, Symfony redraws the screen once every 100ms. If this is too
296-
fast or to slow for your application, use the methods
296+
fast or too slow for your application, use the methods
297297
:method:`Symfony\\Component\\Console\\Helper\\ProgressBar::minSecondsBetweenRedraws` and
298298
:method:`Symfony\\Component\\Console\\Helper\\ProgressBar::maxSecondsBetweenRedraws`::
299299

components/http_kernel.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ The HttpKernel Component
99
The HttpKernel component provides a structured process for converting
1010
a ``Request`` into a ``Response`` by making use of the EventDispatcher
1111
component. It's flexible enough to create a full-stack framework (Symfony),
12-
a micro-framework (Silex) or an advanced CMS system (Drupal).
12+
a micro-framework (Silex) or an advanced CMS (Drupal).
1313

1414
Installation
1515
------------

components/property_access.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
The PropertyAccess Component
66
============================
77

8-
The PropertyAccess component provides function to read and write from/to an
8+
The PropertyAccess component provides functions to read and write from/to an
99
object or array using a simple string notation.
1010

1111
Installation

configuration/front_controllers_and_kernel.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -247,7 +247,7 @@ the directory of the environment you're using (most commonly ``dev/`` while
247247
developing and debugging). While it can vary, the ``var/cache/dev/`` directory
248248
includes the following:
249249

250-
``srcApp_KernelDevDebugContainer.php``
250+
``App_KernelDevDebugContainer.php``
251251
The cached "service container" that represents the cached application
252252
configuration.
253253

configuration/micro_kernel_trait.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ Advanced Example: Twig, Annotations and the Web Debug Toolbar
103103
-------------------------------------------------------------
104104

105105
The purpose of the ``MicroKernelTrait`` is *not* to have a single-file application.
106-
Instead, its goal to give you the power to choose your bundles and structure.
106+
Instead, its goal is to give you the power to choose your bundles and structure.
107107

108108
First, you'll probably want to put your PHP classes in an ``src/`` directory. Configure
109109
your ``composer.json`` file to load from there:

create_framework/http_foundation.rst

+4-4
Original file line numberDiff line numberDiff line change
@@ -176,20 +176,20 @@ fingertips thanks to a nice and simple API::
176176
// the URI being requested (e.g. /about) minus any query parameters
177177
$request->getPathInfo();
178178

179-
// retrieve GET and POST variables respectively
179+
// retrieves GET and POST variables respectively
180180
$request->query->get('foo');
181181
$request->request->get('bar', 'default value if bar does not exist');
182182

183-
// retrieve SERVER variables
183+
// retrieves SERVER variables
184184
$request->server->get('HTTP_HOST');
185185

186186
// retrieves an instance of UploadedFile identified by foo
187187
$request->files->get('foo');
188188

189-
// retrieve a COOKIE value
189+
// retrieves a COOKIE value
190190
$request->cookies->get('PHPSESSID');
191191

192-
// retrieve an HTTP request header, with normalized, lowercase keys
192+
// retrieves a HTTP request header, with normalized, lowercase keys
193193
$request->headers->get('host');
194194
$request->headers->get('content-type');
195195

deployment.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Using Platforms as a Service
6565

6666
Using a Platform as a Service (PaaS) can be a great way to deploy your Symfony
6767
app quickly. There are many PaaS, but we recommend `Platform.sh`_ as it
68-
provides a dedicated Symfony integration and help fund the Symfony development.
68+
provides a dedicated Symfony integration and helps fund the Symfony development.
6969

7070
Using Build Scripts and other Tools
7171
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

doctrine/associations.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -592,7 +592,7 @@ To update a relationship in the database, you *must* set the relationship on the
592592
*owning* side. The owning side is always where the ``ManyToOne`` mapping is set
593593
(for a ``ManyToMany`` relation, you can choose which side is the owning side).
594594

595-
Does this means it's not possible to call ``$category->addProduct()`` or
595+
Does this mean it's not possible to call ``$category->addProduct()`` or
596596
``$category->removeProduct()`` to update the database? Actually, it *is* possible,
597597
thanks to some clever code that the ``make:entity`` command generated::
598598

migration.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ It is quite common for an existing application to either not have a test suite
130130
at all or have low code coverage. Introducing unit tests for this code is
131131
likely not cost effective as the old code might be replaced with functionality
132132
from Symfony components or might be adapted to the new application.
133-
Additionally legacy code tends to be hard to write tests for making the process
133+
Additionally legacy code tends to be hard to write tests for, making the process
134134
slow and cumbersome.
135135

136136
Instead of providing low level tests, that ensure each class works as expected, it

notifier/chatters.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ you to send messages to chat services like Slack or Telegram::
2323
public function thankyou(ChatterInterface $chatter)
2424
{
2525
$message = (new ChatMessage('You got a new invoice for 15 EUR.'))
26-
// if not set explicitly, the message is send to the
26+
// if not set explicitly, the message is sent to the
2727
// default transport (the first one configured)
2828
->transport('slack');
2929

rate_limiter.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -359,7 +359,7 @@ the :class:`Symfony\\Component\\RateLimiter\\Reservation` object returned by the
359359
Storing Rate Limiter State
360360
--------------------------
361361

362-
All rate limiter policies require to store their state(e.g. how many hits were
362+
All rate limiter policies require to store their state (e.g. how many hits were
363363
already made in the current time window). By default, all limiters use the
364364
``cache.rate_limiter`` cache pool created with the :doc:`Cache component </cache>`.
365365

reference/constraints/Image.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -366,7 +366,7 @@ value.
366366
``maxPixelsMessage``
367367
~~~~~~~~~~~~~~~~~~~~
368368

369-
**type**: ``string`` **default**: ``The image has to many pixels ({{ pixels }} pixels).
369+
**type**: ``string`` **default**: ``The image has too many pixels ({{ pixels }} pixels).
370370
Maximum amount expected is {{ max_pixels }} pixels.``
371371

372372
The error message if the amount of pixels of the image exceeds `maxPixels`_.

reference/forms/types/datetime.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ the data can be a ``DateTime`` object, a string, a timestamp or an array.
1313
+---------------------------+-----------------------------------------------------------------------------+
1414
| Underlying Data Type | can be ``DateTime``, string, timestamp, or array (see the ``input`` option) |
1515
+---------------------------+-----------------------------------------------------------------------------+
16-
| Rendered as | single text box or three select fields |
16+
| Rendered as | single text box or five select fields |
1717
+---------------------------+-----------------------------------------------------------------------------+
1818
| Default invalid message | Please enter a valid date and time. |
1919
+---------------------------+-----------------------------------------------------------------------------+

routing/custom_route_loader.rst

+3-3
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@ How to Create a custom Route Loader
77
Basic applications can define all their routes in a single configuration file -
88
usually ``config/routes.yaml`` (see :ref:`routing-creating-routes`).
99
However, in most applications it's common to import routes definitions from
10-
different resources: PHP annotations in controller files, YAML, XML or PHP
11-
files stored in some directory, etc.
10+
different resources: PHP annotations or attributes in controller files, YAML, XML
11+
or PHP files stored in some directory, etc.
1212

1313
Built-in Route Loaders
1414
----------------------
@@ -214,7 +214,7 @@ tag it manually with ``routing.route_loader``.
214214

215215
.. tip::
216216

217-
If your service is invokable, you don't need to precise the method to use.
217+
If your service is invokable, you don't need to specify the method to use.
218218

219219
Creating a custom Loader
220220
------------------------

security.rst

+2-2
Original file line numberDiff line numberDiff line change
@@ -995,7 +995,7 @@ Enable the authenticator using the ``json_login`` setting:
995995
mandatory wildcards - e.g. ``/login/{foo}`` where ``foo`` has no
996996
default value).
997997

998-
The authenticator runs when a client request the ``check_path``. First,
998+
The authenticator runs when a client requests the ``check_path``. First,
999999
create a controller for this path:
10001000

10011001
.. code-block:: terminal
@@ -1078,7 +1078,7 @@ That's it! To summarize the process:
10781078
"password": "MyPassword"
10791079
}
10801080
#. The security system intercepts the request, checks the user's submitted
1081-
credentials and authenticates the user. If the credentials is incorrect,
1081+
credentials and authenticates the user. If the credentials are incorrect,
10821082
an HTTP 401 Unauthorized JSON response is returned, otherwise your
10831083
controller is run;
10841084
#. Your controller creates the correct response:

security/remember_me.rst

+3-3
Original file line numberDiff line numberDiff line change
@@ -87,9 +87,9 @@ which is defined using the ``APP_SECRET`` environment variable.
8787
After enabling the ``remember_me`` system in the configuration, there are a
8888
couple more things to do before remember me works correctly:
8989

90-
#. :ref:`Add an opt-in checkbox to active remember me <security-remember-me-activate>`;
90+
#. :ref:`Add an opt-in checkbox to activate remember me <security-remember-me-activate>`;
9191
#. :ref:`Use an authenticator that supports remember me <security-remember-me-authenticator>`;
92-
#. Optionally, :ref:`configure the how remember me cookies are stored and validated <security-remember-me-storage>`.
92+
#. Optionally, :ref:`configure how remember me cookies are stored and validated <security-remember-me-storage>`.
9393

9494
After this, the remember me cookie will be created upon successful
9595
authentication. For some pages/actions, you can
@@ -131,7 +131,7 @@ checkbox must have a name of ``_remember_me``:
131131
.. note::
132132

133133
Optionally, you can configure a custom name for this checkbox using the
134-
``remember_me_parameter`` setting under the ``remember_me`` section.
134+
``name`` setting under the ``remember_me`` section.
135135

136136
Always activating Remember Me
137137
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

service_container/factories.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Static Factories
1919
Suppose you have a factory that configures and returns a new ``NewsletterManager``
2020
object by calling the static ``createNewsletterManager()`` method::
2121

22-
// src/Email\NewsletterManagerStaticFactory.php
22+
// src/Email/NewsletterManagerStaticFactory.php
2323
namespace App\Email;
2424

2525
// ...

session.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ sessions, check their default configuration:
7878
Setting the ``handler_id`` config option to ``null`` means that Symfony will
7979
use the native PHP session mechanism. The session metadata files will be stored
8080
outside of the Symfony application, in a directory controlled by PHP. Although
81-
this usually simplify things, some session expiration related options may not
81+
this usually simplifies things, some session expiration related options may not
8282
work as expected if other applications that write to the same directory have
8383
short max lifetime settings.
8484

0 commit comments

Comments
 (0)