Fix Dartfish context in Statsbomb case study

Corrected three technical inaccuracies in Problem section:
- UI: Button-heavy interface (not "rigid forms")
- Shortcuts: Had them, but weren't contextual (not "no shortcuts")
- Constraint: Keys couldn't overlap (not "competing for key space")

Added concrete math (50+ events vs 40 keys) to show ceiling problem.
This sets up architectural contrast with contextual solution later.

Author: saadshahd

src/pages/portfolio/statsbomb.mdx

@@ -44,7 +44,9 @@ import Accordion from '../../components/Accordion.astro';
 
 Week one. Ali and I sat down with paper. We hand-wrote sequencing rules for soccer matches—which events could follow which, what validated as legal, how phases transitioned. It was painful. But necessary.
 
-The industry-standard tool—Dartfish—couldn't scale to what we needed. Rigid forms forced mouse clicks for every field. No keyboard shortcuts meant collectors couldn't build muscle memory. Two collectors per match, each following a team, manually entering 3000+ events over 16 hours. Duplicated effort. No prevention, only validation after mistakes happened.
+The industry-standard tool—Dartfish—couldn't scale to what we needed. Button-heavy interface forced mouse clicks for every selection. It had keyboard shortcuts, but they weren't contextual. Each key could only map to one event type—globally, across the entire data spec. No overlap possible. With 50+ event types but only 40 usable keys, we hit a ceiling. Collectors memorized which arbitrary key triggered which event, at all times, regardless of game context. Cognitive overload.
+
+Two collectors per match, each following a team, manually entering 3000+ events over 16 hours. Duplicated effort. No prevention, only validation after mistakes happened.
 
 Years of daily conversations with collectors revealed their actual workflows and friction points. They needed keyboard flows that built muscle memory. Contextual mappings that reduced cognitive load. Collaboration patterns that eliminated rework.