From dd175841e5b76e72bf260bd35e08374c3b1dbd50 Mon Sep 17 00:00:00 2001
From: Aaron McPhall <amcphall@gmail.com>
Date: Tue, 31 Jan 2012 17:39:01 -0500
Subject: [PATCH] Changed scoring.html to reflect multi-point tokens

---
 packages/mcp/www/scoring.html | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/packages/mcp/www/scoring.html b/packages/mcp/www/scoring.html
index a268508..c48ec0f 100644
--- a/packages/mcp/www/scoring.html
+++ b/packages/mcp/www/scoring.html
@@ -29,7 +29,7 @@
     <p>
       Many of the categories are in the form of
       multiple <em>puzzles</em>: for each puzzle presented, a
-      case-sensitive answer must be found to recieve the amount of
+      case-sensitive answer must be found to receive the amount of
       points that puzzle is worth.  Any team may answer any puzzle
       question at any time.  A new puzzle is revealed when a team
       correctly answers the highest-valued puzzle in that category.
@@ -38,12 +38,20 @@
 
     <h2 id="tokens">Tokens</h2>
     <p>
-      Tokens are strings redeemable once for a single point each.  A
+      Tokens are strings redeemable once for points. They take on
+      two forms: a single or multipoint token. A single point
       token for the "example" category might look like this:
     </p>
 
     <pre>example:xylep-radar-nanox</pre>
 
+    <p>
+      A 42 point
+      token for the "example" category might look like this:
+    </p>
+
+    <pre>example:42:xihyp-ropar-nanix</pre>
+
     <p>
       Tokens are typically associated with "live" categories, such as a
       network-based service or a treasure hunt.  Tokens can be submitted