apply review suggestions

Author: Hannes7eicher

content/hardware/03.nano/boards/nano-esp32/tutorials/debugging/debugging.md

@@ -1,13 +1,13 @@
 ---
 title: Debugging with the Nano ESP32
-description: Get started with debugging using the Arduino Nano ESP32 with the IDE 2.
+description: Get started with debugging the Arduino Nano ESP32 with the IDE 2.
 author: Hannes Siebeneicher
 hardware:
   - hardware/03.nano/boards/nano-esp32
 tags: [ESP32, Debugging, IDE]
 ---
 
-Debugging is a crucial step especially when developing more complex projects. But even for beginners, it can be worth looking into as it gives you a lot more insights on what your code does at a specific time. 
+Debugging skills are valuable not only for tackling complex projects but also for beginners and those working on intermediate-level projects, as they offer valuable insights into the specific behavior of your code.
 
 ## What Is Debugging?
 
@@ -24,12 +24,12 @@ Debugging is an essential skill for anyone working with technology, whether you'
 ## Software & Hardware Needed
 
 - [Arduino Nano ESP32](https://store.arduino.cc/nano-esp32)
-- [Arduino IDE](/software/ide-v2)
-- [Arduino Nano ESP32 Core](https://github.com/arduino/arduino-esp32) (2.0.12 or newer)
+- [Arduino IDE](https://www.arduino.cc/en/software)
+- [Arduino ESP32 Core](https://github.com/arduino/arduino-esp32) installed (2.0.12 or newer)
 
 ## IDE Setup
 
-In order to use the debugging feature on the Nano ESP32 you will need to download and install the IDE 2.2.0 or newer. After you install it, you have to configure the IDE as follows:
+To use the debugging feature on the Nano ESP32, you need to have the IDE 2.2.0 or a newer version installed. After you install it, you have to configure the IDE as follows:
 
 -  **Tools** > **USB Mode** > **Debug mode (Hardware CDC)**
 
@@ -49,15 +49,15 @@ If this is your first time debugging your code we recommend starting with the cl
 
 Before starting a debug session make sure to always do one of the following:
 
-- Either connect a jumper cable between the **GND** and the **B1** pins and press the reset button **once**. The RGB LED will turn on with a green or blue color. Inside **Tools**, the board will be shown as a random ESP32 board. 
+- Either connect a jumper cable between the **GND** and the **B1** pins, press the reset button **once**, and remove the jumper cable. The RGB LED will turn on with a green or blue color. Inside **Tools**, the board will be shown as a random ESP32 board. 
 
 ***This is because in this mode all ESP32 chips share the same identifier assigned to USB devices, therefore the IDE selects a random ESP32 board.***
 
 Continue to select **Tools** > **Board** > **Arduino Nano ESP32** as well as the correct **Port**.
 
 After that select **Sketch** > **Upload Using Programmer**.
 
-- Or double tap the reset button. You will see the RGB LED fading slowly which means you correctly entered the recovery / Device Firmware Update (DFU) mode. You should see two ports in the drop-down menu, one showing a USB symbol and another one showing a cube.
+- Or double-tap the reset button. You will see the RGB LED fading slowly which means you correctly entered the recovery / Device Firmware Update (DFU) mode. You should see two ports in the drop-down menu, one showing a USB symbol and another one showing a cube.
 
 ![DFU Mode](./assets/dfuMode.png)
 
@@ -67,9 +67,9 @@ Finally, after completing all steps above the last step is to start the debuggin
 
 ![Start Debugging](./assets/startDebugging.png)
 
-***Note: During the upload you will see a debug_custom.json being created at the top of the IDE. If you want to debug using another board it's important that you delete this file otherwise the IDE will use the wrong debugger and fail. You can find the file inside your sketch folder at ~\Documents\Arduino\sketches\"Your Sketch".***
+***Note: During the upload you will see a debug_custom.json appear in the file view. If you want to debug using another board it's important that you delete this file otherwise the IDE will use the wrong debugger and fail. You can find the file inside your sketch folder, typically at `~/documents/Arduino/<yoursketch>`***
 
-After starting the debugging session you will have to press the continue button **several times** until you reach you main sketch and the breakpoints you set. This is due to how the recovery system works and is **expected behavior**.
+After starting the debugging session you have to press the continue button **several times** until you reach your main sketch and the breakpoints you set. This is due to how the recovery system works is expected behavior.
 
 ![Continue Button](./assets/continueBtn.png)
 
@@ -79,14 +79,13 @@ Debug-enabled sketches will only accept updates with the above instructions. To
 
 Then repeat the steps described above:
 
-- Either connect a jumper cable between the **GND** and the **B1** pins press the reset button **once** and upload using programmer 
+- Either connect a jumper cable between the **GND** and the **B1** pins press the reset button **once** and upload using programmer.
 
-- Or **double tap** the reset button to enter **DFU mode** and perform a normal upload using the upload button.
-
-## Learn More
-
-To learn more about how to debug using the IDE check out [Debugging with the Arduino IDE 2](/software/ide-v2/tutorials/ide-v2-debugger)
+- Or **double-tap** the reset button to enter **DFU mode** and perform a normal upload using the upload button.
 
 ## Summary
 
-In this article we covered the basic steps for getting started with debugging using the Arduino Nano ESP32 and the IDE 2.
+In this article we covered the basic steps for debugging the Arduino Nano ESP32 using the Arduino IDE. We have learned how to select the debug mode, how to place the board in the right mode, and how to test out the Arduino IDE's debugging features.
+
+## Learn More
+This article only covers how to configure the Nano ESP32 for debugging, and how to get things working. To learn more about how to use the debugging features in the IDE, see the [Debugging with the Arduino IDE 2](/software/ide-v2/tutorials/ide-v2-debugger) article, which covers things in more detail.