Approved Ralph's review.

tkolcon · ralph-lange · ralph-lange · commit 7a88ccdb2111 · 2020-04-29T08:04:22.000+02:00
Co-Authored-By: Ralph Lange &lt;ralph-lange@users.noreply.github.com&gt;
diff --git a/_docs/tutorials/advanced/nuttx/debugging/index.md b/_docs/tutorials/advanced/nuttx/debugging/index.md
@@ -4,7 +4,7 @@ permalink: /docs/tutorials/advanced/nuttx/debugging/
 author: Ingo Lütkebohle (merged by Tomasz Kołcon)
 ---
 
-This tutorial consists of 2 parts: debugging a NuttX target with GDB and OpenOCD and debugging with Visual Studio Code. The first one describes tools installation and debugging via command line. The second focuses on the description of debugging using the modern IDE.
+This tutorial consists of two parts: First, debugging a NuttX target with GDB and OpenOCD. This part covers tool installation and debugging via command line. Second, debugging with Visual Studio Code, i.e. using a modern IDE.
 
 ## Debugging a NuttX target with GDB and OpenOCD
 
@@ -236,4 +236,4 @@ Extract the SVD and then add an `svdFile` attribute to the launch configuration.
 Run the debugger again, and your window should look as follows:
 ![](/img/tutorials/debug-vscode-svd.png)
 
-Voilà! The `Cortex Peripherals` is populated with everything that the STM32F407 MCU has to offer. Please note that not all of these peripherals might actually be connected on the board. However, those that are, and that are used in your application, can easily be investigated like this.
+Voilà! The `Cortex Peripherals` is populated with everything that the STM32F407 MCU has to offer. Please note that not all of these peripherals might actually be connected on the board. However, those that are, and that are used in your application, can easily be investigated like this.
