diff --git a/bundles/best_practices.rst b/bundles/best_practices.rst index 4452380dc90..6424d807b5a 100644 --- a/bundles/best_practices.rst +++ b/bundles/best_practices.rst @@ -23,7 +23,7 @@ vendor segment, followed by zero or more category segments, and it ends with the namespace short name, which must end with ``Bundle``. A namespace becomes a bundle as soon as you add a bundle class to it. The -bundle class name must follow these simple rules: +bundle class name must follow these rules: * Use only alphanumeric characters and underscores; * Use a StudlyCaps name (i.e. camelCase with the first letter uppercased); @@ -467,8 +467,9 @@ Retrieve the configuration parameters in your code from the container:: $container->getParameter('acme_blog.author.email'); -Even if this mechanism is simple enough, you should consider using the more -advanced :doc:`semantic bundle configuration `. +While this mechanism requires the least effort, you should consider using the +more advanced :doc:`semantic bundle configuration ` to +make your configuration more robust. Versioning ---------- diff --git a/bundles/override.rst b/bundles/override.rst index 8c8f434f9de..f4cadb965b1 100644 --- a/bundles/override.rst +++ b/bundles/override.rst @@ -68,7 +68,7 @@ the routes from any bundle, then they must be manually imported from somewhere in your application (e.g. ``config/routes.yaml``). The easiest way to "override" a bundle's routing is to never import it at -all. Instead of importing a third-party bundle's routing, simply copy +all. Instead of importing a third-party bundle's routing, copy that routing file into your application, modify it, and import it instead. Controllers diff --git a/configuration/configuration_organization.rst b/configuration/configuration_organization.rst index 11f8c2aaede..2647f3ba4a4 100644 --- a/configuration/configuration_organization.rst +++ b/configuration/configuration_organization.rst @@ -5,7 +5,7 @@ How to Organize Configuration Files =================================== The Symfony skeleton defines three :doc:`execution environments ` -called ``dev``, ``prod`` and ``test``. An environment simply represents a way +called ``dev``, ``prod`` and ``test``. An environment represents a way to execute the same codebase with different configurations. In order to select the configuration file to load for each environment, Symfony @@ -129,9 +129,9 @@ Global Configuration Files Some system administrators may prefer to store sensitive parameters in files outside the project directory. Imagine that the database credentials for your -website are stored in the ``/etc/sites/mysite.com/parameters.yaml`` file. Loading -this file is as simple as indicating the full file path when importing it from -any other configuration file: +website are stored in the ``/etc/sites/mysite.com/parameters.yaml`` file. You +can load files from outside the project folder by indicating the full file path +when importing it from any other configuration file: .. configuration-block:: diff --git a/configuration/environments.rst b/configuration/environments.rst index de67c3fec45..6c26d53ff1d 100644 --- a/configuration/environments.rst +++ b/configuration/environments.rst @@ -199,7 +199,7 @@ Creating a new Environment -------------------------- Since an environment is nothing more than a string that corresponds to a set of -configuration, creating a new environment is quite easy. +configuration, you can also create your own environments for specific purposes. Suppose, for example, that before deployment, you need to benchmark your application. One way to benchmark the application is to use near-production @@ -355,7 +355,7 @@ includes the following: .. note:: - You can easily change the directory location and name. For more information + You can change the directory location and name. For more information read the article :doc:`/configuration/override_dir_structure`. Going further diff --git a/configuration/front_controllers_and_kernel.rst b/configuration/front_controllers_and_kernel.rst index 7faf233b7de..61ded2eb384 100644 --- a/configuration/front_controllers_and_kernel.rst +++ b/configuration/front_controllers_and_kernel.rst @@ -51,7 +51,7 @@ You can choose the front controller that's used by adding it in the URL, like: http://localhost/index.php/some/path/... As you can see, this URL contains the PHP script to be used as the front -controller. You can use that to easily switch to a custom made front controller +controller. You can use that to switch to a custom made front controller that is located in the ``public/`` directory. .. seealso:: @@ -123,7 +123,7 @@ controller to make use of the new kernel. The Environments ---------------- -As just mentioned, the ``Kernel`` has to implement another method - +As mentioned above, the ``Kernel`` has to implement another method - :method:`Symfony\\Bundle\\FrameworkBundle\\Kernel\\MicroKernelTrait::configureContainer`. This method is responsible for loading the application's configuration from the right *environment*. diff --git a/configuration/micro_kernel_trait.rst b/configuration/micro_kernel_trait.rst index 5a35462b209..6d7cabf68e1 100644 --- a/configuration/micro_kernel_trait.rst +++ b/configuration/micro_kernel_trait.rst @@ -5,8 +5,8 @@ The default ``Kernel`` class included in Symfony applications uses a :class:`Symfony\\Bundle\\FrameworkBundle\\Kernel\\MicroKernelTrait` to configure the bundles, the routes and the service container in the same class. -This micro-kernel approach is so flexible that let you control your application -structure and features quite easily. +This micro-kernel approach is flexible, allowing you to control your application +structure and features. A Single-File Symfony Application --------------------------------- diff --git a/configuration/multiple_kernels.rst b/configuration/multiple_kernels.rst index a6d3449685f..d5999b96c20 100644 --- a/configuration/multiple_kernels.rst +++ b/configuration/multiple_kernels.rst @@ -124,7 +124,7 @@ According to the above code, this config will live in one or multiple files stored in ``config/api/`` and ``config/api/ENVIRONMENT_NAME/`` directories. The new configuration files can be created from scratch when you load just a few -bundles, because it will be very simple. Otherwise, duplicate the existing +bundles, because it will be small. Otherwise, duplicate the existing config files in ``config/packages/`` or better, import them and override the needed options. diff --git a/configuration/override_dir_structure.rst b/configuration/override_dir_structure.rst index 6bf0a1d9dc4..ee3d4bf7586 100644 --- a/configuration/override_dir_structure.rst +++ b/configuration/override_dir_structure.rst @@ -5,7 +5,7 @@ How to Override Symfony's default Directory Structure ===================================================== Symfony automatically ships with a default directory structure. You can -easily override this directory structure to create your own. The default +override this directory structure to create your own. The default directory structure is: .. code-block:: text diff --git a/console/input.rst b/console/input.rst index 8cca2f34d4b..2a8f034c0fc 100644 --- a/console/input.rst +++ b/console/input.rst @@ -71,7 +71,7 @@ to greet all your friends). Only the last argument can be a list:: 'Who do you want to greet (separate multiple names with a space)?' ); -To use this, just specify as many names as you want: +To use this, specify as many names as you want: .. code-block:: terminal diff --git a/console/lazy_commands.rst b/console/lazy_commands.rst index 02179b0e914..0fef23838dc 100644 --- a/console/lazy_commands.rst +++ b/console/lazy_commands.rst @@ -42,7 +42,7 @@ Built-in Command Loaders ~~~~~~~~~~~~~~~~~~~~~~~~ The :class:`Symfony\\Component\\Console\\CommandLoader\\FactoryCommandLoader` -class provides a simple way of getting commands lazily loaded as it takes an +class provides a way of getting commands lazily loaded as it takes an array of ``Command`` factories as its only constructor argument:: use Symfony\Component\Console\CommandLoader\FactoryCommandLoader; diff --git a/console/style.rst b/console/style.rst index 9bdcbaf1631..c80e31b11ed 100644 --- a/console/style.rst +++ b/console/style.rst @@ -336,7 +336,7 @@ Defining your Own Styles ------------------------ If you don't like the design of the commands that use the Symfony Style, you can -define your own set of console styles. Just create a class that implements the +define your own set of console styles. Create a class that implements the :class:`Symfony\\Component\\Console\\Style\\StyleInterface`:: namespace App\Console; diff --git a/contributing/code/git.rst b/contributing/code/git.rst index ce0642c5599..4ff26d324b3 100644 --- a/contributing/code/git.rst +++ b/contributing/code/git.rst @@ -10,7 +10,7 @@ Pull Requests Whenever a pull request is merged, all the information contained in the pull request (including comments) is saved in the repository. -You can easily spot pull request merges as the commit message always follows +You can identify pull request merges as the commit message always follows this pattern: .. code-block:: text diff --git a/contributing/code/reproducer.rst b/contributing/code/reproducer.rst index fe7a2a74255..be6514c842c 100644 --- a/contributing/code/reproducer.rst +++ b/contributing/code/reproducer.rst @@ -63,7 +63,7 @@ to a route definition. Then, after creating your project: #. Don't edit any of the default Symfony configuration options. #. Don't copy your original application code and don't use the same structure of controllers, actions, etc. as in your original application. -#. Create a simple controller and add your routing definition that shows the bug. +#. Create a small controller and add your routing definition that shows the bug. #. Don't create or modify any other file. #. Execute ``composer require symfony/web-server-bundle`` and use the ``server:run`` command to browse to the new route and see if the bug appears or not. diff --git a/contributing/community/review-comments.rst b/contributing/community/review-comments.rst index a317c12fa27..2b7a5f04047 100644 --- a/contributing/community/review-comments.rst +++ b/contributing/community/review-comments.rst @@ -26,7 +26,7 @@ constructive, respectful and helpful reviews and replies. your ideas and opinions but helping you to better communicate, prevent possible confusion, and keeping the Symfony community a welcoming place for everyone. **You are free to disagree with - someone's opinions, just don't be disrespectful.** + someone's opinions, but don't be disrespectful.** First of, accept that many programming decisions are opinions. Discuss trade offs, which you prefer, and reach a resolution quickly. diff --git a/controller/error_pages.rst b/controller/error_pages.rst index 5564fe9be88..9f4774fa6e1 100644 --- a/controller/error_pages.rst +++ b/controller/error_pages.rst @@ -11,7 +11,7 @@ exception in your code. In the :doc:`development environment `, Symfony catches all the exceptions and displays a special **exception page** -with lots of debug information to help you quickly discover the root problem: +with lots of debug information to help you discover the root problem: .. image:: /_images/controller/error_pages/exceptions-in-dev-environment.png :alt: A typical exception page in the development environment @@ -198,7 +198,7 @@ If you need a little more flexibility beyond just overriding the template, then you can change the controller that renders the error page. For example, you might need to pass some additional variables into your template. -To do this, simply create a new controller anywhere in your application and set +To do this, create a new controller anywhere in your application and set the :ref:`twig.exception_controller ` configuration option to point to it: @@ -249,8 +249,8 @@ will be passed two parameters: A :class:`\\Symfony\\Component\\HttpKernel\\Log\\DebugLoggerInterface` instance which may be ``null`` in some circumstances. -Instead of creating a new exception controller from scratch you can, of course, -also extend the default :class:`Symfony\\Bundle\\TwigBundle\\Controller\\ExceptionController`. +Instead of creating a new exception controller from scratch you can also extend +the default :class:`Symfony\\Bundle\\TwigBundle\\Controller\\ExceptionController`. In that case, you might want to override one or both of the ``showAction()`` and ``findTemplate()`` methods. The latter one locates the template to be used. diff --git a/controller/service.rst b/controller/service.rst index 3c04f55688d..071e444c9a2 100644 --- a/controller/service.rst +++ b/controller/service.rst @@ -75,7 +75,7 @@ Invokable Controllers --------------------- If your controller implements the ``__invoke()`` method - popular with the -Action-Domain-Response (ADR) pattern, you can simply refer to the service id +Action-Domain-Response (ADR) pattern, you can refer to the service id without the method (``App\Controller\HelloController`` for example). Alternatives to base Controller Methods diff --git a/controller/soap_web_service.rst b/controller/soap_web_service.rst index 85e2dfa4ef2..bcaa79f826e 100644 --- a/controller/soap_web_service.rst +++ b/controller/soap_web_service.rst @@ -6,8 +6,8 @@ How to Create a SOAP Web Service in a Symfony Controller ======================================================== -Setting up a controller to act as a SOAP server is simple with a couple -tools. You must, of course, have the `PHP SOAP`_ extension installed. +Setting up a controller to act as a SOAP server is aided by a couple +tools. Those tools expect you to have the `PHP SOAP`_ extension installed. As the PHP SOAP extension cannot currently generate a WSDL, you must either create one from scratch or use a 3rd party generator. diff --git a/create_framework/event_dispatcher.rst b/create_framework/event_dispatcher.rst index 8939659bd4f..f76c86cf1ad 100644 --- a/create_framework/event_dispatcher.rst +++ b/create_framework/event_dispatcher.rst @@ -248,8 +248,8 @@ issue: the knowledge of the priorities is "hardcoded" in the front controller, instead of being in the listeners themselves. For each application, you have to remember to set the appropriate priorities. Moreover, the listener method names are also exposed here, which means that refactoring our listeners would -mean changing all the applications that rely on those listeners. Of course, -there is a solution: use subscribers instead of listeners:: +mean changing all the applications that rely on those listeners. The solution +to this dilemma is to use subscribers instead of listeners:: $dispatcher = new EventDispatcher(); $dispatcher->addSubscriber(new Simplex\ContentLengthListener()); diff --git a/create_framework/front_controller.rst b/create_framework/front_controller.rst index b2acfc06ade..f28afe8531c 100644 --- a/create_framework/front_controller.rst +++ b/create_framework/front_controller.rst @@ -61,7 +61,7 @@ which name is exposed to the end user via the URL (``http://127.0.0.1:4321/bye.php``): there is a direct mapping between the PHP script name and the client URL. This is because the dispatching of the request is done by the web server directly. It might be a good idea to move this -dispatching to our code for better flexibility. This can be easily achieved by +dispatching to our code for better flexibility. This can be achieved by routing all client requests to a single PHP script. .. tip:: diff --git a/create_framework/http_foundation.rst b/create_framework/http_foundation.rst index df7bab89136..79ff1c953a6 100644 --- a/create_framework/http_foundation.rst +++ b/create_framework/http_foundation.rst @@ -201,7 +201,7 @@ You can also simulate a request:: $request = Request::create('/index.php?name=Fabien'); -With the ``Response`` class, you can easily tweak the response:: +With the ``Response`` class, you can tweak the response:: $response = new Response(); diff --git a/create_framework/http_kernel_controller_resolver.rst b/create_framework/http_kernel_controller_resolver.rst index 860f5003bed..c5817c26bcc 100644 --- a/create_framework/http_kernel_controller_resolver.rst +++ b/create_framework/http_kernel_controller_resolver.rst @@ -109,7 +109,7 @@ correctly:: public function index($request) More interesting, ``getArguments()`` is also able to inject any Request -attribute; the argument just needs to have the same name as the corresponding +attribute; if the argument has the same name as the corresponding attribute:: public function index($year) @@ -127,7 +127,7 @@ optional attribute of the Request:: public function index($year = 2012) -Let's just inject the ``$year`` request attribute for our controller:: +Let's inject the ``$year`` request attribute for our controller:: class LeapYearController { diff --git a/create_framework/http_kernel_httpkernel_class.rst b/create_framework/http_kernel_httpkernel_class.rst index 1c3892a6e05..20479f8ccfd 100644 --- a/create_framework/http_kernel_httpkernel_class.rst +++ b/create_framework/http_kernel_httpkernel_class.rst @@ -104,8 +104,8 @@ The error controller reads as follows:: } } -Voilà! Clean and customizable error management without efforts. And of course, -if your controller throws an exception, HttpKernel will handle it nicely. +Voilà! Clean and customizable error management without efforts. And +if your ``ErrorController`` throws an exception, HttpKernel will handle it nicely. In chapter two, we talked about the ``Response::prepare()`` method, which ensures that a Response is compliant with the HTTP specification. It is @@ -115,8 +115,7 @@ client; that's what the ``ResponseListener`` does:: $dispatcher->addSubscriber(new HttpKernel\EventListener\ResponseListener('UTF-8')); This one was easy too! Let's take another one: do you want out of the box -support for streamed responses? Just subscribe to -``StreamedResponseListener``:: +support for streamed responses? Subscribe to ``StreamedResponseListener``:: $dispatcher->addSubscriber(new HttpKernel\EventListener\StreamedResponseListener()); diff --git a/create_framework/http_kernel_httpkernelinterface.rst b/create_framework/http_kernel_httpkernelinterface.rst index 21b63363e25..1b687623bd1 100644 --- a/create_framework/http_kernel_httpkernelinterface.rst +++ b/create_framework/http_kernel_httpkernelinterface.rst @@ -92,7 +92,7 @@ to cache a response for 10 seconds, use the ``Response::setTtl()`` method:: If, like me, you are running your framework from the command line by simulating requests (``Request::create('/is_leap_year/2012')``), you can - easily debug Response instances by dumping their string representation + debug Response instances by dumping their string representation (``echo $response;``) as it displays all headers as well as the response content. @@ -113,9 +113,9 @@ expiration and the validation models of the HTTP specification. If you are not comfortable with these concepts, read the `HTTP caching`_ chapter of the Symfony documentation. -The Response class contains many other methods that let you configure the -HTTP cache very easily. One of the most powerful is ``setCache()`` as it -abstracts the most frequently used caching strategies into one simple array:: +The Response class contains methods that let you configure the +HTTP cache. One of the most powerful is ``setCache()`` as it +abstracts the most frequently used caching strategies into a single array:: $date = date_create_from_format('Y-m-d H:i:s', '2005-10-15 10:00:00'); @@ -135,7 +135,7 @@ abstracts the most frequently used caching strategies into one simple array:: $response->setSharedMaxAge(10); When using the validation model, the ``isNotModified()`` method allows you to -easily cut on the response time by short-circuiting the response generation as +cut on the response time by short-circuiting the response generation as early as possible:: $response->setETag('whatever_you_compute_as_an_etag'); diff --git a/create_framework/introduction.rst b/create_framework/introduction.rst index d503fed1503..82aaf864ea3 100644 --- a/create_framework/introduction.rst +++ b/create_framework/introduction.rst @@ -38,7 +38,7 @@ you can use as is or as a start for your very own. It will start with a simple framework and more features will be added with time. Eventually, you will have a fully-featured full-stack web framework. -And of course, each step will be the occasion to learn more about some of the +And each step will be the occasion to learn more about some of the Symfony Components. Many modern web frameworks advertize themselves as being MVC frameworks. This diff --git a/create_framework/routing.rst b/create_framework/routing.rst index cafe4beb7ce..75e4c2598a1 100644 --- a/create_framework/routing.rst +++ b/create_framework/routing.rst @@ -189,7 +189,8 @@ more flexible than the previous one. Enjoy! Using the Routing component has one big additional benefit: the ability to generate URLs based on Route definitions. When using both URL matching and URL generation in your code, changing the URL patterns should have no other -impact. Want to know how to use the generator? Insanely easy:: +impact. Want to know how to use the generator? Calling the ``generate`` method +is all it takes:: use Symfony\Component\Routing; diff --git a/create_framework/templating.rst b/create_framework/templating.rst index a00f5b352fb..04751aa164c 100644 --- a/create_framework/templating.rst +++ b/create_framework/templating.rst @@ -69,7 +69,7 @@ the ``_controller`` route attribute:: $response = new Response('An error occurred', 500); } -A route can now be associated with any controller and of course, within a +A route can now be associated with any controller and within a controller, you can still use the ``render_template()`` to render a template:: $routes->add('hello', new Routing\Route('/hello/{name}', array( @@ -138,7 +138,7 @@ application that needs some simple logic. Our application has one page that says whether a given year is a leap year or not. When calling ``/is_leap_year``, you get the answer for the current year, but you can also specify a year like in ``/is_leap_year/2009``. Being generic, the -framework does not need to be modified in any way, just create a new +framework does not need to be modified in any way, create a new ``app.php`` file:: // example.com/src/app.php @@ -169,7 +169,7 @@ framework does not need to be modified in any way, just create a new The ``is_leap_year()`` function returns ``true`` when the given year is a leap year, ``false`` otherwise. If the year is ``null``, the current year is -tested. The controller is simple: it gets the year from the request +tested. The controller does little: it gets the year from the request attributes, pass it to the ``is_leap_year()`` function, and according to the return value it creates a new Response object. diff --git a/create_framework/unit_testing.rst b/create_framework/unit_testing.rst index d3bb5f623a4..79b26b96f3a 100644 --- a/create_framework/unit_testing.rst +++ b/create_framework/unit_testing.rst @@ -121,8 +121,7 @@ This test simulates a request that does not match any route. As such, the ``match()`` method returns a ``ResourceNotFoundException`` exception and we are testing that our framework converts this exception to a 404 response. -Executing this test is as simple as running ``phpunit`` from the -``example.com`` directory: +Execute this test by running ``phpunit`` in the ``example.com`` directory: .. code-block:: terminal @@ -136,7 +135,8 @@ Executing this test is as simple as running ``phpunit`` from the After the test ran, you should see a green bar. If not, you have a bug either in the test or in the framework code! -Adding a unit test for any exception thrown in a controller is just as easy:: +Adding a unit test for any exception thrown in a controller means expecting a +response code of 500:: public function testErrorHandling() { @@ -209,7 +209,7 @@ Alternatively you can output the result directly to the console: $ phpunit --coverage-text -Thanks to the simple object-oriented code that we have written so far, we have +Thanks to the clean object-oriented code that we have written so far, we have been able to write unit-tests to cover all possible use cases of our framework; test doubles ensured that we were actually testing our code and not Symfony code. diff --git a/doctrine/associations.rst b/doctrine/associations.rst index 6e6925f06d3..7d36e662126 100644 --- a/doctrine/associations.rst +++ b/doctrine/associations.rst @@ -13,7 +13,7 @@ How to Work with Doctrine Associations / Relations There are **two** main relationship/association types: ``ManyToOne`` / ``OneToMany`` - The most common relationship, mapped in the database with a simple foreign + The most common relationship, mapped in the database with a foreign key column (e.g. a ``category_id`` column on the ``product`` table). This is actually just *one* association type, but seen from the two different *sides* of the relation. @@ -462,7 +462,7 @@ objects). Remember that you can see all of the queries made during a request via the web debug toolbar. -Of course, if you know up front that you'll need to access both objects, you +If you know up front that you'll need to access both objects, you can avoid the second query by issuing a join in the original query. Add the following method to the ``ProductRepository`` class:: diff --git a/doctrine/dbal.rst b/doctrine/dbal.rst index 5255064db97..e4f253237b2 100644 --- a/doctrine/dbal.rst +++ b/doctrine/dbal.rst @@ -7,7 +7,7 @@ How to Use Doctrine DBAL .. note:: This article is about the Doctrine DBAL. Typically, you'll work with - the higher level Doctrine ORM layer, which simply uses the DBAL behind + the higher level Doctrine ORM layer, which uses the DBAL behind the scenes to actually communicate with the database. To read more about the Doctrine ORM, see ":doc:`/doctrine`". diff --git a/doctrine/event_listeners_subscribers.rst b/doctrine/event_listeners_subscribers.rst index 1c9d2081b46..36802396fae 100644 --- a/doctrine/event_listeners_subscribers.rst +++ b/doctrine/event_listeners_subscribers.rst @@ -23,7 +23,7 @@ The Doctrine website also explains all existing events that can be listened to. Configuring the Listener/Subscriber ----------------------------------- -To register a service to act as an event listener or subscriber you just have +To register a service to act as an event listener or subscriber you have to :doc:`tag ` it with the appropriate name. Depending on your use-case, you can hook a listener into every DBAL connection and ORM entity manager or just into one specific DBAL connection and all the entity diff --git a/doctrine/multiple_entity_managers.rst b/doctrine/multiple_entity_managers.rst index db57d81461c..178b8f61700 100644 --- a/doctrine/multiple_entity_managers.rst +++ b/doctrine/multiple_entity_managers.rst @@ -12,9 +12,9 @@ entity manager that connects to another database might handle the rest. .. note:: - Using multiple entity managers is pretty easy, but more advanced and not - usually required. Be sure you actually need multiple entity managers before - adding in this layer of complexity. + Using multiple entity managers is not complicated to configure, but more + advanced and not usually required. Be sure you actually need multiple + entity managers before adding in this layer of complexity. .. caution:: diff --git a/doctrine/registration_form.rst b/doctrine/registration_form.rst index 229040acac2..12bb6d27e98 100644 --- a/doctrine/registration_form.rst +++ b/doctrine/registration_form.rst @@ -6,8 +6,8 @@ How to Implement a Simple Registration Form =========================================== -Creating a registration form is pretty easy - it *really* means just creating -a form that will update some ``User`` model object (a Doctrine entity in this +Creating a registration form works the same as creating any form. You configure +the form to update some ``User`` model object (a Doctrine entity in this example) and then save it. First, make sure you have all the dependencies you need installed: @@ -376,7 +376,7 @@ return the ``email`` property:: // ... } -Next, just update the ``providers`` section of your ``security.yaml`` file +Next, update the ``providers`` section of your ``security.yaml`` file so that Symfony knows how to load your users via the ``email`` property on login. See :ref:`authenticating-someone-with-a-custom-entity-provider`. diff --git a/email/dev_environment.rst b/email/dev_environment.rst index c71621e7698..8b24d3baf22 100644 --- a/email/dev_environment.rst +++ b/email/dev_environment.rst @@ -7,7 +7,7 @@ How to Work with Emails during Development When developing an application which sends email, you will often not want to actually send the email to the specified recipient during development. If you are using the default Symfony mailer, you -can easily achieve this through configuration settings without having to +can achieve this through configuration settings without having to make any changes to your application's code at all. There are two main choices when it comes to handling email during development: (a) disabling the sending of email altogether or (b) sending all email to a specific diff --git a/email/spool.rst b/email/spool.rst index e3fc88fe8e4..c64ae9bdada 100644 --- a/email/spool.rst +++ b/email/spool.rst @@ -141,7 +141,7 @@ You can also set the time limit in seconds: $ php bin/console swiftmailer:spool:send --time-limit=10 --env=prod -Of course you will not want to run this manually in reality. Instead, the +You will most likely not want to run this command manually in reality. Instead, the console command should be triggered by a cron job or scheduled task and run at a regular interval. diff --git a/event_dispatcher/before_after_filters.rst b/event_dispatcher/before_after_filters.rst index abe5fd6a56d..917020d10c8 100644 --- a/event_dispatcher/before_after_filters.rst +++ b/event_dispatcher/before_after_filters.rst @@ -87,7 +87,7 @@ implement it:: // ... } -A controller that implements this interface simply looks like this:: +A controller that implements this interface looks like this:: namespace App\Controller; @@ -181,7 +181,7 @@ all responses that have passed this token authentication. Another core Symfony event - called ``kernel.response`` (aka ``KernelEvents::RESPONSE``) - is notified on every request, but after the controller returns a Response object. -Creating an "after" listener is as easy as creating a listener class and registering +To create an "after" listener, create a listener class and register it as a service on this event. For example, take the ``TokenSubscriber`` from the previous example and first diff --git a/form/bootstrap4.rst b/form/bootstrap4.rst index 386015744d0..8e34006bae9 100644 --- a/form/bootstrap4.rst +++ b/form/bootstrap4.rst @@ -2,7 +2,7 @@ Bootstrap 4 Form Theme ====================== Symfony provides several ways of integrating Bootstrap into your application. The -most straightforward way is to just add the required ```` and ``