Index: doc/proposals/references.md
===================================================================
--- doc/proposals/references.md	(revision 5c6afcdba6e3011ac15b8a95cf89ca0c694d9818)
+++ doc/proposals/references.md	(revision b947fb2e40ff1eb3c74f2ca17397c8a24c9a2a9c)
@@ -17,5 +17,5 @@
 derived rvalue types such as pointer types may include qualifiers; 
 `const int *` is a distinct type from `int *`, though the latter is safely 
-convertable to the former. 
+convertible to the former. 
 In general, any number of qualifiers can be safely added to the 
 pointed-to-type of a pointer type, e.g. `int *` converts safely to 
@@ -23,5 +23,5 @@
 `const volatile int *`.
 
-Since lvalues are precicely "addressable objects", in C, only lvalues can be 
+Since lvalues are precisely "addressable objects", in C, only lvalues can be 
 used as the operand of the `&` address-of operator. 
 Similarly, only modifiable lvalues may be used as the assigned-to 
@@ -147,10 +147,10 @@
 call "lvalue of type `T`" as `T&`. 
 There's also an obvious argument that lvalues of a (possibly-qualified) type 
-`T` should be convertable to references of type `T`, where `T` is also 
+`T` should be convertible to references of type `T`, where `T` is also 
 so-qualified (e.g. lvalue `int` to `int&`, lvalue `const char` to 
 `const char&`). 
 By similar arguments to pointer types, qualifiers should be addable to the 
 referred-to type of a reference (e.g. `int&` to `const int&`). 
-As a note, since pointer arithmetic is explictly not defined on `T&`, 
+As a note, since pointer arithmetic is explicitly not defined on `T&`, 
 `restrict T&` should be allowable and would have alias-analysis rules that 
 are actually comprehensible to mere mortals.