---

yaml
---
r: 229004
b: refs/heads/try
c: e167ee8
h: refs/heads/master
v: v3

Author: mdinger

[refs]

@@ -1,7 +1,7 @@
 ---
 refs/heads/master: aca2057ed5fb7af3f8905b2bc01f72fa001c35c8
 refs/heads/snap-stage3: 1af31d4974e33027a68126fa5a5a3c2c6491824f
-refs/heads/try: 29e71b92bc5992dd2bf85dc4b27b60aaf0dcead8
+refs/heads/try: e167ee825984b649c1e5e1754b8479f70f1043c5
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503

branches/try/meet-safe-and-unsafe.md

@@ -14,12 +14,12 @@ on a leap year? Are we ready for that? Unsafe better be, because if they get
 built to Unsafe's standards!
 
 That's where Safe comes in. Safe has to handle *everything else*. Since Safe needs
-to *get work done*, they've grown to be fairly carless and clumsy! Safe doesn't worry
+to *get work done*, they've grown to be fairly careless and clumsy! Safe doesn't worry
 about all the crazy eventualities that Unsafe does, because life is too short to deal
 with leap-year-earthquakes. Of course, this means there's some jobs that Safe just
 can't handle. Safe is all about quantity over quality.
 
-Unsafe loves Safe to bits, but knows that tey *can never trust them to do the
+Unsafe loves Safe to bits, but knows that they *can never trust them to do the
 right thing*. Still, Unsafe acknowledges that not every problem needs quite the
 attention to detail that they apply. Indeed, Unsafe would *love* if Safe could do
 *everything* for them. To accomplish this, Unsafe spends most of their time