Update README.md

Author: Zarboni

README.md

@@ -2,15 +2,15 @@
 
 > *You're the last QA Engineer before release. The clock is ticking. Can you make the right call?*
 
-An interactive browser game for QA engineers — and anyone who's had to decide whether to ship at 5 PM on a Friday.
+An interactive browser game for QA engineers and Analysts and anyone who's had to decide whether to ship at 5 PM on a Friday.
 
 **[Play it here](https://zarboni.github.io/release-panic-simulator/)**
 
 ---
 
 ## What it is
 
-You're given a realistic release dashboard — test results, bug tracker, CI pipeline, risk score — and you have to make a call before the clock runs out. Four scenarios, each built around situations that actually happen on engineering teams.
+You're given a realistic release dashboard, test results, bug tracker, CI pipeline, risk score and you have to make a call before the clock runs out. Four scenarios, each built around situations that actually happen on engineering teams.
 
 Your options at the end of each scenario:
 
@@ -21,7 +21,7 @@ Your options at the end of each scenario:
 | **Request Hotfix** | Close to ready — one targeted fix first |
 | **Escalate to Dev Lead** | The decision is above your authority |
 
-There's always a correct answer. The outcome screen shows what would actually happen — and why.
+There's always a correct answer. The outcome screen shows what would actually happen and why.
 
 ---
 
@@ -61,7 +61,7 @@ There's always a correct answer. The outcome screen shows what would actually ha
 
 ## Why I built it
 
-I built this to show how I approach release decisions, not just that I can write tests. The scenarios are designed around the decisions that matter in practice:
+I built this to show colleagues how I approach release decisions, not just that I can write tests. The scenarios are designed around the decisions that matter in practice:
 
 - Reading the full picture, not just whether CI is green
 - Knowing when to block, when to escalate, and when a targeted fix is the right call
@@ -98,13 +98,13 @@ Requires Node.js 18+.
 ## Design Notes
 
 **Why retro terminal?**  
-QA work lives in terminals, CI dashboards, and bug trackers. The aesthetic fits the domain and makes the fake data feel more real than a polished UI would.
+QA work lives in terminals, CI dashboards, and bug trackers. The aesthetic fits the domain and makes the fake data feel more real than a polished UI would. Plus having that visual feel of viewing an old vhs tape 😂
 
 **Why four decisions instead of just approve/block?**  
-Because that's how it actually works. "Escalate" is a meaningful choice. "Request hotfix" is different from "block and come back later." The binary approve/reject framing misses the nuance.
+Because that's how it actually works. "Escalate" is a meaningful choice. "Request hotfix" is different from "block and come back later."
 
 **Why does Scenario 2 have a risk score of 28/100?**  
-That's the point. The risk score is calculated from what the pipeline can see — it can't read the diff. Most players approve it, and most players are wrong.
+That's the point. The risk score is calculated from what the pipeline can see. It can't read the diff. Most players approve it, and many players are wrong.
 
 **Why show consequences for every wrong answer?**  
 Punishing wrong answers without explanation doesn't teach anything. The outcome screen exists to make the reasoning visible, not just the verdict.
@@ -119,6 +119,3 @@ Punishing wrong answers without explanation doesn't teach anything. The outcome
 
 ---
 
-## License
-
-MIT — fork it, add scenarios, make it your own.