applied comments

OskarStark · OskarStark · commit c063b0e03df1 · 2019-02-25T20:56:43.000+01:00
diff --git a/best_practices/controllers.rst b/best_practices/controllers.rst
@@ -208,8 +208,9 @@ flexible::
         // ...
     }
 
-The point is this: the ParamConverter shortcut is great for simple situations.
-But you shouldn't forget that querying for entities directly is not to difficult.
+The point is this: the ParamConverter shortcut is great for most situations.
+However, there is nothing wrong with querying for entities directly if the
+ParamConverter would get complicated.
 
 Pre and Post Hooks
 ------------------
diff --git a/best_practices/security.rst b/best_practices/security.rst
@@ -166,7 +166,7 @@ need to repeat the expression code using Twig syntax:
         <a href=""> ... </a>
     {% endif %}
 
-A better solution - if your logic is simple enough - is to add a new method
+A good solution - if your logic is simple enough - can be to add a new method
 to the ``Post`` entity that checks if a given user is its author::
 
     // src/AppBundle/Entity/Post.php
diff --git a/create_framework/http_foundation.rst b/create_framework/http_foundation.rst
@@ -52,7 +52,7 @@ As you can see for yourself, the simple code we had written first is not that
 simple anymore if we want to avoid PHP warnings/notices and make the code
 more secure.
 
-Beyond security, this code is quite hard to test. Even if there is not
+Beyond security, this code can be complex to test. Even if there is not
 much to test, it strikes me that writing unit tests for the simplest possible
 snippet of PHP code is not natural and feels ugly. Here is a tentative PHPUnit
 unit test for the above code::
diff --git a/email/testing.rst b/email/testing.rst
@@ -10,7 +10,7 @@ SwiftmailerBundle, which leverages the power of the `Swift Mailer`_ library.
 To functionally test that an email was sent, and even assert the email subject,
 content or any other headers, you can use :doc:`the Symfony Profiler </profiler>`.
 
-Start with an controller action that sends an email::
+Start with a controller action that sends an email::
 
     public function sendEmailAction($name, \Swift_Mailer $mailer)
     {
diff --git a/form/direct_submit.rst b/form/direct_submit.rst
@@ -4,7 +4,7 @@
 How to Use the submit() Function to Handle Form Submissions
 ===========================================================
 
-Handle the form submission via the ``handleRequest()`` method::
+Handle the form submission with the ``handleRequest()`` method::
 
     use Symfony\Component\HttpFoundation\Request;
     // ...
diff --git a/forms.rst b/forms.rst
@@ -10,8 +10,8 @@ Forms
     Do you prefer video tutorials? Check out the `Symfony Forms screencast series`_.
 
 Dealing with HTML forms is one of the most common - and challenging - tasks for
-a web developer. Symfony integrates a Form component that makes dealing with
-forms straightforward. In this article, you'll build a complex form from the ground up,
+a web developer. Symfony integrates a Form component that helps you dealing
+with forms. In this article, you'll build a complex form from the ground up,
 learning the most important features of the form library along the way.
 
 .. note::

Original file line number	Diff line number	Diff line change
@@ -10,7 +10,7 @@ SwiftmailerBundle, which leverages the power of the `Swift Mailer`_ library.
`10`	`10`	`To functionally test that an email was sent, and even assert the email subject,`
`11`	`11`	content or any other headers, you can use :doc:`the Symfony Profiler </profiler>`.
`12`	`12`
`13`		`-Start with an controller action that sends an email::`
	`13`	`+Start with a controller action that sends an email::`
`14`	`14`
`15`	`15`	`public function sendEmailAction($name, \Swift_Mailer $mailer)`
`16`	`16`	`{`