---

yaml
---
r: 235697
b: refs/heads/stable
c: cf1e078
h: refs/heads/master
i:
  235695: 7eec48f
v: v3

Author: ticki

[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: 48870d4f05177aa8e4d8439b71f39283f1880327
+refs/heads/stable: cf1e078bf65899f466ebe07d29732979a845a718
 refs/tags/1.0.0: 55bd4f8ff2b323f317ae89e254ce87162d52a375
 refs/tags/1.1.0: bc3c16f09287e5545c1d3f76b7abd54f2eca868b
 refs/tags/1.2.0: f557861f822c34f07270347b94b5280de20a597e

branches/stable/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.