Apply nits

Author: ldm0

src/type-coercions.md

@@ -210,7 +210,7 @@ let baz = [a, b, c];
 ```
 
 In this example, both `foo` and `bar` have the type
-`LubCoerce(typeof(a), typeof(a), typeof(c))` and `baz` have the type
+`LubCoerce(typeof(a), typeof(a), typeof(c))` and `baz` has the type
 `[LubCoerce(typeof(a), typeof(b), typeof(c)); 3]`.
 
 LUB coercion is performed by the following algorithm:
@@ -242,19 +242,17 @@ LubCoerce(vars...):
 
 LUB coercion has the following properties:
 
-1. Order independent: e.g. `LubCoerce(ty0, ty1, ty2, ty3)` equals to
-    `LubCoerce(ty1, ty0, ty4, ty3)`.
-2. `LubCoerce(ty0, ty1, ty2, ...)` equals to
+1. `LubCoerce(ty0, ty1, ty2, ...)` equals to
     `LubCoerce(LubCoerce(ty0, ty1), ty2, ...)`
-3. `LubCoerce(ty0, ty1) == Some(ty2)` means both `ty0` and `ty1` can be coerced
+2. `LubCoerce(ty0, ty1) == Some(ty2)` means both `ty0` and `ty1` can be coerced
     to `ty2`.
 
-Note the feature No. 3, it uses the word "means" rather than "if and only if".
+Note the feature No. 2, it uses the word "means" rather than "if and only if".
 That's because currently if `ty0` and `ty1` can be coerced to `ty2` and
-unfortunately `ty2` equals to neither `ty0` nor `ty1`, there are only one
+if `ty2` equals to neither `ty0` nor `ty1`, there is only one
 special situation where we can get `LubCoerce(ty0, ty1) == Some(ty2)`:
 `LubCoerce((FnDef | Closure), (FnDef | Closure)) == Some(FnPtr)` (where Closure
-is non-capturing). You can check it with the pseudo code.
+is non-capturing).
 
 When an expression that performs LUB coercion has an expected type, the
 expected type is added to the list of types the coercion operates on. So,