Merge pull request #242 from jwilk/spelling

Fix typos.

security-advisories/2015-03-02-0-c++-integer-overflow.md

@@ -91,7 +91,7 @@ following preventative measures going forward:
 4. We will continue to require that all tests (including the new fuzz test) run
    cleanly under Valgrind before each release.
 5. We will commission a professional security review before any 1.0 release.
-   Until that time, we continue to recommend agaisnt using Cap'n Proto to
+   Until that time, we continue to recommend against using Cap'n Proto to
    interpret data from potentially-malicious sources.
 
 I am pleased that measures 1, 2, and 3 all detected this bug, suggesting that

security-advisories/2015-03-02-2-all-cpu-amplification.md

@@ -21,7 +21,7 @@ CVE-2015-2312
 Impact
 ======
 
-- Remotely cause a peer to use excessive CPU time and other resoucres to
+- Remotely cause a peer to use excessive CPU time and other resources to
   process a very small message, possibly enabling a DoS attack.
 
 Fixed in
@@ -69,6 +69,6 @@ Preventative measures
 =====================
 
 This problem was discovered through fuzz testing using American Fuzzy Lop,
-wich identified the problem as a "hang", although in fact the test case just
+which identified the problem as a "hang", although in fact the test case just
 took a very long time to complete. We are incorporating testing with AFL into
 our release process going forward.

security-advisories/2015-03-05-0-c++-addl-cpu-amplification.md

@@ -43,7 +43,7 @@ Details
 =======
 
 Advisory [2015-03-02-2][1] described a bug allowing a remote attacker to
-consume excessive CPU time or other resources usin a specially-crafted message.
+consume excessive CPU time or other resources using a specially-crafted message.
 The present advisory is simply another case of the same bug which was initially
 missed.