               <li>How your project addresses the theme of the hackathon.</li>
               <li>What tools did you use to collaborate.</li>
             </ol>
-          <p>Your submission should have a time label less than <b>#{endDay}</b>.
+          <p>Your submission should have a time label less than <b>#{secondDay} 2359 PDT</b>.
           Submissions received after the deadline will not be considered. No exceptions.
         </p>
       </article>

        any assets or code used as part of your submission must have been created during the event.
        The only exception to this rule is the usage of publicly available material. This includes:
        public code snippets, images, open source libraries and projects, public APIs, etc. You
        get the picture. Play fair!
        </p>
        <p>
        <i>Note: If your team qualifies for a prize, you are automatically subject to a code
        and asset review to ensure that the above rule has been adhered to.
        </i>
      </article>
      <article>
        <h4>What are the prizes?</h4>

        <h4>What is the schedule?</h4>
        <ul>
          <li>Now - Registration open.</li>
          <li>#{closeDay}, 1200 PDT - Applications are closed. Final notifications are sent to teams/individuals who were accepted and the
          Hackathon Theme is announced (on the <a href="https://koding.com/Activity/Topic/hackathon" target=_blank>#hackathon channel on Koding</a> and via email to the accepted teams).</li>
          <li>#{firstDay} - Day 1 Let the hacking begin!</li>
          <li>#{secondDay} - Day 2 of the Hackathon
            <ul>
              <li>0000 – 2200 PDT Hacking continues</li>
              <li>2330 – 2359 PDT Teams submit their projects to <a href="mailto:hackathon@koding.com">hackathon@koding.com</a> (see section below on how to submit)</li>
            </ul>
          </li>
          <li>#{emailDay} - Winners are notified via email and winning projects are listed for public viewing.</li>
