docs: fix a few things in a11y doc

Change-Id: I142b0b4498cf6d19655ad1ccc2066e59c39e75a6

1 files changed, 10 insertions, 11 deletions

diff --git a/docs/html/guide/practices/design/accessibility.jd b/docs/html/guide/practices/design/accessibility.jd
index dec815f..4590682 100644
--- a/docs/html/guide/practices/design/accessibility.jd
+++ b/docs/html/guide/practices/design/accessibility.jd
@@ -45,17 +45,16 @@ href="{@docRoot}resources/samples/AccessibilityService/index.html">Accessibility
 
 
 <p>Many Android users have disabilities that require them to interact with their Android devices in
-different ways.  These include users who have visual, physical or aging-related disabilities that
+different ways.  These include users who have visual, physical or age-related disabilities that
 prevent them from fully using or seeing a touchscreen.</p>
 
 <p>Android provides an accessibility layer that helps these users navigate their Android-powered
 devices more easily.  Android's accessibility services provide things like text-to-speech, haptic
-feedback and trackball/D-pad navigation that augment the user experience.</p>
+feedback, and trackball/d-pad navigation that augment the user experience.</p>
 
 <p>Your application should follow the guidelines in this document to ensure that it provides a
-good experience for users with disabilities.</p>
-
-<p>Following these two basic rules will solve most access-related problems:</p>
+good experience for users with disabilities. Following these two basic rules will solve most
+access-related problems:</p>
 
 <ul>
 <li>Make all of your user interface controls accessible with a trackball or directional
@@ -72,7 +71,7 @@ widgets using the <a href="{@docRoot}reference/android/view/View#attr_android:co
 <p>Many Android devices come with some sort of directional controller, such as:</p>
 <ul>
 <li>A clickable trackball that users can move in any direction</li>
-<li>A clickable D-pad that allows users to navigate in four directions.</li>
+<li>A clickable d-pad that allows users to navigate in four directions.</li>
 <li>Arrow keys and an OK button that’s equivalent to clicking a trackball or d-pad.</li>
 </ul>
 
@@ -110,22 +109,22 @@ layout file by setting the <a href="{@docRoot}reference/android/view/View#attr_a
 
 <p>When the user navigates in any direction using the directional controls, focus is passed from one
 view to another, as determined by the focus ordering. The ordering of the focus movement is based on
-an algorithm which finds the nearest neighbor in a given direction. In rare cases, the default
+an algorithm that finds the nearest neighbor in a given direction. In rare cases, the default
 algorithm may not match the order that you intended for your UI. In these situations, you can
 provide explicit overrides to the ordering using the following XML attributes in the layout
 file:</p>
 
 <dl>
- <dt><a href="{@docRoot}reference/android/view/View#attr_android:nextFocusDown"
+ <dt><a href="{@docRoot}reference/android/view/View.html#attr_android:nextFocusDown"
 >{@code android:nextFocusDown}</a></dt>
   <dd>Defines the next view to receive focus when the user navigates down.</dd>
- <a><a href="{@docRoot}reference/android/view/View#attr_android:nextFocusLeft"
+ <a><a href="{@docRoot}reference/android/view/View.html#attr_android:nextFocusLeft"
 >{@code android:nextFocusLeft}</a></dt>
   <dd>Defines the next view to receive focus when the user navigates left.</dd>
- <dt><a href="{@docRoot}reference/android/view/View#attr_android:nextFocusRight"
+ <dt><a href="{@docRoot}reference/android/view/View.html#attr_android:nextFocusRight"
 >{@code android:nextFocusRight}</a></dt>
   <dd>Defines the next view to receive focus when the user navigates right.</dd>
- <dt><a href="{@docRoot}reference/android/view/View#attr_android:nextFocusUp"
+ <dt><a href="{@docRoot}reference/android/view/View.html#attr_android:nextFocusUp"
 >{@code android:nextFocusUp}</a></dt>
   <dd>Defines the next view to receive focus when the user navigates up.</dd>
 </dl>