---

yaml
---
r: 210822
b: refs/heads/try
c: 190de69
h: refs/heads/master
v: v3

Author: cactorium

[refs]

@@ -2,7 +2,7 @@
 refs/heads/master: 3e561f05c00cd180ec02db4ccab2840a4aba93d2
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: ba0e1cd8147d452c356aacb29fb87568ca26f111
-refs/heads/try: 507f8b8d942f17452c16876a02bef9e1bc15d028
+refs/heads/try: 190de695f58e9cb71d9b799b13570b33f4422363
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/dist-snap: ba4081a5a8573875fed17545846f6f6902c8ba8d
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596

branches/try/src/librustc_typeck/diagnostics.rs

@@ -367,7 +367,7 @@ it has been disabled for now.
 E0197: r##"
 Inherent implementations (one that do not implement a trait but provide
 methods associated with a type) are always safe because they are not
-implementing an unsafe trait. Removing the unsafe keyword from the inherent
+implementing an unsafe trait. Removing the `unsafe` keyword from the inherent
 implementation will resolve this error.
 
 ```