Update images and address feedback

Author: raksiv

docs/guides/python/debugging.mdx

@@ -16,25 +16,40 @@ This guide will walk you through setting up local debugging for Nitric applicati
 
 Debugging serverless-style applications can be challenging due to the way functions are triggered by events. For Python, we can use [`debugpy`](https://github.com/microsoft/debugpy) to connect a debugger to the service while it runs.
 
-### 1. Modify the Python entry point
+### 1. Add debugpy to our project
+
+```bash
+uv add debugpy
+```
+
+### 2. Modify the Python entry point
 
 Add the following lines to the top of the service file (e.g., `services/api.py`). This starts a debug server that the IDE can attach to.
 
+<Note>
+  This code is for local development only and must not be included in production
+  deployments.
+</Note>
+
 ```python
 import debugpy
 
 host, port = debugpy.listen(("0.0.0.0", 52509))  # Static port for consistent debugging
 print(f"✅ Debugpy is listening on {host}:{port}", flush=True)
 ```
 
-> A **static port** (`52509`) is used so the IDE knows which port to connect to. Update the `launch.json` configuration to match this port before starting the debugger.
+<Note>
+  A **static port** (`52509`) is used so the IDE knows which port to connect to.
+  Update the `launch.json` configuration to match this port before starting the
+  debugger.
+</Note>
 
-### 2. Update `nitric.yaml`
+### 3. Update `nitric.yaml`
 
-Modify the `start` command to include an auto-reloader and ensure Python does not use frozen modules, which can interfere with `debugpy`, E.g.
+Modify the `start` command to include an auto-reloader and ensure Python does not use frozen modules, which can interfere with `debugpy`:
 
 ```yaml
-name: message-board
+name: my-project
 services:
   - basedir: ''
     match: services/*.py
@@ -49,9 +64,12 @@ runtimes:
     args: {}
 ```
 
-> This configuration restarts the service on file changes and includes the necessary flags for debugging compatibility.
+<Note>
+  This configuration restarts the service on file changes and includes the
+  necessary flags for debugging compatibility.
+</Note>
 
-### 3. Configure `launch.json` in VS Code
+### 4. Configure `launch.json` in VS Code
 
 VS Code uses a `launch.json` file to define how it should start or attach to a debugging session. In this case, the debugger doesn't launch the application itself—it attaches to the running service that was started manually from the terminal.
 
@@ -85,14 +103,17 @@ To create or update the launch.json file:
 }
 ```
 
-> Ensure the `port` matches the value used in the `debugpy.listen()` call. If the port changes in the code, update it here as well.
+<Note>
+  Ensure the `port` matches the value used in the `debugpy.listen()` call. If
+  the port changes in the code, update it here as well.
+</Note>
 
-### 4. Running the debugger
+### 5. Running the debugger
 
-Start your nitric service with `nitric start` and start the debugger.
+Start your nitric service with `nitric start`, in the Terminal, both the Nitric runtime output and the debugpy listener output will be visible, including the active debug port.
 
-![vscode](/docs/images/guides/python-debugging/debugger.png)
+![vscode](/docs/images/guides/python-debugging/terminal.png)
 
-In the Terminal, both the Nitric runtime output and the debugpy listener output will be visible, including the active debug port.
+Now run the debugger and add breakpoints or watch variables.
 
-In this example, a breakpoint has been hit on line 16 of `message_api.py`, within an HTTP handler for the `/messages` endpoint.
+![vscode](/docs/images/guides/python-debugging/debug.png)