index 3bf2e68..b9d55fd 100644
@@ -12,15 +12,8 @@ you build a great project, then discover the submission requires a 2-minute vide
## why it's a gotcha
-submission requirements are often posted weeks before the deadline but nobody reads them until the end. the video, the writeup, the screenshots — these are what judges actually see first. your code might be excellent, but if your submission materials are rushed, judges form a bad first impression before they ever look at the project.
+submission requirements are often posted weeks before the deadline but nobody reads them until the end. the video, the writeup, the screenshots — these are what judges actually see first. your code might be excellent, but if your submission materials are rushed, judges form a bad first impression before they ever look at the project. discovering them last-minute while [[submitting-right-at-the-deadline|submitting at the deadline]] is the worst combination.
## the fix
-read the full submission requirements on day one. put the non-code deliverables on your task list alongside the coding work. allocate time for the video and writeup — they're not afterthoughts, they're the packaging.
-
-## see also
-
-- [[match-the-theme-track]] — read the rules before you build
-- [[check-what-you-submit]] — verify the submission matches the requirements
-- [[submitting-right-at-the-deadline]] — late discovery + last-minute = disaster
-- [[frame-impact-explicitly]] — the writeup is where you frame impact
\ No newline at end of file
+read the full submission requirements on day one. put the non-code deliverables on your task list alongside the coding work. allocate time for the video and writeup — they're not afterthoughts, they're the packaging. same lesson as [[match-the-theme-track|matching the theme]]: read the rules before you build. and [[check-what-you-submit|verify your submission]] matches what was asked for. the writeup is also where you [[frame-impact-explicitly|frame your impact]].
\ No newline at end of file