Proofread encore

Author: greg0ire

frontend/encore/cdn.rst

@@ -36,7 +36,7 @@ e.g. ``https://my-cool-app.com.global.prod.fastly.net/dashboard.js``.
     directly from your web server.
 
 You *do* need to make sure that the ``script`` and ``link`` tags you include on your
-pages also uses the CDN. Fortunately, the ``manifest.json`` paths are updated to
+pages also use the CDN. Fortunately, the ``manifest.json`` paths are updated to
 point to the CDN. In Symfony, as long as you've configured
 :doc:`Asset Versioning </frontend/encore/versioning>`, you're done! The ``manifest.json``
 file includes the full CDN URL:

frontend/encore/css-preprocessors.rst

@@ -1,5 +1,5 @@
-CSS Preprocessors: Sass, LESS, etc
-==================================
+CSS Preprocessors: Sass, LESS, etc.
+===================================
 
 Using Sass
 ----------
@@ -22,7 +22,7 @@ And enable it in ``webpack.config.js``:
         .enableSassLoader()
     ;
 
-That's it! All files ending in ``.sass`` or ``.scss`` will be processed.
+That's it! All files ending in ``.sass`` or ``.scss`` will be pre-processed.
 
 Using LESS
 ----------

frontend/encore/dev-server.rst

@@ -1,7 +1,7 @@
 Using webpack-dev-server and HMR
 ================================
 
-While developing, instead of using ``encore dev --watch``, you can instead use the
+While developing, instead of using ``encore dev --watch``, you can use the
 `webpack-dev-server`_:
 
 .. code-block:: terminal

frontend/encore/page-specific-assets.rst

@@ -28,7 +28,7 @@ tag for ``checkout.css`` if you import any CSS).
 Multiple Entries Per Page?
 --------------------------
 
-Typically, you should include only *one* entry JavaScript per page. This means
+Typically, you should include only *one* JavaScript entry per page. This means
 the checkout page will include ``checkout.js``, but will *not* include the
 ``app.js`` that's used on the other pages. Think of the checkout page as its
 own "app", where ``checkout.js`` includes all the functionality you need.

frontend/encore/server-data.rst

@@ -26,7 +26,7 @@ Fetch this in JavaScript:
 There is no size limit for the value of the ``data-`` attributes, so you can
 store any content. In Twig, use the ``html_attr`` escaping strategy to avoid messing
 with HTML attributes. For example, if your ``User`` object has some ``getProfileData()``
-method that returns an array, you could:
+method that returns an array, you could do the following:
 
 .. code-block:: twig
 

frontend/encore/simple-example.rst

@@ -22,7 +22,7 @@ Inside, use Encore to help generate your Webpack configuration.
     var Encore = require('@symfony/webpack-encore');
 
     Encore
-        // directory where should all compiled assets will be stored
+        // directory where all compiled assets will be stored
         .setOutputPath('web/build/')
 
         // what's the public path to this directory (relative to your project's document root dir)
@@ -40,7 +40,7 @@ Inside, use Encore to help generate your Webpack configuration.
         // allow sass/scss files to be processed
         .enableSassLoader()
 
-        // allows legacy applications to use $/jQuery as a global variable
+        // allow legacy applications to use $/jQuery as a global variable
         .autoProvidejQuery()
 
         .enableSourceMaps(!Encore.isProduction())
@@ -99,8 +99,8 @@ In Symfony, use the ``asset()`` helper:
 Requiring JavaScript Modules
 ----------------------------
 
-Webpack is module bundler... which means that you can ``require`` other JavaScript
-files. First, create a file that exports a function:
+Webpack is a module bundler... which means that you can ``require`` other
+JavaScript files. First, create a file that exports a function:
 
 .. code-block:: javascript
 

frontend/encore/sourcemaps.rst

@@ -1,7 +1,7 @@
 Enabling Source Maps
 ====================
 
-`Source maps`_ allow browsers to access to the original code related to some
+`Source maps`_ allow browsers to access the original code related to some
 asset (e.g. the Sass code that was compiled to CSS or the TypeScript code that
 was compiled to JavaScript). Source maps are useful for debugging purposes but
 unnecessary when executing the application in production.

frontend/encore/versioning.rst

@@ -8,7 +8,7 @@ By calling ``enableVersioning()``, each filename will now include a hash that
 changes whenever the *contents* of that file change (e.g. ``app.123abc.js``
 instead of ``app.js``). This allows you to use aggressive caching strategies
 (e.g. a far future ``Expires``) because, whenever a file change, its hash will change,
-invalidating any existing cache:
+ignoring any existing cache:
 
 .. code-block:: diff