Reword

Author: javiereguiluz

components/dependency_injection/compilation.rst

@@ -468,13 +468,13 @@ serves at dumping the compiled container::
         file_put_contents($file, $dumper->dump());
     }
 
-
 .. tip::
 
-    Call to `file_put_contents` is not atomic. When generating container in
-    a production  environment with multiple concurrent requests, use `dumpFile`
-    from `component-filesystem` instead. This generates file in tmp and moves it
-    to its destination only once it's fully written to.
+    The ``file_put_contents()`` function is not atomic. That could cause issues
+    in a production environment with multiple concurrent requests. Instead, use
+    the :ref:`dumpFile() method <filesystem-dumpfile>` from Symfony Filesystem
+    component or other methods provided by Symfony (e.g. ``$containerConfigCache->write()``)
+    which are atomic.
 
 ``ProjectServiceContainer`` is the default name given to the dumped container
 class. However, you can change this with the ``class`` option when you
@@ -567,11 +567,6 @@ for these resources and use them as metadata for the cache::
 
     require_once $file;
     $container = new MyCachedContainer();
-    
-.. note::
-
-    Using `$containerConfigCache->write` also makes sure that
-    the file write operation is atomic.
 
 Now the cached dumped container is used regardless of whether debug mode
 is on or not. The difference is that the ``ConfigCache`` is set to debug

components/filesystem.rst

@@ -291,6 +291,8 @@ exception on failure::
 
     The option to set a suffix in  ``tempnam()`` was introduced in Symfony 5.1.
 
+.. _filesystem-dumpfile:
+
 ``dumpFile``
 ~~~~~~~~~~~~