summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorkopriva <kopriva@google.com>2018-03-19 14:13:08 -0700
committerkopriva <kopriva@google.com>2018-03-19 14:25:30 -0700
commit4dddc63ee7c09f5ef243591700502160c08dc337 (patch)
treec3b291fe1e9d274918f03611f7d69baa9d7a16a5
parent3b0285794a8b8691c6ebc2af360a5a8e2d094a4b (diff)
docs: fixing typo, bug 36909553
Test: make ds-docs Bug: 36909553 Change-Id: I6e6842fe555690d97b954c370b777b25c6f5e54e
-rw-r--r--core/java/android/app/Activity.java8
1 files changed, 4 insertions, 4 deletions
diff --git a/core/java/android/app/Activity.java b/core/java/android/app/Activity.java
index 8dc558ccf755..c349ab3c4abe 100644
--- a/core/java/android/app/Activity.java
+++ b/core/java/android/app/Activity.java
@@ -640,13 +640,13 @@ import java.util.List;
* <a name="ProcessLifecycle"></a>
* <h3>Process Lifecycle</h3>
*
- * <p>The Android system attempts to keep application process around for as
+ * <p>The Android system attempts to keep an application process around for as
* long as possible, but eventually will need to remove old processes when
- * memory runs low. As described in <a href="#ActivityLifecycle">Activity
+ * memory runs low. As described in <a href="#ActivityLifecycle">Activity
* Lifecycle</a>, the decision about which process to remove is intimately
- * tied to the state of the user's interaction with it. In general, there
+ * tied to the state of the user's interaction with it. In general, there
* are four states a process can be in based on the activities running in it,
- * listed here in order of importance. The system will kill less important
+ * listed here in order of importance. The system will kill less important
* processes (the last ones) before it resorts to killing more important
* processes (the first ones).
*