---

yaml
---
r: 210659
b: refs/heads/try
c: aa529ef
h: refs/heads/master
i:
  210657: 4db611b
  210655: 7e2ec68
v: v3

Author: meqif

[refs]

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

branches/try/src/librustc_resolve/diagnostics.rs

@@ -53,17 +53,17 @@ has been imported into the current module.
 
 Wrong example:
 ```
-extern a;
-extern crate_a as a;
+extern crate a;
+extern crate crate_a as a;
 ```
 
 The solution is to choose a different name that doesn't conflict with any
 external crate imported into the current module.
 
 Correct example:
 ```
-extern a;
-extern crate_a as other_name;
+extern crate a;
+extern crate crate_a as other_name;
 ```
 "##,
 
@@ -72,7 +72,7 @@ The name for an item declaration conflicts with an external crate's name.
 
 For instance,
 ```
-extern abc;
+extern crate abc;
 
 struct abc;
 ```
@@ -82,15 +82,15 @@ There are two possible solutions:
 Solution #1: Rename the item.
 
 ```
-extern abc;
+extern crate abc;
 
 struct xyz;
 ```
 
 Solution #2: Import the crate with a different name.
 
 ```
-extern abc as xyz;
+extern crate abc as xyz;
 
 struct abc;
 ```