---

yaml
---
r: 236031
b: refs/heads/stable
c: 9c87b1f
h: refs/heads/master
i:
  236029: f1827fc
  236027: 18f4972
  236023: cefe885
  236015: 6a94029
  235999: 6e8cc28
  235967: 029c54d
  235903: 68595d7
  235775: 072bc97
  235519: a8b5df3
v: v3

Author: Manishearth

[refs]

@@ -29,7 +29,7 @@ refs/heads/tmp: afae2ff723393b3ab4ccffef6ac7c6d1809e2da0
 refs/tags/1.0.0-alpha.2: 4c705f6bc559886632d3871b04f58aab093bfa2f
 refs/tags/homu-tmp: f859507de8c410b648d934d8f5ec1c52daac971d
 refs/tags/1.0.0-beta: 8cbb92b53468ee2b0c2d3eeb8567005953d40828
-refs/heads/stable: 2d5c1bbee053ff2398f42cc7229738f33f78ff4b
+refs/heads/stable: 9c87b1f8dbc3105e3e9338b169d0884ce7a902af
 refs/tags/1.0.0: 55bd4f8ff2b323f317ae89e254ce87162d52a375
 refs/tags/1.1.0: bc3c16f09287e5545c1d3f76b7abd54f2eca868b
 refs/tags/1.2.0: f557861f822c34f07270347b94b5280de20a597e

branches/stable/conversions.md

@@ -210,10 +210,10 @@ expression, `e as U2` is not necessarily so (in fact it will only be valid if
 For numeric casts, there are quite a few cases to consider:
 
 * casting between two integers of the same size (e.g. i32 -> u32) is a no-op
-* casting from a larger integer to a smaller integer (e.g. u32 -> u8) will truncate
-* casting from a smaller integer to a larger integer (e.g. u8 -> u32) will
-    * zero-extend if the source is unsigned
-    * sign-extend if the source is signed
+* casting from a smaller integer to a bigger integer (e.g. u32 -> u8) will truncate
+* casting from a larger integer to a smaller integer (e.g. u8 -> u32) will
+    * zero-extend if the target is unsigned
+    * sign-extend if the target is signed
 * casting from a float to an integer will round the float towards zero
     * **NOTE: currently this will cause Undefined Behaviour if the rounded
       value cannot be represented by the target integer type**. This is a bug

branches/stable/data.md

@@ -236,7 +236,7 @@ one.
 This is the most important `repr`. It has fairly simple intent: do what C does.
 The order, size, and alignment of fields is exactly what you would expect from
 C or C++. Any type you expect to pass through an FFI boundary should have `repr(C)`,
-as C is the lingua-franca of the programming world. However this is also necessary
+as C is the lingua-franca of the programming world. This is also necessary
 to soundly do more elaborate tricks with data layout such as reintepretting values
 as a different type.
 

branches/stable/intro.md

@@ -230,7 +230,7 @@ struct Vec<T> {
 }
 
 // Note this implementation does not correctly handle zero-sized types.
-// We currently live in a nice imaginary world of only positive fixed-size
+// We currently live in a nice imaginary world of only postive fixed-size
 // types.
 impl<T> Vec<T> {
     fn push(&mut self, elem: T) {