diff --git a/doc/devdocs/modules/launcher/debugging.md b/doc/devdocs/modules/launcher/debugging.md
index 9e716ffbae..bf1606b9af 100644
--- a/doc/devdocs/modules/launcher/debugging.md
+++ b/doc/devdocs/modules/launcher/debugging.md
@@ -11,7 +11,7 @@ This approach is used to test UI, plugins, and core `PowerToys Run` functionalit
 2. Press `F5` to start debugging.
 
 ## Debugging with runner
-This approach can be used to test UI, plugins, core `PowerToys Run` functionality and `PowerToys Run` settings. This approach **cannot** be used to debugging functions that execute on starting `launcher.exe` process. This requires building runner along with all the other modules on first compile, making it slower than `Direct debugging` approach. The subsequent compilations should be fast.
+This approach can be used to test UI, plugins, core `PowerToys Run` functionality and `PowerToys Run` settings. This approach **cannot** be used to debug functions that execute on starting `launcher.exe` process. This requires building runner along with all the other modules on first compile, making it slower than `Direct debugging` approach. The subsequent compilations should be fast.
 1. Right-click on `runner` and select `Set as startup Project`. 
 2. Press `F5` to start debugging.
 3. Attach debugger to `launcher.exe` process.