Merge branch '3.4' into 4.3

* 3.4:
  Renamed the security:check command as check:security

Author: javiereguiluz

contributing/code/security.rst

@@ -38,7 +38,8 @@ confirmed, the core team works on a solution following these steps:
 #. Publish the post on the official Symfony `blog`_ (it must also be added to
    the "`Security Advisories`_" category);
 #. Update the public `security advisories database`_ maintained by the
-   FriendsOfPHP organization and which is used by the ``security:check`` command.
+   FriendsOfPHP organization and which is used by
+   :doc:`the check:security command </security/security_checker>`.
 
 .. note::
 
@@ -169,7 +170,7 @@ Security Advisories
 .. tip::
 
     You can check your Symfony application for known security vulnerabilities
-    using :ref:`the security:check command <security-checker>`.
+    using :ref:`the check:security command <security-checker>`.
 
 Check the `Security Advisories`_ blog category for a list of all security
 vulnerabilities that were fixed in Symfony releases, starting from Symfony

setup.rst

@@ -180,7 +180,7 @@ vulnerability:
 
 .. code-block:: terminal
 
-    $ symfony security:check
+    $ symfony check:security
 
 A good security practice is to execute this command regularly to be able to
 update or replace compromised dependencies as soon as possible. The security
@@ -189,7 +189,7 @@ so your ``composer.lock`` file is not sent on the network.
 
 .. tip::
 
-    The ``security:check`` command terminates with a non-zero exit code if
+    The ``check:security`` command terminates with a non-zero exit code if
     any of your dependencies is affected by a known security vulnerability.
     This way you can add it to your project build process and your continuous
     integration workflows to make them fail when there are vulnerabilities.