diff --git a/documentation/debugging.md b/documentation/debugging.md
index 8e46f991b..7cecb8542 100644
--- a/documentation/debugging.md
+++ b/documentation/debugging.md
@@ -3,9 +3,9 @@ Debugging with Smack
 
 [Back](index.html)
 
-Smack includes two built-in debugging consoles that will let you track all XML
-traffic between the client and server. A lite debugger which is part of the
-`smack-core.jar` and an enhanced debugger contained in `smack-debug.jar`.
+Smack includes two built-in debugging consoles that will let you track
+all XML traffic between the client and server. A lite debugger and an
+enhanced debugger contained in `smack-debug.jar`, and a console debugger in `smack-core.jar`.
 
 Debugging mode can be enabled in two different ways:
 
@@ -29,9 +29,9 @@ Smack uses the following logic to decide the debugger console to use:
 
 `java -Dsmack.debuggerClass=my.company.com.MyDebugger SomeApp `
 
-  2. If step 1 fails then Smack will try to use the enhanced debugger. The file `smackx-debug.jar` contains the enhanced debugger. Therefore you will need to place the jar file in the classpath. For situations where space is an issue you may want to only deploy `smack-core.jar` in which case the enhanced debugger won't be available.
+  2. If step 1 fails then Smack will try to use the enhanced debugger. The file `smackx-debug.jar` contains the enhanced debugger. Therefore you will need to place the jar file in the classpath. For situations where space is an issue you may want to only deploy `smack-core.jar` in which case the enhanced and lite debugger won't be available, but only the console debugger.
 
-  3. The last option if the previous two steps fail is to use the lite debugger. The lite debugger is a very good option for situations where you need to have low memory footprint.
+  3. The last option if the previous two steps fail is to use the console debugger. The console debugger is a very good option for situations where you need to have low memory footprint.
 
 Enhanced Debugger
 -----------------