---

yaml
---
r: 236063
b: refs/heads/stable
c: adcd30c
h: refs/heads/master
i:
  236061: 0444ade
  236059: f1a45c2
  236055: 6f14223
  236047: 5f01c7d
  236031: fc5c0b8
v: v3

Author: Gankra

[refs]

@@ -29,7 +29,7 @@ refs/heads/tmp: afae2ff723393b3ab4ccffef6ac7c6d1809e2da0
 refs/tags/1.0.0-alpha.2: 4c705f6bc559886632d3871b04f58aab093bfa2f
 refs/tags/homu-tmp: f859507de8c410b648d934d8f5ec1c52daac971d
 refs/tags/1.0.0-beta: 8cbb92b53468ee2b0c2d3eeb8567005953d40828
-refs/heads/stable: 59ff3a39ae866b862678a769f469f0bae55606e5
+refs/heads/stable: adcd30c5a2aa732174b0c5deba3f4b9c9a9a44d0
 refs/tags/1.0.0: 55bd4f8ff2b323f317ae89e254ce87162d52a375
 refs/tags/1.1.0: bc3c16f09287e5545c1d3f76b7abd54f2eca868b
 refs/tags/1.2.0: f557861f822c34f07270347b94b5280de20a597e

branches/stable/safe-unsafe-meaning.md

@@ -98,7 +98,7 @@ destructors will be successfully called! Hooray!
 
 However BTreeMap is implemented using a modest spoonful of Unsafe (most collections
 are). That means that it is not necessarily *trivially true* that a bad Ord
-implementation will make BTreeMap behave safely. Unsafe most be sure not to rely
+implementation will make BTreeMap behave safely. Unsafe must be sure not to rely
 on Ord *where safety is at stake*, because Ord is provided by Safe, and memory
 safety is not Safe's responsibility to uphold. *It must be impossible for Safe
 code to violate memory safety*.