applied comments

configuration/micro_kernel_trait.rst

@@ -350,4 +350,4 @@ Then see webpage in browser:
 
 Hey, that looks a lot like a *traditional* Symfony application! You're right: the
 ``MicroKernelTrait`` *is* still Symfony: but you can control your structure and
-features in a lighter way.
+features with less boilerplate configuration and code.

form/events.rst

@@ -11,7 +11,8 @@ Using form events, you may modify information or fields at different steps
 of the workflow: from the population of the form to the submission of the
 data from the request.
 
-Registering an event listener is straightforward using the Form component.
+By utilizing the Symfony event system, event listeners can be registered to
+your forms.
 
 For example, if you wish to register a function to the
 ``FormEvents::PRE_SUBMIT`` event, the following code lets you add a field,

frontend.rst

@@ -28,7 +28,8 @@ to solve the most common Webpack use cases.
 .. tip::
 
     Encore is made by `Symfony`_ and works *beautifully* in Symfony applications.
-    But it can be used in any application or language!
+    But it can be used in any PHP application and even with other server side
+    programming languages!
 
 .. _encore-toc:
 

frontend/encore/cdn.rst

@@ -1,7 +1,8 @@
 Using a CDN
 ===========
 
-When deploying to a CDN, your uploaded built files need to be configured in Encore:
+Are you deploying to a CDN? That's awesome :) Once you've made sure that your
+built files are uploaded to the CDN, configure it in Encore:
 
 .. code-block:: diff
 

reference/constraints/Callback.rst

@@ -3,9 +3,9 @@ Callback
 
 The purpose of the Callback constraint is to create completely custom
 validation rules and to assign any validation errors to specific fields
-on your object. If you're using validation with forms, this means that you
-can make these custom errors display next to a specific field, instead at
-the top of your form.
+on your object. If you're using validation with forms, this means that
+instead of displaying custom errors at the top of the form, you can
+display them next to the field they apply to.
 
 This process works by specifying one or more *callback* methods, each of
 which will be called during the validation process. Each of those methods

reference/forms/types/dateinterval.rst

@@ -56,7 +56,7 @@ or an array (see `input`_).
 Basic Usage
 -----------
 
-The most important options are `input`_ and `widget`_.
+This field type is highly configurable. The most important options are `input`_ and `widget`_.
 
 You can configure *a lot* of different options, including exactly *which* range
 options to show (e.g. don't show "months", but *do* show "days")::

routing/optional_placeholders.rst

@@ -121,9 +121,9 @@ be available inside your controller. Its value can be used to determine which
 set of blog posts to display for the given page.
 
 But hold on! Since placeholders are required by default, this route will
-no longer match on ``/blog``. Instead, to see page 1 of the blog, you'd
-need to use the URL ``/blog/1``! Since that's no way for a rich web app
-to behave, modify the route to make the ``{page}`` parameter optional.
+no longer match on ``/blog`` alone. Instead, to see page 1 of the blog,
+you'd need to use the URL ``/blog/1``! Since that's no way for a rich web
+app to behave, modify the route to make the ``{page}`` parameter optional.
 This is done by including it in the ``defaults`` collection:
 
 .. configuration-block::