Fixed typos

Resolves #18

applied using `hub am https://github.com/facebook/watchman/pull/18`

BSER.markdown

@@ -63,7 +63,7 @@ A real number is indicated by a `0x07` byte followed by 8 bytes of double value.
 `0x0b` indicates a compact array of objects follows.  Some of the bigger
 datastructures returned by watchman are tabular data expressed as an array
 of objects.  This serialization type factors out the repeated object keys
-into a header array listing the keys, followed by an array continaing
+into a header array listing the keys, followed by an array containing
 all the values of the objects.
 
 To represent missing keys in templated arrays, the `0x0c` encoding value may

README.markdown

@@ -1179,7 +1179,7 @@ of it!) and be followed by a newline `\n` character:
 ## Contributing?
 
 If you're thinking of hacking on watchman we'd love to hear from you!
-Feel free to use the Github issue tracker and pull requests discuss and
+Feel free to use the GitHub issue tracker and pull requests discuss and
 submit code changes.
 
 We (Facebook) have to ask for a "Contributor License Agreement" from someone

arcanist/lib/WatchmanInstance.php

@@ -391,7 +391,7 @@ function generateValgrindTestResults() {
           }
         }
       } else {
-        var_dump($xml_data);
+        var_dump($vg);
       }
     }
 

hash.c

@@ -106,7 +106,7 @@ uint32_t w_hash_bytes(const void *key, size_t length, uint32_t initval)
      * rest of the string.  Every machine with memory protection I've seen
      * does it on word boundaries, so is OK with this.  But VALGRIND will
      * still catch it and complain.  The masking trick does make the hash
-     * noticably faster for short strings (like English words).
+     * noticeably faster for short strings (like English words).
      */
     if (!running_on_valgrind()) {