---

yaml
---
r: 229026
b: refs/heads/try
c: b79d279
h: refs/heads/master
v: v3

Author: Gankra

[refs]

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

branches/try/src/doc/tarpl/exotic-sizes.md

@@ -63,7 +63,7 @@ context.
 Rust largely understands that any operation that produces or stores a ZST can be
 reduced to a no-op. For instance, a `HashSet<T>` can be effeciently implemented
 as a thin wrapper around `HashMap<T, ()>` because all the operations `HashMap`
-normally does to store and retrieve keys will be completely stripped in
+normally does to store and retrieve values will be completely stripped in
 monomorphization.
 
 Similarly `Result<(), ()>` and `Option<()>` are effectively just fancy `bool`s.