Minor rewords and fixes

Author: javiereguiluz

frontend/custom_version_strategy.rst

@@ -8,16 +8,17 @@ How to Use a Custom Version Strategy for Assets
     The Asset component was introduced in Symfony 2.7.
 
 Asset versioning is a technique that improves the performance of web
-applications by adding a version identifier to the URL of your static assets
-(CSS, JavaScript, images, etc.) When the content of the asset changes, the
-identifier changes and the browser is forced to download it again instead of
-using the cached version.
+applications by adding a version identifier to the URL of the static assets
+(CSS, JavaScript, images, etc.) When the content of the asset changes, its
+identifier is also modified to force the browser download it again instead of
+reusing the cached asset.
 
-Symfony supports the basic asset versioning thanks to the
+Symfony supports asset versioning thanks to the
 :ref:`version <reference-framework-assets-version>` and
 :ref:`version_format <reference-framework-assets-version-format>` configuration
-options. If your application requires a more advanced versioning, you can create
-your own version strategy.
+options. If your application requires a more advanced versioning, such as
+generating the version dynamically based on some external information, you can
+create your own version strategy.
 
 Creating your Own Asset Version Strategy
 ----------------------------------------
@@ -39,7 +40,7 @@ Implement VersionStrategyInterface
 Asset version strategies are PHP classes that implement the
 :class:`Symfony\\Component\\Asset\\VersionStrategy\\VersionStrategyInterface`.
 In this example, the constructor of the class takes as arguments the path to
-the manifest file generated by gulp-buster and the format of the generated
+the manifest file generated by `gulp-buster`_ and the format of the generated
 version string::
 
     // src/AppBundle/Asset/VersionStrategy/GulpBusterVersionStrategy.php