diff --git a/public/docs/ts/latest/guide/displaying-data.jade b/public/docs/ts/latest/guide/displaying-data.jade
index 20587dbf12..3926087275 100644
--- a/public/docs/ts/latest/guide/displaying-data.jade
+++ b/public/docs/ts/latest/guide/displaying-data.jade
@@ -58,7 +58,7 @@ figure.image-display
 .l-sub-section
   :marked
     More precisely, the re-display occurs after some kind of asynchronous event related to
-    the view such as a keystroke, a timer completion, or an asynch `XHR` response.
+    the view such as a keystroke, a timer completion, or an async `XHR` response.
     We don't have those in this sample.
     But then the properties aren't changing on their own either. For the moment we must operate on faith.
 :marked
diff --git a/public/docs/ts/latest/guide/glossary.jade b/public/docs/ts/latest/guide/glossary.jade
index e15657bfc7..385eea25a4 100644
--- a/public/docs/ts/latest/guide/glossary.jade
+++ b/public/docs/ts/latest/guide/glossary.jade
@@ -585,11 +585,11 @@
     calls to remote servers.
 
     Zones intercept all of these activities and give a "zone client" the opportunity
-    to take action before and after the asynch activity completes.
+    to take action before and after the async activity completes.
 
     Angular runs our application in a zone where it can respond to
     asynchronous events by checking for data changes and updating
     the information it displays via [data binding](#data-binding).
 
     Learn more about zones in this
-    [Brian Ford video](https://www.youtube.com/watch?v=3IqtmUscE_U).
\ No newline at end of file
+    [Brian Ford video](https://www.youtube.com/watch?v=3IqtmUscE_U).