diff --git a/_build/redirection_map b/_build/redirection_map
index 501f6c69d29..ab541e427b7 100644
--- a/_build/redirection_map
+++ b/_build/redirection_map
@@ -127,7 +127,8 @@
 /cookbook/controller/index /controller
 /cookbook/controller/service /controller/service
 /cookbook/controller/upload_file /controller/upload_file
-/cookbook/debugging /debug/debugging
+/cookbook/debugging /
+/debug/debugging /
 /cookbook/deployment/azure-website /cookbook/azure-website
 /cookbook/deployment/fortrabbit /deployment/fortrabbit
 /cookbook/deployment/heroku /deployment/heroku
diff --git a/configuration/front_controllers_and_kernel.rst b/configuration/front_controllers_and_kernel.rst
index da6c6c781af..54cab74072a 100644
--- a/configuration/front_controllers_and_kernel.rst
+++ b/configuration/front_controllers_and_kernel.rst
@@ -45,7 +45,6 @@ to `decorate`_ the kernel with additional features. Examples include:
 * Configuring the autoloader or adding additional autoloading mechanisms;
 * Adding HTTP level caching by wrapping the kernel with an instance of
   :ref:`AppCache <symfony-gateway-cache>`;
-* Enabling (or skipping) the :doc:`ClassCache </debug/debugging>`;
 * Enabling the :doc:`Debug Component </components/debug>`.
 
 The front controller can be chosen by requesting URLs like:
diff --git a/debug.rst b/debug.rst
deleted file mode 100644
index 49d3074b799..00000000000
--- a/debug.rst
+++ /dev/null
@@ -1,8 +0,0 @@
-Debugging
-=========
-
-.. toctree::
-    :maxdepth: 1
-    :glob:
-
-    debug/*
diff --git a/debug/debugging.rst b/debug/debugging.rst
deleted file mode 100644
index 26f6a2da89e..00000000000
--- a/debug/debugging.rst
+++ /dev/null
@@ -1,53 +0,0 @@
-.. index::
-   single: Debugging
-
-How to Optimize your Development Environment for Debugging
-==========================================================
-
-When you work on a Symfony project on your local machine, you should use the
-``dev`` environment (``app_dev.php`` front controller). This environment
-configuration is optimized for two main purposes:
-
-* Give the developer accurate feedback whenever something goes wrong (web
-  debug toolbar, nice exception pages, profiler, ...);
-
-* Be as similar as possible as the production environment to avoid problems
-  when deploying the project.
-
-Useful Debugging Commands
--------------------------
-
-When developing a large application, it can be hard to keep track of all the
-different services, routes and translations. Luckily, Symfony has some commands
-that can help you visualize and find the information.
-
-``about``
-    Shows information about the current project, such as the Symfony version,
-    the Kernel and PHP.
-
-``debug:container``
-    Displays information about the contents of the Symfony container for all public
-    services. To find only those matching a name, append the name as an argument.
-
-``debug:config``
-    Shows all configured bundles, their class and their alias.
-    
-``debug:form``
-    Displays information about form types and their options.
-
-``debug:event-dispatcher``
-    Displays information about all the registered listeners in the event dispatcher.
-
-``debug:router``
-    Displays information about all configured routes in the application as a
-    table with the name, method, scheme, host and path for each route.
-
-``debug:translation <locale>``
-    Shows a table of the translation key, the domain, the translation and the
-    fallback translation for all known messages, if translations exist for
-    the given locale.
-
-.. tip::
-
-    When in doubt how to use a console command, open the help section by
-    appending the ``--help`` option.
diff --git a/index.rst b/index.rst
index 2c4379f1e0e..5d86033a0cb 100644
--- a/index.rst
+++ b/index.rst
@@ -40,7 +40,6 @@ Topics
     bundles
     console
     doctrine
-    debug
     deployment
     email
     event_dispatcher