diff --git a/Documentation/quickstart/debugging.rst b/Documentation/quickstart/debugging.rst
index cc3489eca8..afa897bdae 100644
--- a/Documentation/quickstart/debugging.rst
+++ b/Documentation/quickstart/debugging.rst
@@ -59,7 +59,7 @@ start ``openocd`` with the following command:
 
 .. code-block:: console
 
-  $ openocd -f interface/st-link-v2.cfg -f target/stm32f1x.cfg
+  $ openocd -f interface/stlink-v2.cfg -f target/stm32f1x.cfg
 
 This will start a ``gdb`` server. Then, start ``gdb`` with:
 
@@ -138,7 +138,7 @@ Finally, to enable NuttX integration, you need to supply an additional ``openocd
 
 .. code-block:: console
 
-  $ openocd -f interface/st-link-v2.cfg -f target/stm32f1x.cfg -c '$_TARGETNAME configure -rtos nuttx'
+  $ openocd -f interface/stlink-v2.cfg -f target/stm32f1x.cfg -c '$_TARGETNAME configure -rtos nuttx'
   
 Since ``openocd`` also needs to know the memory layout of certain datastructures, you need to have ``gdb``
 run the following commands once the ``nuttx`` binary is loaded:
diff --git a/Documentation/quickstart/running.rst b/Documentation/quickstart/running.rst
index 6deb17df24..34b9d81a86 100644
--- a/Documentation/quickstart/running.rst
+++ b/Documentation/quickstart/running.rst
@@ -52,7 +52,7 @@ Now, to flash the binary to your board, connect the USB cable and do:
 .. code-block:: console
 
   $ cd nuttx/
-  $ openocd -f interface/st-link-v2.cfg -f target/stm32f1x.cfg -c 'init' \
+  $ openocd -f interface/stlink-v2.cfg -f target/stm32f1x.cfg -c 'init' \
     -c 'program nuttx/nuttx.bin verify reset' -c 'shutdown'
 
 Access NuttShell