Revert "moved from demo section to prize section"

This reverts commit f1eba1d.

index.markdown

@@ -385,6 +385,13 @@ prize for it relatively small, and give attendees a one-time token (a code on
 the reverse of their pass for large events, or a physical item for smaller ones)
 in order to vote.
 
+### Judge Selection
+
+The judges for your hackathon should reflect the nature of your event.
+For standard hackathons, judges should be primarily technical or knowledgable in the relevant thematic area (eg. musicians judging Music Hack Day).
+Try to avoid having businesspeople (VCs, non-technical founders, journalists, etc.) judge technical events, as it encourages hackers to build prototype businesses, not interesting hacks.
+It should be possible to win a hackathon based purely on technical merit, even if the hack is completely impractical.
+
 ### Judge previews _Optional_
 
 If possible, let the judges meet all the teams for a few minutes, a couple of
@@ -458,13 +465,6 @@ are likely to just disappoint the winning team. When organizations/individuals
 wish to pursue further development of a hack they should speak to the winning
 team separately.
 
-### Judge selection
-
-The judges for your hackathon should reflect the nature of your event.
-For standard hackathons, judges should be primarily technical or knowledgable in the relevant thematic area (eg. musicians judging Music Hack Day).
-Try to avoid having businesspeople (VCs, non-technical founders, journalists, etc.) judge technical events, as it encourages hackers to build prototype businesses, not interesting hacks.
-It should be possible to win a hackathon based purely on technical merit, even if the hack is completely impractical.
-
 ## Atmosphere and attitudes
 
 ### Don't make people feel unwelcome