Cleanup Lesson 5 Running Collections

Removes unneeded draft section.

Author: diazjf

tutorial/content/Lesson 5/02-running-collections.md

@@ -27,7 +27,7 @@ This will execute all requests in the collection in the order they appear (alpha
   That this may fail because the certain requests depend on variables that are set in other requests.
 {{< /callout >}}
 
-## Handling Variables (e.g. {{newDogId}})
+## Running a Single Request
 
 One of the most powerful features of the CLI is that it maintains the **runtime state** of your variables, just like the desktop app.
 
@@ -65,29 +65,6 @@ which results in:
 └───────────────┴──────────────┘
 ```
 
-### Get Dog
-
-Questions:
-
-1. When running create dog, how do I get the actual response?
-2. How can I get the newDogId variable?
-3. Do sequences need to be set manually?
-
-**Get Dog**: In a subsequent request, we use that variable to fetch any details or verify the creation:
-    ```http
-    GET /api/dogs/{{newDogId}}
-    ```
-
-Now let's run **Get Dog**
-```bash
-#TODO: Not working, how can I get the newDogId variable?
-bru run Dogs/Get Dog.yml --env Local
-```
-
-When you run `bru run`, Bruno executes the "Create Dog" request first, sets the `newDogId` variable, and then correctly substitutes `{{newDogId}}` in the "Get Dog" request. You don't need to do anything special; the context is preserved automatically for the duration of the run.
-
-{{% /steps %}}
-
 ## Understanding the Output
 
 When the run completes, you will see a summary table in your terminal. Here is how to interpret it: