diff --git a/docs/types/never.md b/docs/types/never.md
index 220a090db..d55641f74 100644
--- a/docs/types/never.md
+++ b/docs/types/never.md
@@ -74,7 +74,7 @@ const failExpression = function(message: string) {
 };
 ```
 
-Of course you can fix it by an explict annotation: 
+Of course you can fix it by an explicit annotation: 
 
 ```ts
 function failDeclaration(message: string): never {
@@ -82,7 +82,7 @@ function failDeclaration(message: string): never {
 }
 ```
 
-Key reason is backword compatability with real world JavaScript code: 
+Key reason is backword compatibility with real world JavaScript code: 
 
 ```ts
 class Base {
@@ -100,7 +100,7 @@ class Derived extends Base {
 
 If `Base.overrideMe` . 
 
-> Real world TypeScript can overcome this with `abstract` functions but this inferrence is maintained for compatability.
+> Real world TypeScript can overcome this with `abstract` functions but this inferrence is maintained for compatibility.
 
 <!--
 PR: https://github.com/Microsoft/TypeScript/pull/8652
diff --git a/docs/types/type-compatibility.md b/docs/types/type-compatibility.md
index 9aab13724..42c24049c 100644
--- a/docs/types/type-compatibility.md
+++ b/docs/types/type-compatibility.md
@@ -207,7 +207,7 @@ status = num; // OKAY
 num = status; // OKAY
 ```
 
-* Enum values from different enum types are considered incompatible. This makes enums useable *nominally* (as opposed to structurally)
+* Enum values from different enum types are considered incompatible. This makes enums usable *nominally* (as opposed to structurally)
 
 ```ts
 enum Status { Ready, Waiting };