symfony
diff --git a/‎assetic/asset_management.rst
Copy file name to clipboardExpand all lines: assetic/asset_management.rst
+5-4Lines changed: 5 additions & 4 deletions b/‎assetic/asset_management.rst
Copy file name to clipboardExpand all lines: assetic/asset_management.rst
+5-4Lines changed: 5 additions & 4 deletions
diff --git a/‎frontend/custom_version_strategy.rst
Copy file name to clipboardExpand all lines: frontend/custom_version_strategy.rst
+11-7Lines changed: 11 additions & 7 deletions b/‎frontend/custom_version_strategy.rst
Copy file name to clipboardExpand all lines: frontend/custom_version_strategy.rst
+11-7Lines changed: 11 additions & 7 deletions
diff --git a/‎reference/twig_reference.rst
Copy file name to clipboardExpand all lines: reference/twig_reference.rst
+4-2Lines changed: 4 additions & 2 deletions b/‎reference/twig_reference.rst
Copy file name to clipboardExpand all lines: reference/twig_reference.rst
+4-2Lines changed: 4 additions & 2 deletions
diff --git a/‎templating.rst
Copy file name to clipboardExpand all lines: templating.rst
+6-5Lines changed: 6 additions & 5 deletions b/‎templating.rst
Copy file name to clipboardExpand all lines: templating.rst
+6-5Lines changed: 6 additions & 5 deletions
@@ -552,10 +552,11 @@ done from the template and is relative to the public document root:
 
 .. note::
 
-    Symfony also contains a method for cache *busting*, where the final URL
-    generated by Assetic contains a query parameter that can be incremented
-    via configuration on each deployment. For more information, see the
-    :ref:`reference-framework-assets-version` configuration option.
+    Symfony provides various cache busting implementations via the
+    :ref:`version <reference-framework-assets-version>`,
+    :ref:`version_format <reference-assets-version-format>`, and
+    :ref:`json_manifest_path <reference-assets-json-manifest-path>`
+    configuration options.
 
 .. _assetic-dumping:
 
 
@@ -10,13 +10,17 @@ applications by adding a version identifier to the URL of the static assets
 identifier is also modified to force the browser to download it again instead of
 reusing the cached asset.
 
-Symfony supports asset versioning thanks to the
-:ref:`version <reference-framework-assets-version>`,
-:ref:`version_format <reference-assets-version-format>`, and
-:ref:`json_manifest_path <reference-assets-json-manifest-path>` configuration
-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.
+If your application requires advanced versioning, such as generating the
+version dynamically based on some external information, you can create your
+own version strategy.
+
+.. note::
+
+    Symfony provides various cache busting implementations via the
+    :ref:`version <reference-framework-assets-version>`,
+    :ref:`version_format <reference-assets-version-format>`, and
+    :ref:`json_manifest_path <reference-assets-json-manifest-path>`
+    configuration options.
 
 Creating your Own Asset Version Strategy
 ----------------------------------------
 
@@ -123,8 +123,10 @@ asset
 
 Returns a public path to ``path``, which takes into account the base path
 set for the package and the URL path. More information in
-:ref:`templating-assets`. For asset versioning, see
-:ref:`reference-framework-assets-version`.
+:ref:`templating-assets`. Symfony provides various cache busting
+implementations via the :ref:`reference-framework-assets-version`,
+:ref:`reference-assets-version-strategy`, and
+:ref:`reference-assets-json-manifest-path` configuration options.
 
 asset_version
 ~~~~~~~~~~~~~~
 
@@ -771,11 +771,12 @@ should render with the subdirectory (e.g. ``/my_app/images/logo.png``). The
 ``asset()`` function takes care of this by determining how your application is
 being used and generating the correct paths accordingly.
 
-Additionally, if you use the ``asset()`` function, Symfony can automatically
-append a query string to your asset, in order to guarantee that updated static
-assets won't be loaded from cache after being deployed. For example, ``/images/logo.png`` might
-look like ``/images/logo.png?v2``. For more information, see the :ref:`reference-framework-assets-version`
-configuration option.
+.. tip::
+
+    The ``asset()`` function supports various cache busting techniques via the
+    :ref:`version <reference-framework-assets-version>`,
+    :ref:`version_format <reference-assets-version-format>`, and
+    :ref:`json_manifest_path <reference-assets-json-manifest-path>` configuration options.
 
 If you need absolute URLs for assets, use the ``absolute_url()`` Twig function
 as follows: