---

yaml
---
r: 221008
b: refs/heads/auto
c: cf1e078
h: refs/heads/master
v: v3

Author: ticki

[refs]

@@ -8,7 +8,7 @@ refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503
 refs/tags/release-0.3.1: 495bae036dfe5ec6ceafd3312b4dca48741e845b
 refs/tags/release-0.4: e828ea2080499553b97dfe33b3f4d472b4562ad7
 refs/tags/release-0.5: 7e3bcfbf21278251ee936ad53e92e9b719702d73
-refs/heads/auto: 48870d4f05177aa8e4d8439b71f39283f1880327
+refs/heads/auto: cf1e078bf65899f466ebe07d29732979a845a718
 refs/tags/release-0.6: b4ebcfa1812664df5e142f0134a5faea3918544c
 refs/tags/0.1: b19db808c2793fe2976759b85a355c3ad8c8b336
 refs/tags/0.2: 1754d02027f2924bed83b0160ee340c7f41d5ea1

branches/auto/src/doc/trpl/unsafe.md

@@ -103,7 +103,7 @@ borrow checker’. Adding `unsafe` to some random Rust code doesn’t change its
 semantics, it won’t just start accepting anything. But it will let you write
 things that _do_ break some of the rules.
 
-You will also encounter the 'unsafe' keyword when writing bindings to foreign
+You will also encounter the `unsafe` keyword when writing bindings to foreign
 (non-Rust) interfaces. You're encouraged to write a safe, native Rust interface
 around the methods provided by the library.