summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
author kopriva <kopriva@google.com> 2018-09-17 11:35:13 -0700
committer kopriva <kopriva@google.com> 2018-09-17 11:35:13 -0700
commitfc3949e0992f52bd2f3f2be41b51a8b3ef786d9b (patch)
tree982e31c41fd68992edffd4d1a2f64511ab86cacb
parent3667b7122557ef15fcacf267133bdd3eae4c0737 (diff)
docs: bug 36997358, typo 'than an'
Test: make ds-docs Bug: 36997358 Change-Id: I11a5fcbd76638c7d6b060c0852268efa9e37a7fe Exempt-From-Owner-Approval: Docs-only change
-rw-r--r--core/java/android/app/Activity.java4
1 files changed, 2 insertions, 2 deletions
diff --git a/core/java/android/app/Activity.java b/core/java/android/app/Activity.java
index 68e8a52a9c24..f765620a2eb9 100644
--- a/core/java/android/app/Activity.java
+++ b/core/java/android/app/Activity.java
@@ -544,12 +544,12 @@ import java.util.List;
* <a name="SavingPersistentState"></a>
* <h3>Saving Persistent State</h3>
*
- * <p>There are generally two kinds of persistent state than an activity
+ * <p>There are generally two kinds of persistent state that an activity
* will deal with: shared document-like data (typically stored in a SQLite
* database using a {@linkplain android.content.ContentProvider content provider})
* and internal state such as user preferences.</p>
*
- * <p>For content provider data, we suggest that activities use a
+ * <p>For content provider data, we suggest that activities use an
* "edit in place" user model. That is, any edits a user makes are effectively
* made immediately without requiring an additional confirmation step.
* Supporting this model is generally a simple matter of following two rules:</p>