Tweaked some phrasing for clarity

Author: AloeareV

src/type-coercions.md

@@ -1,8 +1,8 @@
 # Type coercions
 
-**Type coercions** are implicit changes of the type of a value. They happen
-automatically at specific locations and are highly restricted in what types
-actually coerce.
+**Type coercions** are implicit operations that change the type of a value.
+They happen automatically at specific locations and are highly restricted in 
+what types actually coerce.
 
 Coercions are originally defined in [RFC 401] and expanded upon in [RFC 1558].
 
@@ -21,7 +21,7 @@ sites are:
    let _: &i8 = &mut 42;
    ```
 
-* `static` and `const` items (similar to `let` statements).
+* `static` and `const` item declarations (similar to `let` statements).
 
 * Arguments for function calls
 
@@ -52,19 +52,20 @@ sites are:
       Foo { x: &mut 42 };
   }
   ```
+  
+  (Note that lifetime specifiers on `struct Foo` have been omitted for brevity.)
 
 * Function results–either the final line of a block if it is not
   semicolon-terminated or any expression in a `return` statement
 
-  For example, `x` is coerced to have type `&dyn Binary` in the following:
+  For example, `x` is coerced to have type `&dyn Display` in the following:
 
   ```rust
-  fn foo(x: &u32) -> &dyn Binary {
+  fn foo(x: &u32) -> &dyn Display {
       x
   }
   ```
-The [as] keyword can also be used to perform explicit type coersion, as well as
-some additional casts.
+* The [as] type cast operator can also explicitly perform type coersion.
 
 
 If the expression in one of these coercion sites is a coercion-propagating