Update 04-github-actions-intro.md

Author: pelikhan

workshop/04-github-actions-intro.md

@@ -106,31 +106,6 @@ Open a real workflow file and find the three core building blocks — no termina
    - One `jobs:` entry — what is the job named?
    - One `steps` item — what command does it run?
 
-You don't need to understand every line. The goal is to see that a real workflow follows exactly the structure described above.
-
-- [ ] I found the `on:` trigger in a real workflow
-- [ ] I identified a job name under `jobs:`
-- [ ] I found at least one `steps` command
-
-## Check your understanding
-
-Mark each statement as true or false, then reveal the answers:
-
-- [ ] Workflow files live in `.github/workflows/` as YAML
-- [ ] The `on:` key defines when a workflow runs, not which commands to execute
-- [ ] Each step in a job runs on its own separate virtual machine
-- [ ] Agentic workflows replace scripted steps with a plain-language brief
-
-<details>
-<summary>Reveal answers</summary>
-
-1. True — workflow files live in `.github/workflows/` as YAML.
-2. True — `on:` is the trigger; commands go in `steps` entries.
-3. False — steps within a job share one runner; a new machine is provisioned per job.
-4. True — agentic workflows use a Markdown brief in place of scripted `steps`; the agent decides the how.
-
-</details>
-
 ## ✅ Checkpoint
 
 - [ ] I can identify `on`, `jobs`, and `steps` in a workflow file