From 5d3b0c7a7a74c18879c4a98970cab4be19ffd37f Mon Sep 17 00:00:00 2001 From: Roman Nurik Date: Mon, 23 Jan 2012 11:23:46 -0800 Subject: [PATCH] docs: Android Design typo and grammar fixes Change-Id: Ice0eb216c985183e2f41c287ea5d1cc7af1f31f2 --- docs/html/design/get-started/ui-overview.html | 15 ++++++++------- docs/html/design/patterns/app-structure.html | 6 +++--- docs/html/design/patterns/navigation.html | 13 +++++++------ docs/html/design/patterns/notifications.html | 2 +- 4 files changed, 19 insertions(+), 17 deletions(-) diff --git a/docs/html/design/get-started/ui-overview.html b/docs/html/design/get-started/ui-overview.html index b08c7430827b2..bd5ff9c84bac5 100644 --- a/docs/html/design/get-started/ui-overview.html +++ b/docs/html/design/get-started/ui-overview.html @@ -153,12 +153,12 @@ recently used app at the bottom.

-

UI Bars

+

System Bars

-

The UI bars are screen areas dedicated to the display of notifications, communication of device -status, and device navigation. Typically the UI bars are displayed concurrently with your app. Apps -that display immersive content, such as movies or images, can temporarily hide the UI bars to allow -the user to enjoy full screen content without distraction.

+

The system bars are screen areas dedicated to the display of notifications, communication of device +status, and device navigation. Typically the system bars are displayed concurrently with your app. +Apps that display immersive content, such as movies or images, can temporarily hide the system bars +to allow the user to enjoy full screen content without distraction.

@@ -177,8 +177,9 @@ the user to enjoy full screen content without distraction.

Recents, and also displays a menu for apps written for Android 2.3 or earlier.

  • -

    System Bar

    -

    Combines the status and navigation bars for display on tablet form factors.

    +

    Combined Bar

    +

    On tablet form factors the status and navigation bars are combined into a single bar at the + bottom of the screen.

    • diff --git a/docs/html/design/patterns/app-structure.html b/docs/html/design/patterns/app-structure.html index b87f4021879eb..fb9205b4bf813 100644 --- a/docs/html/design/patterns/app-structure.html +++ b/docs/html/design/patterns/app-structure.html @@ -159,9 +159,9 @@ layouts that are visually engaging and appropriate for the data type and screen
    - Market's start screen primarily allows navigation into the stores for Apps, Music, Books, and - Games. It is also enriched with tailored recommendations and promotions that surface content - of interest to the user. Search is readily available from the action bar. + Market's start screen primarily allows navigation into the stores for Apps, Music, Books, + Movies and Games. It is also enriched with tailored recommendations and promotions that + surface content of interest to the user. Search is readily available from the action bar.
    diff --git a/docs/html/design/patterns/navigation.html b/docs/html/design/patterns/navigation.html index aabfc39c83738..cad36828ada69 100644 --- a/docs/html/design/patterns/navigation.html +++ b/docs/html/design/patterns/navigation.html @@ -131,7 +131,7 @@ return the user to the Home screen, or even to a different application.

    The Back key also supports a few behaviors not directly tied to screen-to-screen navigation:

    Navigation Within Your App

    @@ -189,18 +189,19 @@ screen widget can bypass the Inbox screen, taking the user directly to a convers

    App-to-app navigation

    When navigating deep into your app's hierarchy directly from another app via an intent, Back will return to the referring app.

    -

    The Up button is handled is follows: +

    The Up button is handled as follows: - If the destination screen is typically reached from one particular screen within your app, Up should navigate to that screen. - Otherwise, Up should navigate to the topmost ("Home") screen of your app.

    -

    For example, after choosing to share a book being view in Market, the user navigates directly to the -Gmail's compose screen. From there, Up returns to the Inbox (which happens to be both the typical -referrer to compose, as well as the topmost screen of the app), while Back returns to Market.

    +

    For example, after choosing to share a book being viewed in Market, the user navigates directly to +Gmail's compose screen. From there, Up returns to the Inbox (which happens to be both the +typical referrer to compose, as well as the topmost screen of the app), while Back returns to +Market.

    System-to-app navigation

    -

    If the your app was reached via the system mechanisms of notifications or home screen widgets, Up +

    If your app was reached via the system mechanisms of notifications or home screen widgets, Up behaves as described for app-to-app navigation, above.

    For the Back key, you should make navigation more predictably by inserting into the task's back stack the complete upward navigation path to the app's topmost screen. This way, a user who has diff --git a/docs/html/design/patterns/notifications.html b/docs/html/design/patterns/notifications.html index acec306472630..c5045aed9e772 100644 --- a/docs/html/design/patterns/notifications.html +++ b/docs/html/design/patterns/notifications.html @@ -200,7 +200,7 @@ stacked (see Stacked notifications below) and references multiple items the user is taken to a hierarchy level below your app's top-level, insert navigation into your app's back stack to allow them to navigate to your app's top level using the system back key. For more information, see the chapter on System-to-app navigation in the -Navigation design pattern.

    +Navigation design pattern.

    Timestamps for time sensitive events

    By default, standard Android notifications include a timestamp in the upper right corner. Consider whether the timestamp is valuable in the context of your notification. If the timestamp is not