A couple of sentence edits for grammar, and some line length tweaks for

consistency (80-character limit).

Author: iangneal

CONTRIBUTING.md

@@ -1,8 +1,8 @@
 # Contributing to Rust
 
 Thank you for your interest in contributing to Rust! There are many ways to
-contribute, and we appreciate all of them. This document is a bit long, so here's
-links to the major sections:
+contribute, and we appreciate all of them. This document is a bit long, so here
+are links to the major sections:
 
 * [Feature Requests](#feature-requests)
 * [Bug Reports](#bug-reports)
@@ -13,10 +13,11 @@ links to the major sections:
 * [Out-of-tree Contributions](#out-of-tree-contributions)
 * [Helpful Links and Information](#helpful-links-and-information)
 
-If you have questions, please make a post on [internals.rust-lang.org][internals] or
-hop on [#rust-internals][pound-rust-internals].
+If you have questions, please make a post on [internals.rust-lang.org][internals]
+or hop on [#rust-internals][pound-rust-internals].
 
-As a reminder, all contributors are expected to follow our [Code of Conduct][coc].
+As a reminder, all contributors are expected to follow our
+[Code of Conduct][coc].
 
 [pound-rust-internals]: http://chat.mibbit.com/?server=irc.mozilla.org&channel=%23rust-internals
 [internals]: https://internals.rust-lang.org
@@ -35,14 +36,15 @@ While bugs are unfortunate, they're a reality in software. We can't fix what we
 don't know about, so please report liberally. If you're not sure if something
 is a bug or not, feel free to file a bug anyway.
 
-**If you believe reporting your bug publicly represents a security risk to Rust users,
-please follow our [instructions for reporting security vulnerabilities](https://www.rust-lang.org/security.html)**.
+**If you believe reporting your bug publicly represents a security risk to Rust
+users, please follow our [instructions for reporting security vulnerabilities]
+(https://www.rust-lang.org/security.html)**.
 
 If you have the chance, before reporting a bug, please [search existing
 issues](https://github.com/rust-lang/rust/search?q=&type=Issues&utf8=%E2%9C%93),
 as it's possible that someone else has already reported your error. This doesn't
-always work, and sometimes it's hard to know what to search for, so consider this
-extra credit. We won't mind if you accidentally file a duplicate report.
+always work, and sometimes it's hard to know what to search for, so consider
+this extra credit. We won't mind if you accidentally file a duplicate report.
 
 Opening an issue is as easy as following [this
 link](https://github.com/rust-lang/rust/issues/new) and filling out the fields.
@@ -126,9 +128,9 @@ file. If you still have a `config.mk` file in your directory - from
 
 ### Building
 
-The build system uses the `x.py` script to control the build process. This script
-is used to build, test, and document various parts of the compiler. You can
-execute it as:
+The build system uses the `x.py` script to control the build process. This
+script is used to build, test, and document various parts of the compiler. You
+can execute it as:
 
 ```sh
 python x.py build
@@ -315,10 +317,10 @@ To find documentation-related issues, sort by the [A-docs label][adocs].
 
 [adocs]: https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AA-docs
 
-In many cases, you don't need a full `./x.py doc`. You can use `rustdoc` directly
-to check small fixes. For example, `rustdoc src/doc/reference.md` will render
-reference to `doc/reference.html`. The CSS might be messed up, but you can
-verify that the HTML is right.
+In many cases, you don't need a full `./x.py doc`. You can use `rustdoc`
+directly to check small fixes. For example, `rustdoc src/doc/reference.md` will
+render reference to `doc/reference.html`. The CSS might be messed up, but you
+can verify that the HTML is right.
 
 ## Issue Triage
 

COPYRIGHT

@@ -6,8 +6,7 @@ terms.
 
 Longer version:
 
-The Rust Project is copyright 2010, The Rust Project
-Developers.
+The Rust Project is copyright 2010, The Rust Project Developers.
 
 Licensed under the Apache License, Version 2.0
 <LICENSE-APACHE or
@@ -270,9 +269,9 @@ their own copyright notices and license terms:
     modification, are permitted provided that the following conditions are met:
     1. Redistributions of source code must retain the above copyright notice(s),
        this list of conditions and the following disclaimer.
-    2. Redistributions in binary form must reproduce the above copyright notice(s),
-       this list of conditions and the following disclaimer in the documentation
-       and/or other materials provided with the distribution.
+    2. Redistributions in binary form must reproduce the above copyright
+       notice(s), this list of conditions and the following disclaimer in the
+       documentation and/or other materials provided with the distribution.
 
     THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER(S)
     ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,

RELEASES.md

@@ -305,7 +305,8 @@ Cargo
 * [Fix retrying crate downloads for network errors][cargo/3348]
 * [Implement string lookup for `build.rustflags` config key][cargo/3356]
 * [Emit more info on --message-format=json][cargo/3319]
-* [Assume `build.rs` in the same directory as `Cargo.toml` is a build script][cargo/3361]
+* [Assume `build.rs` in the same directory as `Cargo.toml` is a build
+  script][cargo/3361]
 * [Don't ignore errors in workspace manifest][cargo/3409]
 * [Fix `--message-format JSON` when rustc emits non-JSON warnings][cargo/3410]
 
@@ -330,8 +331,8 @@ Misc
 * [Rust supports i686-unknown-openbsd][38086]. Tier 3 support. No testing or
   releases.
 * [Rust supports the MSP430][37627]. Tier 3 support. No testing or releases.
-* [Rust supports the ARMv5TE architecture][37615]. Tier 3 support. No testing or
-  releases.
+* [Rust supports the ARMv5TE architecture][37615]. Tier 3 support. No testing
+  or releases.
 
 Compatibility Notes
 -------------------
@@ -923,13 +924,16 @@ Version 1.12.1 (2016-10-20)
 Regression Fixes
 ----------------
 
-* [ICE: 'rustc' panicked at 'assertion failed: concrete_substs.is_normalized_for_trans()' #36381][36381]
+* [ICE: 'rustc' panicked at 'assertion failed: concrete_substs.is_normalized_
+  for_trans()' #36381][36381]
 * [Confusion with double negation and booleans][36856]
 * [rustc 1.12.0 fails with SIGSEGV in release mode (syn crate 0.8.0)][36875]
 * [Rustc 1.12.0 Windows build of `ethcore` crate fails with LLVM error][36924]
-* [1.12.0: High memory usage when linking in release mode with debug info][36926]
+* [1.12.0: High memory usage when linking in release mode with debug
+  info][36926]
 * [Corrupted memory after updated to 1.12][36936]
-* ["Let NullaryConstructor = something;" causes internal compiler error: "tried to overwrite interned AdtDef"][37026]
+* ["Let NullaryConstructor = something;" causes internal compiler error: "tried
+  to overwrite interned AdtDef"][37026]
 * [Fix ICE: inject bitcast if types mismatch for invokes/calls/stores][37112]
 * [debuginfo: Handle spread_arg case in MIR-trans in a more stable way.][37153]
 
@@ -1165,7 +1169,7 @@ Tooling
 * [Test binaries now support a `--test-threads` argument to specify the number
   of threads used to run tests, and which acts the same as the
   `RUST_TEST_THREADS` environment variable]
-  (https://github.com/rust-lang/rust/pull/35414)  
+  (https://github.com/rust-lang/rust/pull/35414)
 * [The test runner now emits a warning when tests run over 60 seconds]
   (https://github.com/rust-lang/rust/pull/35405)
 * [rustdoc: Fix methods in search results]
@@ -2217,15 +2221,22 @@ Libraries
     be the same length
     * `<[T]>::`[`sort_by_key`]
   * checked, saturated, and overflowing operations
-    * [`i32::checked_rem`], [`i32::checked_neg`], [`i32::checked_shl`], [`i32::checked_shr`]
+    * [`i32::checked_rem`], [`i32::checked_neg`], [`i32::checked_shl`],
+      [`i32::checked_shr`]
     * [`i32::saturating_mul`]
-    * [`i32::overflowing_add`], [`i32::overflowing_sub`], [`i32::overflowing_mul`], [`i32::overflowing_div`]
-    * [`i32::overflowing_rem`], [`i32::overflowing_neg`], [`i32::overflowing_shl`], [`i32::overflowing_shr`]
-    * [`u32::checked_rem`], [`u32::checked_neg`], [`u32::checked_shl`], [`u32::checked_shl`]
+    * [`i32::overflowing_add`], [`i32::overflowing_sub`],
+      [`i32::overflowing_mul`], [`i32::overflowing_div`]
+    * [`i32::overflowing_rem`], [`i32::overflowing_neg`],
+      [`i32::overflowing_shl`], [`i32::overflowing_shr`]
+    * [`u32::checked_rem`], [`u32::checked_neg`], [`u32::checked_shl`],
+      [`u32::checked_shl`]
     * [`u32::saturating_mul`]
-    * [`u32::overflowing_add`], [`u32::overflowing_sub`], [`u32::overflowing_mul`], [`u32::overflowing_div`]
-    * [`u32::overflowing_rem`], [`u32::overflowing_neg`], [`u32::overflowing_shl`], [`u32::overflowing_shr`]
-    * and checked, saturated, and overflowing operations for other primitive types
+    * [`u32::overflowing_add`], [`u32::overflowing_sub`],
+      [`u32::overflowing_mul`], [`u32::overflowing_div`]
+    * [`u32::overflowing_rem`], [`u32::overflowing_neg`],
+      [`u32::overflowing_shl`], [`u32::overflowing_shr`]
+    * and checked, saturated, and overflowing operations for other primitive
+      types
   * FFI
     * [`ffi::IntoStringError`]
     * [`CString::into_string`]
@@ -3321,7 +3332,8 @@ Highlights
     access to all underlying information.
 * The compiler now contains extended explanations of many errors. When an error
   with an explanation occurs the compiler suggests using the `--explain` flag
-  to read the explanation. Error explanations are also [available online][err-index].
+  to read the explanation. Error explanations are also
+  [available online][err-index].
 * Thanks to multiple [improvements][sk] to [type checking][pre], as
   well as other work, the time to bootstrap the compiler decreased by
   32%.
@@ -4156,7 +4168,8 @@ Version 0.10 (2014-04-03)
     * Trailing commas are now allowed in argument lists and tuple patterns.
     * The `do` keyword has been removed, it is now a reserved keyword.
     * Default type parameters have been implemented, but are feature gated.
-    * Borrowed variables through captures in closures are now considered soundly.
+    * Borrowed variables through captures in closures are now considered
+      soundly.
     * `extern mod` is now `extern crate`
     * The `Freeze` trait has been removed.
     * The `Share` trait has been added for types that can be shared among
@@ -4187,8 +4200,8 @@ Version 0.10 (2014-04-03)
     * std: The `vec` module has been renamed to `slice`.
     * std: A new vector type, `Vec<T>`, has been added in preparation for DST.
       This will become the only growable vector in the future.
-    * std: `std::io` now has more public-reexports. Types such as `BufferedReader`
-      are now found at `std::io::BufferedReader` instead of
+    * std: `std::io` now has more public-reexports. Types such as
+      `BufferedReader` are now found at `std::io::BufferedReader` instead of
       `std::io::buffered::BufferedReader`.
     * std: `print` and `println` are no longer in the prelude, the `print!` and
       `println!` macros are intended to be used instead.
@@ -4210,7 +4223,8 @@ Version 0.10 (2014-04-03)
       can be found on the wiki's style guide.
     * std: `eof()` has been removed from the `Reader` trait. Specific types may
       still implement the function.
-    * std: Networking types are now cloneable to allow simultaneous reads/writes.
+    * std: Networking types are now cloneable to allow simultaneous
+      reads/writes.
     * std: `assert_approx_eq!` has been removed
     * std: The `e` and `E` formatting specifiers for floats have been added to
       print them in exponential notation.
@@ -4331,24 +4345,25 @@ Version 0.9 (2014-01-09)
       * Comments may be nested.
       * Values automatically coerce to trait objects they implement, without
         an explicit `as`.
-      * Enum discriminants are no longer an entire word but as small as needed to
-        contain all the variants. The `repr` attribute can be used to override
-        the discriminant size, as in `#[repr(int)]` for integer-sized, and
-        `#[repr(C)]` to match C enums.
+      * Enum discriminants are no longer an entire word but as small as needed
+        to contain all the variants. The `repr` attribute can be used to
+        override the discriminant size, as in `#[repr(int)]` for integer-sized,
+        and `#[repr(C)]` to match C enums.
       * Non-string literals are not allowed in attributes (they never worked).
       * The FFI now supports variadic functions.
       * Octal numeric literals, as in `0o7777`.
-      * The `concat!` syntax extension performs compile-time string concatenation.
+      * The `concat!` syntax extension performs compile-time string
+        concatenation.
       * The `#[fixed_stack_segment]` and `#[rust_stack]` attributes have been
         removed as Rust no longer uses segmented stacks.
       * Non-ascii identifiers are feature-gated (`#[feature(non_ascii_idents)]`).
-      * Ignoring all fields of an enum variant or tuple-struct is done with `..`,
-        not `*`; ignoring remaining fields of a struct is also done with `..`,
-        not `_`; ignoring a slice of a vector is done with `..`, not `.._`.
+      * Ignoring all fields of an enum variant or tuple-struct is done with
+        `..`, not `*`; ignoring remaining fields of a struct is also done with
+        `..`, not `_`; ignoring a slice of a vector is done with `..`, not `.._`.
       * `rustc` supports the "win64" calling convention via `extern "win64"`.
       * `rustc` supports the "system" calling convention, which defaults to the
-        preferred convention for the target platform, "stdcall" on 32-bit Windows,
-        "C" elsewhere.
+        preferred convention for the target platform, "stdcall" on 32-bit
+        Windows, "C" elsewhere.
       * The `type_overflow` lint (default: warn) checks literals for overflow.
       * The `unsafe_block` lint (default: allow) checks for usage of `unsafe`.
       * The `attribute_usage` lint (default: warn) warns about unknown

src/doc/book/src/SUMMARY.md

@@ -53,7 +53,8 @@
     * [FFI](ffi.md)
     * [Borrow and AsRef](borrow-and-asref.md)
     * [Release Channels](release-channels.md)
-    * [Using Rust without the standard library](using-rust-without-the-standard-library.md)
+    * [Using Rust without the standard
+      library](using-rust-without-the-standard-library.md)
     * [Procedural Macros (and custom derive)](procedural-macros.md)
 * [Glossary](glossary.md)
 * [Syntax Index](syntax-index.md)

src/doc/book/src/strings.md

@@ -106,8 +106,8 @@ Usually, access to a vector with `[]` is very fast. But, because each character
 in a UTF-8 encoded string can be multiple bytes, you have to walk over the
 string to find the nᵗʰ letter of a string. This is a significantly more
 expensive operation, and we don’t want to be misleading. Furthermore, ‘letter’
-isn’t something defined in Unicode, exactly. We can choose to look at a string as
-individual bytes, or as codepoints:
+isn’t something defined in Unicode, exactly. We can choose to look at a string
+as individual bytes, or as codepoints:
 
 ```rust
 let hachiko = "忠犬ハチ公";
@@ -163,8 +163,8 @@ let hachi = &dog[0..2];
 with this error:
 
 ```text
-thread 'main' panicked at 'byte index 2 is not a char boundary; it is inside '忠'
-(bytes 0..3) of `忠犬ハチ公`'
+thread 'main' panicked at 'byte index 2 is not a char boundary; it is inside
+'忠' (bytes 0..3) of `忠犬ハチ公`'
 ```
 
 ## Concatenation

src/doc/book/src/traits.md

@@ -23,7 +23,8 @@ impl Circle {
 [methodsyntax]: method-syntax.html
 
 Traits are similar, except that we first define a trait with a method
-signature, then implement the trait for a type. In this example, we implement the trait `HasArea` for `Circle`:
+signature, then implement the trait for a type. In this example, we implement
+the trait `HasArea` for `Circle`:
 
 ```rust
 struct Circle {
@@ -78,8 +79,8 @@ impl HasArea for Circle {
 ## Trait bounds on generic functions
 
 Traits are useful because they allow a type to make certain promises about its
-behavior. Generic functions can exploit this to constrain, or [bound][bounds], the types they
-accept. Consider this function, which does not compile:
+behavior. Generic functions can exploit this to constrain, or [bound][bounds],
+the types they accept. Consider this function, which does not compile:
 
 [bounds]: glossary.html#bounds
 
@@ -427,13 +428,16 @@ fn inverse<T>(x: i32) -> T
 ```
 
 This shows off the additional feature of `where` clauses: they allow bounds
-on the left-hand side not only of type parameters `T`, but also of types (`i32` in this case). In this example, `i32` must implement
+on the left-hand side not only of type parameters `T`, but also of types
+(`i32` in this case). In this example, `i32` must implement
 `ConvertTo<T>`. Rather than defining what `i32` is (since that's obvious), the
 `where` clause here constrains `T`.
 
 # Default methods
 
-A default method can be added to a trait definition if it is already known how a typical implementor will define a method. For example, `is_invalid()` is defined as the opposite of `is_valid()`:
+A default method can be added to a trait definition if it is already known how
+a typical implementor will define a method. For example, `is_invalid()` is
+defined as the opposite of `is_valid()`:
 
 ```rust
 trait Foo {
@@ -443,7 +447,9 @@ trait Foo {
 }
 ```
 
-Implementors of the `Foo` trait need to implement `is_valid()` but not `is_invalid()` due to the added default behavior. This default behavior can still be overridden as in:
+Implementors of the `Foo` trait need to implement `is_valid()` but not
+`is_invalid()` due to the added default behavior. This default behavior can
+still be overridden as in:
 
 ```rust
 # trait Foo {

src/doc/book/src/unsized-types.md

@@ -2,9 +2,9 @@
 
 Most types have a particular size, in bytes, that is knowable at compile time.
 For example, an `i32` is thirty-two bits big, or four bytes. However, there are
-some types which are useful to express, but do not have a defined size. These are
-called ‘unsized’ or ‘dynamically sized’ types. One example is `[T]`. This type
-represents a certain number of `T` in sequence. But we don’t know how many
+some types which are useful to express, but do not have a defined size. These
+are called ‘unsized’ or ‘dynamically sized’ types. One example is `[T]`. This
+type represents a certain number of `T` in sequence. But we don’t know how many
 there are, so the size is not known.
 
 Rust understands a few of these types, but they have some restrictions. There

src/doc/book/src/variable-bindings.md

@@ -241,10 +241,10 @@ println!("{}", x); // Prints "42".
 Shadowing and mutable bindings may appear as two sides of the same coin, but
 they are two distinct concepts that can't always be used interchangeably. For
 one, shadowing enables us to rebind a name to a value of a different type. It
-is also possible to change the mutability of a binding. Note that shadowing a 
+is also possible to change the mutability of a binding. Note that shadowing a
 name does not alter or destroy the value it was bound to, and the value will
-continue to exist until it goes out of scope, even if it is no longer accessible
-by any means.
+continue to exist until it goes out of scope, even if it is no longer
+accessible by any means.
 
 ```rust
 let mut x: i32 = 1;

src/doc/book/src/vectors.md

@@ -115,9 +115,10 @@ for i in v {
 }
 ```
 
-Note: You cannot use the vector again once you have iterated by taking ownership of the vector.
-You can iterate the vector multiple times by taking a reference to the vector whilst iterating.
-For example, the following code does not compile.
+Note: You cannot use the vector again once you have iterated by taking
+ownership of the vector. You can iterate the vector multiple times by taking a
+reference to the vector whilst iterating. For example, the following code does
+not compile.
 
 ```rust,ignore
 let v = vec![1, 2, 3, 4, 5];