index 2efd7a5..541265e 100644
@@ -10,16 +10,8 @@ the presentation wasn't that great — should have emphasized live demo more. sp
## why it's a gotcha
-judges at hackathons care about working software. slides about your architecture or market research put them to sleep. they want to see you click buttons and have things happen.
+judges at hackathons care about working software. [[slides-as-documentation|packing slides with code snippets and architecture diagrams]] puts them to sleep. they want to see you click buttons and have things happen.
## the fix
-structure your presentation as: 30 seconds of problem/context, then live demo for as long as you can. slides should support the demo, not replace it.
-
-## see also
-
-- [[test-demo-before-presenting]] — the demo has to actually work first
-- [[slides-as-documentation]] — the anti-pattern this fights against
-- [[no-backup-plan-for-failed-demo]] — have a plan B for when live demo fails
-- [[pitching-matters-as-much-as-product]] — demo is the core of a good pitch
-- [[jumping-between-features-no-narrative]] — the demo needs a story
\ No newline at end of file
+structure your presentation as: 30 seconds of problem/context, then live demo for as long as you can. slides should support the demo, not replace it. of course, the demo has to [[test-demo-before-presenting|actually work first]], and you need a [[no-backup-plan-for-failed-demo|backup plan]] for when it doesn't. the demo itself needs a story — don't [[jumping-between-features-no-narrative|jump between features randomly]].
\ No newline at end of file