From 9525f2a72e2786f1b53927878dd8234859ea5c39 Mon Sep 17 00:00:00 2001 From: Mark Doliner Date: Thu, 2 Jan 2014 11:17:47 -0800 Subject: Miscellaneous small documentation fixes. Most of these I noticed on my own. The change to docs/html/tools/testing/testing_ui.jd is mentioned in a bug report: https://code.google.com/p/android/issues/detail?id=56324 Signed-off-by: Mark Doliner --- docs/html/guide/topics/manifest/activity-element.jd | 2 +- docs/html/tools/testing/testing_ui.jd | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/html') diff --git a/docs/html/guide/topics/manifest/activity-element.jd b/docs/html/guide/topics/manifest/activity-element.jd index 8df1fdf..eabfa60 100644 --- a/docs/html/guide/topics/manifest/activity-element.jd +++ b/docs/html/guide/topics/manifest/activity-element.jd @@ -580,7 +580,7 @@ This attribute was introduced in API Level 3. android:name attribute.

The system reads this attribute to determine which activity should be started when - the use presses the Up button in the action bar. The system can also use this information to + the user presses the Up button in the action bar. The system can also use this information to synthesize a back stack of activities with {@link android.app.TaskStackBuilder}.

To support API levels 4 - 16, you can also declare the parent activity with a {@code diff --git a/docs/html/tools/testing/testing_ui.jd b/docs/html/tools/testing/testing_ui.jd index 701415e..4318a21 100644 --- a/docs/html/tools/testing/testing_ui.jd +++ b/docs/html/tools/testing/testing_ui.jd @@ -90,7 +90,7 @@ Functional or black-box UI testing does not require testers to know the internal alt="User interface of uiautomatorviewer tool" height="327px" id="figure1"/>

- Figure 1. The {@code uiautomatorviewer} showing the captured interface of a test deviice. + Figure 1. The {@code uiautomatorviewer} showing the captured interface of a test device.

To analyze the UI components of the application that you want to test:

-- cgit v1.1