diff --git a/docs/html/guide/topics/fundamentals/tasks-and-back-stack.jd b/docs/html/guide/topics/fundamentals/tasks-and-back-stack.jd
index bd542bd292f38..cfed7428a04d5 100644
--- a/docs/html/guide/topics/fundamentals/tasks-and-back-stack.jd
+++ b/docs/html/guide/topics/fundamentals/tasks-and-back-stack.jd
@@ -10,8 +10,8 @@ parent.link=activities.html
All activities belong to a task
A task contains a collection of activities in the order in which the user interacts with
them
- Tasks can move to the background and retain the state of each activity in order for the user
-to perform other tasks without loosing their work
+ Tasks can move to the background and retain the state of each activity in order for users
+to perform other tasks without losing their work
In this document
@@ -301,7 +301,7 @@ activity at the top of the back stack is not an existing instance of th
and D on top (the stack is A-B-C-D; D is on top). An intent arrives for an activity of type D.
If D has the default {@code "standard"} launch mode, a new instance of the class is launched and the
stack becomes A-B-C-D-D. However, if D's launch mode is {@code "singleTop"}, the existing instance
-of D is deliverd the intent through {@link
+of D receives the intent through {@link
android.app.Activity#onNewIntent onNewIntent()}, because it's at the top of the stack—the
stack remains A-B-C-D. However, if an intent arrives for an activity of type B, then a new
instance of B is added to the stack, even if its launch mode is {@code "singleTop"}.
@@ -358,7 +358,7 @@ discussed more.
Note: The behaviors that you specify for your activity with the {@code launchMode} attribute
-can be overriden by flags included with the intent that start your activity, as discussed in the
+can be overridden by flags included with the intent that start your activity, as discussed in the
next section.