Doh.  Update revision date.

Change-Id: If7ac3f9881b43b1eba9b807ad9ad4667c6904390
diff --git a/webm-contributor-guide.html b/webm-contributor-guide.html
index d1d7e7d..6676838 100644
--- a/webm-contributor-guide.html
+++ b/webm-contributor-guide.html
@@ -133,9 +133,9 @@
 
 <h1 id="contributing-source-code-to-libvpx">Contributing Source Code to libvpx</h1>
 
-<p><em>Revised 2010-12-22</em></p>
+<p><em>Revised 2011-01-05</em></p>
 
-<p>This document will help guide you through contributing code to the WebM 
+<p>This document will help guide you through contributing code to the WebM
 Project and libvpx.</p>
 
 <hr />
@@ -157,23 +157,23 @@
 
 <hr />
 
-<p>In general, most of the on-going work on libvpx concerns speed and 
+<p>In general, most of the on-going work on libvpx concerns speed and
 quality improvement. A developer typically follows this workflow:</p>
 
 <ol>
   <li>Work on the source code.</li>
   <li>Recompile the <code>vpxenc</code> encoder binary.</li>
   <li>Perform a video encode job with the new binary.</li>
-  <li>Evaluate the results, comparing to an identical encode done with a 
+  <li>Evaluate the results, comparing to an identical encode done with a
 prior version of <code>vpxenc</code>.</li>
 </ol>
 
-<p>Once meaningful improvement is achieved, the developer submits his code 
+<p>Once meaningful improvement is achieved, the developer submits his code
 revisions to <code>libvpx</code>.</p>
 
-<p>Below we describe in more detail how the core libvpx developers 
-evaluate their own work, so that new contributors can replicate the 
-process and have their code contributions approved and merged more 
+<p>Below we describe in more detail how the core libvpx developers
+evaluate their own work, so that new contributors can replicate the
+process and have their code contributions approved and merged more
 easily.</p>
 
 <h2 id="required-packages">Required Packages</h2>
@@ -186,16 +186,16 @@
 
 <h2 id="become-a-contributor">Become a Contributor</h2>
 
-<p>All contributors are welcome. The WebM Project website has details on 
-configuring your machine and creating an account in our code review 
-system, so review the information at 
+<p>All contributors are welcome. The WebM Project website has details on
+configuring your machine and creating an account in our code review
+system, so review the information at
 <strong><a href="http://www.webmproject.org/code/">http://www.webmproject.org/code/</a></strong> to get started.</p>
 
 <h2 id="subscribe-to-codec-devel">Subscribe to codec-devel</h2>
 
-<p><strong><em>codec-devel</em></strong> is the mailing list (and Google Group) for developers 
-working on the libvpx library or researching next generation codecs. 
-While anyone may post to codec-devel, subscribing gives you unmoderated 
+<p><strong><em>codec-devel</em></strong> is the mailing list (and Google Group) for developers
+working on the libvpx library or researching next generation codecs.
+While anyone may post to codec-devel, subscribing gives you unmoderated
 access.</p>
 
 <ul>
@@ -204,7 +204,7 @@
   <li>Post: <a href="&#109;&#097;&#105;&#108;&#116;&#111;:&#099;&#111;&#100;&#101;&#099;&#045;&#100;&#101;&#118;&#101;&#108;&#064;&#119;&#101;&#098;&#109;&#112;&#114;&#111;&#106;&#101;&#099;&#116;&#046;&#111;&#114;&#103;">&#099;&#111;&#100;&#101;&#099;&#045;&#100;&#101;&#118;&#101;&#108;&#064;&#119;&#101;&#098;&#109;&#112;&#114;&#111;&#106;&#101;&#099;&#116;&#046;&#111;&#114;&#103;</a></li>
 </ul>
 
-<p>Though <em>codec-devel</em> offers a web interface, many subscribers treat it 
+<p>Though <em>codec-devel</em> offers a web interface, many subscribers treat it
 as a simple mailing list and interact solely through their mail clients.</p>
 
 <h2 id="download-test-clips">Download Test Clips</h2>
@@ -213,29 +213,29 @@
   <li>Create a directory to hold the clips (e.g., <code>~/derf_cif</code> on Linux
 or <code>c:/derf_cif</code> on Windows).</li>
   <li>Visit <a href="http://media.xiph.org/video/derf/">http://media.xiph.org/video/derf/</a> with your web browser.</li>
-  <li>Download each of the the CIF clips found there, in YUV4MPEG (y4m) 
+  <li>Download each of the the CIF clips found there, in YUV4MPEG (y4m)
 format, to the directory you created.</li>
 </ol>
 
 <div class="admon tip">
   <p>Encoding Only a Few Test Clips</p>
 
