Fix line lengths

2 files changed, 12 insertions, 12 deletions

diff --git a/src/doc/rustc-dev-guide/src/bug-fix-procedure.md b/src/doc/rustc-dev-guide/src/bug-fix-procedure.md
index 9ad57be99e9..9c711ae1c87 100644
--- a/src/doc/rustc-dev-guide/src/bug-fix-procedure.md
+++ b/src/doc/rustc-dev-guide/src/bug-fix-procedure.md
@@ -289,13 +289,13 @@ self.tcx.sess.add_lint(lint::builtin::OVERLAPPING_INHERENT_IMPLS,
                        msg);
 ```
 
-We want to convert this into an error. In some cases, there may be an existing
-error for this scenario. In others, we will need to allocate a fresh diagnostic
-code.
-[Instructions for allocating a fresh diagnostic code can be found here.](diagnostics/diagnostic-codes.html)
-You may want to mention in the extended description that the compiler behavior
-changed on this point, and include a reference to the tracking issue for the
-change.
+We want to convert this into an error. In some cases, there may be an
+existing error for this scenario. In others, we will need to allocate a
+fresh diagnostic code.  [Instructions for allocating a fresh diagnostic
+code can be found here.](diagnostics/diagnostic-codes.html) You may want
+to mention in the extended description that the compiler behavior
+changed on this point, and include a reference to the tracking issue for
+the change.
 
 Let's say that we've adopted `E0592` as our code. Then we can change the
 `add_lint()` call above to something like:
diff --git a/src/doc/rustc-dev-guide/src/tests/intro.md b/src/doc/rustc-dev-guide/src/tests/intro.md
index cdb22a19cf4..b70a23a6a76 100644
--- a/src/doc/rustc-dev-guide/src/tests/intro.md
+++ b/src/doc/rustc-dev-guide/src/tests/intro.md
@@ -1,12 +1,12 @@
 # The compiler testing framework
 
-The Rust project runs a wide variety of different tests, orchestrated
-by the build system (`x.py test`).  The main test harness for testing
-the compiler itself is a tool called compiletest (located in the
+The Rust project runs a wide variety of different tests, orchestrated by
+the build system (`x.py test`).  The main test harness for testing the
+compiler itself is a tool called compiletest (located in the
 [`src/tools/compiletest`] directory). This section gives a brief
 overview of how the testing framework is setup, and then gets into some
-of the details on [how to run tests](./running.html) as well as
-[how to add new tests](./adding.html).
+of the details on [how to run tests](./running.html) as well as [how to
+add new tests](./adding.html).
 
 [`src/tools/compiletest`]: https://github.com/rust-lang/rust/tree/master/src/tools/compiletest