symfony
diff --git a/‎components/console/introduction.rst
Lines changed: 17 additions & 5 deletions b/‎components/console/introduction.rst
Lines changed: 17 additions & 5 deletions
diff --git a/‎cookbook/console/console_command.rst
Lines changed: 2 additions & 30 deletions b/‎cookbook/console/console_command.rst
Lines changed: 2 additions & 30 deletions
@@ -449,6 +449,8 @@ method::
     You can also test a whole console application by using
     :class:`Symfony\\Component\\Console\\Tester\\ApplicationTester`.
 
+.. _calling-existing-command:
+
 Calling an Existing Command
 ---------------------------
 
@@ -478,16 +480,26 @@ Calling a command from another one is straightforward::
     }
 
 First, you :method:`Symfony\\Component\\Console\\Application::find` the
-command you want to execute by passing the command name.
-
-Then, you need to create a new
-:class:`Symfony\\Component\\Console\\Input\\ArrayInput` with the arguments and
-options you want to pass to the command.
+command you want to execute by passing the command name. Then, you need to create
+a new :class:`Symfony\\Component\\Console\\Input\\ArrayInput` with the arguments
+and options you want to pass to the command.
 
 Eventually, calling the ``run()`` method actually executes the command and
 returns the returned code from the command (return value from command's
 ``execute()`` method).
 
+.. tip::
+
+    If you want to suppress the output of the executed command, pass a :class:`Symfony\\Component\\Console\\Output\\NullOutput`
+    as the second argument to ``$command->execute()``.
+
+.. caution::
+
+    Note that all the commands will run in the same process, and some of Symfony's
+    built-in commands may not work well this way. For instance, ``cache:clear``
+    and ``cache:warmup`` commands change some class definitions, so running something
+    after them is likely to break.
+
 .. note::
 
     Most of the time, calling a command from code that is not executed on the
 
@@ -153,36 +153,8 @@ see :doc:`/cookbook/service_container/scopes`.
 Invoking Other Commands
 -----------------------
 
-If you need to implement a command that runs other dependent commands, you can fetch 
-these commands using the :class:`Symfony\\Component\\Console\\Application <Symfony\\Component\\Console\\Application>`'s ``find`` method. 
-
-Also note that you'll have to pass :class:`Symfony\\Component\\Console\\Input\\InputInterface` and :class:`Symfony\\Component\\Console\\Output\\OutputInterface` 
-as arguments to the command's ``execute`` method. This can be easily implemented 
-with :class:`Symfony\\Component\\Console\\Input\\ArrayInput`::
-
-    protected function execute(InputInterface $input, OutputInterface $output)
-    {
-        $command = $this->getApplication()->find('some:command');
-        $command->execute(
-            new ArrayInput(array(
-                'foo' => 'foo', 
-                '--bar' => 'foobar',
-            )), 
-            $output
-        );
-    }
-
-.. tip::
-
-    If you want to suppress the output of the executed command, pass a :class:`Symfony\\Component\\Console\\Output\\NullOutput`
-    as the second argument to ``$command->execute()``.
-
-.. caution::
-
-    Note that all these commands will run in the same process, and some of Symfony's 
-    built-in commands may not work well this way. For instance, ``cache:clear`` and ``cache:warmup`` 
-    commands change some class definitions, so running something 
-    after them is likely to break.
+See :ref:`calling-existing-command` if you need to implement a command that runs
+other dependent commands.
 
 Testing Commands
 ----------------