-  <p>Normally, you won&rsquo;t want to encode the entire set of test clips, which 
-can be very time-consuming. Instead, consider symlinking only the clips 
-you want to use from their storage directory (e.g. <code>~/derf_cif</code>) to a 
+  <p>Normally, you won&rsquo;t want to encode the entire set of test clips, which
+can be very time-consuming. Instead, consider symlinking only the clips
+you want to use from their storage directory (e.g. <code>~/derf_cif</code>) to a
 working directory (e.g. <code>~/derf_working</code>), and running your tests there.</p>
 </div>
 
 <h2 id="download-test-scripts">Download Test Scripts</h2>
 
-<p>Test scripts (and this document) are available in the 
+<p>Test scripts (and this document) are available in the
 <code>contributor-guide</code> Git project:</p>
 
 <pre><code>$ git clone git://review.webmproject.org/contributor-guide.git
 $ cd contributor-guide
 </code></pre>
 
-<p>Symlink or physically copy the following scripts to somewhere in your 
+<p>Symlink or physically copy the following scripts to somewhere in your
 $PATH:</p>
 
 <ul>
@@ -248,19 +248,19 @@
 
 <ol>
   <li>
-    <p>To get started, ensure that your system satisfies the <strong><a href="http://www.webmproject.org/code/build-prerequisites/">build 
+    <p>To get started, ensure that your system satisfies the <strong><a href="http://www.webmproject.org/code/build-prerequisites/">build
 prerequisites</a></strong>.</p>
   </li>
   <li>
-    <p>Next, <strong>clone the libvpx repository</strong>. After cloning, you&rsquo;ll be 
+    <p>Next, <strong>clone the libvpx repository</strong>. After cloning, you&rsquo;ll be
 working in the master branch by default.</p>
 
     <pre><code>$ git clone git://review.webmproject.org/libvpx.git
 $ cd libvpx
 </code></pre>
 
-    <p><strong>Important:</strong>  If your idea necessitates a change to the VP8 
-format itself, you&rsquo;ll want to work in the libvpx experimental 
+    <p><strong>Important:</strong>  If your idea necessitates a change to the VP8
+format itself, you&rsquo;ll want to work in the libvpx experimental
 branch instead:</p>
 
     <pre><code>$ git clone git://review.webmproject.org/libvpx.git
@@ -269,8 +269,8 @@
 </code></pre>
   </li>
   <li>
-    <p><strong>Configure and build libvpx.</strong> Be sure to run the configure 
-script with <code>--enable-psnr</code>, which causes the encoder (<code>vpxenc</code>) 
+    <p><strong>Configure and build libvpx.</strong> Be sure to run the configure
+script with <code>--enable-psnr</code>, which causes the encoder (<code>vpxenc</code>)
 to output statistical data as well as a video file. For example:</p>
 
     <pre><code>$ ./configure --disable-codecs --enable-vp8 --enable-psnr --enable-debug --disable-install-docs --log=yes
@@ -282,8 +282,8 @@
     <pre><code>$ ./configure --help
 </code></pre>
 
-    <p>There are several ways to &ldquo;install&rdquo; (<code>make install</code>, etc.), so 
-we&rsquo;ll leave that up to you.  Just ensure that the VP8 encoder 
+    <p>There are several ways to &ldquo;install&rdquo; (<code>make install</code>, etc.), so
+we&rsquo;ll leave that up to you.  Just ensure that the VP8 encoder
 (<code>vpxenc</code>) is executable and in your $PATH.</p>
   </li>
   <li>
@@ -293,29 +293,29 @@
 $ run_tests 200 500 50 baseline
 </code></pre>
 
-    <p>In this example, <code>run_tests</code> will encode each <code>y4m</code> file in the 
-current directory at bitrates of 200, 250, 300, 350, 400, 450 and 
-500 kbps (start at 200, end at 500, 50 kbps increments). It will 
+    <p>In this example, <code>run_tests</code> will encode each <code>y4m</code> file in the
+current directory at bitrates of 200, 250, 300, 350, 400, 450 and
+500 kbps (start at 200, end at 500, 50 kbps increments). It will
 create a directory <code>baseline</code> and write its output there.</p>
 
-    <p>Output consists of <code>webm</code> video files and <code>stt</code> files containing 
-statistics for each encode. If the test encodes are 2-pass 
-(default), an <code>fpf</code> file (first-pass data file) is also written 
-for each input file, and will be reused on subsequent 2-pass 
+    <p>Output consists of <code>webm</code> video files and <code>stt</code> files containing
+statistics for each encode. If the test encodes are 2-pass
+(default), an <code>fpf</code> file (first-pass data file) is also written
+for each input file, and will be reused on subsequent 2-pass
 encodes if not deleted.</p>
   </li>
   <li>
-    <p><strong>Make your changes to libvpx</strong>, rebuild, and re-run the tests 
+    <p><strong>Make your changes to libvpx</strong>, rebuild, and re-run the tests
 using a different output directory name. Example:</p>
 
     <pre><code>$ run_tests 200 500 50 mytweak
 </code></pre>
 
-    <p>Alternatively, change the parameters in the batch encoder script 
-(<code>be</code>) that&rsquo;s called by <code>run_tests</code>. <code>be</code> in turn calls <code>vpxenc</code>. </p>
+    <p>Alternatively, change the parameters in the batch encoder script
+(<code>be</code>) that&rsquo;s called by <code>run_tests</code>. <code>be</code> in turn calls <code>vpxenc</code>.</p>
   </li>
   <li>
-    <p>When the tests are finished, run <code>visual_metrics.py</code> to generate 
+    <p>When the tests are finished, run <code>visual_metrics.py</code> to generate
 an <strong>HTML-format report</strong> that compares <code>mytweak</code> with <code>baseline</code>.</p>
 
     <pre><code>$ visual_metrics.py . baseline mytweak &gt; mytweak.html
diff --git a/webm-contributor-guide.txt b/webm-contributor-guide.txt
index 670ea1c..15e2c52 100644
--- a/webm-contributor-guide.txt
+++ b/webm-contributor-guide.txt
@@ -2,9 +2,9 @@
 Contributing Source Code to libvpx
 ==================================
 
-_Revised 2010-12-22_
+_Revised 2011-01-05_
 
-This document will help guide you through contributing code to the WebM 
+This document will help guide you through contributing code to the WebM
 Project and libvpx.
 
 * * *
@@ -16,21 +16,21 @@
 
 * * *
 
-In general, most of the on-going work on libvpx concerns speed and 
+In general, most of the on-going work on libvpx concerns speed and
 quality improvement. A developer typically follows this workflow:
 
   1. Work on the source code.
   2. Recompile the `vpxenc` encoder binary.
   3. Perform a video encode job with the new binary.
-  4. Evaluate the results, comparing to an identical encode done with a 
+  4. Evaluate the results, comparing to an identical encode done with a
      prior version of `vpxenc`.
 
-Once meaningful improvement is achieved, the developer submits his code 
+Once meaningful improvement is achieved, the developer submits his code
 revisions to `libvpx`.
 
-Below we describe in more detail how the core libvpx developers 
-evaluate their own work, so that new contributors can replicate the 
-process and have their code contributions approved and merged more 
+Below we describe in more detail how the core libvpx developers
+evaluate their own work, so that new contributors can replicate the
+process and have their code contributions approved and merged more
 easily.
 
 
@@ -45,25 +45,25 @@
 Become a Contributor
 --------------------
 
-All contributors are welcome. The WebM Project website has details on 
-configuring your machine and creating an account in our code review 
-system, so review the information at 
+All contributors are welcome. The WebM Project website has details on
+configuring your machine and creating an account in our code review
+system, so review the information at
 **<http://www.webmproject.org/code/>** to get started.
 
 
 Subscribe to codec-devel
 ------------------------
 
-**_codec-devel_** is the mailing list (and Google Group) for developers 
-working on the libvpx library or researching next generation codecs. 
-While anyone may post to codec-devel, subscribing gives you unmoderated 
+**_codec-devel_** is the mailing list (and Google Group) for developers
+working on the libvpx library or researching next generation codecs.
+While anyone may post to codec-devel, subscribing gives you unmoderated
 access.
 
   * Archive: <https://groups.google.com/a/webmproject.org/group/codec-devel>
   * Subscribe: <codec-devel+subscribe@webmproject.org>
   * Post: <codec-devel@webmproject.org>
 
-Though _codec-devel_ offers a web interface, many subscribers treat it 
+Though _codec-devel_ offers a web interface, many subscribers treat it
 as a simple mailing list and interact solely through their mail clients.
 
 
@@ -73,15 +73,15 @@
   1. Create a directory to hold the clips (e.g., `~/derf_cif` on Linux
      or `c:/derf_cif` on Windows).
   2. Visit <http://media.xiph.org/video/derf/> with your web browser.
-  3. Download each of the the CIF clips found there, in YUV4MPEG (y4m) 
+  3. Download each of the the CIF clips found there, in YUV4MPEG (y4m)
      format, to the directory you created.
 
 <div class="admon tip" markdown="1">
 Encoding Only a Few Test Clips
 
-Normally, you won't want to encode the entire set of test clips, which 
-can be very time-consuming. Instead, consider symlinking only the clips 
-you want to use from their storage directory (e.g. `~/derf_cif`) to a 
+Normally, you won't want to encode the entire set of test clips, which
+can be very time-consuming. Instead, consider symlinking only the clips
+you want to use from their storage directory (e.g. `~/derf_cif`) to a
 working directory (e.g. `~/derf_working`), and running your tests there.
 </div>
 
@@ -89,7 +89,7 @@
 Download Test Scripts
 ---------------------
 
-Test scripts (and this document) are available in the 
+Test scripts (and this document) are available in the
 `contributor-guide` Git project:
 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -97,7 +97,7 @@
 $ cd contributor-guide
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Symlink or physically copy the following scripts to somewhere in your 
+Symlink or physically copy the following scripts to somewhere in your
 $PATH:
 
   * `be`
@@ -108,10 +108,10 @@
 Download, Build and Test libvpx
 -------------------------------
 
-  1. To get started, ensure that your system satisfies the **[build 
+  1. To get started, ensure that your system satisfies the **[build
      prerequisites](http://www.webmproject.org/code/build-prerequisites/)**.
 
-  2. Next, **clone the libvpx repository**. After cloning, you'll be 
+  2. Next, **clone the libvpx repository**. After cloning, you'll be
      working in the master branch by default.
 
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -119,8 +119,8 @@
      $ cd libvpx
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-     **Important:**  If your idea necessitates a change to the VP8 
-     format itself, you'll want to work in the libvpx experimental 
+     **Important:**  If your idea necessitates a change to the VP8
+     format itself, you'll want to work in the libvpx experimental
      branch instead:
 
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -129,8 +129,8 @@
      $ git checkout experimental
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-  3. **Configure and build libvpx.** Be sure to run the configure 
-     script with `--enable-psnr`, which causes the encoder (`vpxenc`) 
+  3. **Configure and build libvpx.** Be sure to run the configure
+     script with `--enable-psnr`, which causes the encoder (`vpxenc`)
      to output statistical data as well as a video file. For example:
 
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -139,44 +139,44 @@
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
      To learn more about configuration options, do:
-     
+
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      $ ./configure --help
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-     
-     There are several ways to "install" (`make install`, etc.), so 
-     we'll leave that up to you.  Just ensure that the VP8 encoder 
+
+     There are several ways to "install" (`make install`, etc.), so
+     we'll leave that up to you.  Just ensure that the VP8 encoder
      (`vpxenc`) is executable and in your $PATH.
-     
+
   4. **Run some encodes** using the provided scripts.  Example:
 
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      $ cd <test clip directory>
      $ run_tests 200 500 50 baseline
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-     
-     In this example, `run_tests` will encode each `y4m` file in the 
-     current directory at bitrates of 200, 250, 300, 350, 400, 450 and 
-     500 kbps (start at 200, end at 500, 50 kbps increments). It will 
+
+     In this example, `run_tests` will encode each `y4m` file in the
+     current directory at bitrates of 200, 250, 300, 350, 400, 450 and
+     500 kbps (start at 200, end at 500, 50 kbps increments). It will
      create a directory `baseline` and write its output there.
-     
-     Output consists of `webm` video files and `stt` files containing 
-     statistics for each encode. If the test encodes are 2-pass 
-     (default), an `fpf` file (first-pass data file) is also written 
-     for each input file, and will be reused on subsequent 2-pass 
+
+     Output consists of `webm` video files and `stt` files containing
+     statistics for each encode. If the test encodes are 2-pass
+     (default), an `fpf` file (first-pass data file) is also written
+     for each input file, and will be reused on subsequent 2-pass
      encodes if not deleted.
 
-  5. **Make your changes to libvpx**, rebuild, and re-run the tests 
+  5. **Make your changes to libvpx**, rebuild, and re-run the tests
      using a different output directory name. Example:
 
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      $ run_tests 200 500 50 mytweak
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-     Alternatively, change the parameters in the batch encoder script 
-     (`be`) that's called by `run_tests`. `be` in turn calls `vpxenc`. 
-     
-  6. When the tests are finished, run `visual_metrics.py` to generate 
+     Alternatively, change the parameters in the batch encoder script
+     (`be`) that's called by `run_tests`. `be` in turn calls `vpxenc`.
+
+  6. When the tests are finished, run `visual_metrics.py` to generate
      an **HTML-format report** that compares `mytweak` with `baseline`.
 
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~