commit 8a52f3d6836aec401034a6afa9443e68f7fde662
author Scott Main <smain@google.com> Wed Jul 28 14:14:40 2010 -0700
committer Scott Main <smain@google.com> Wed Jul 28 14:15:26 2010 -0700
tree 5de6c1f02f5a99601f664eccf6fa1ce43d918aea
parent 86c035f0d176be9cb06b1e4f2390c25701417586

fix markup error
bug:2871538

Change-Id: I7ab4a9bb722ee8b3e5d740f79143776be8b56a6f

docs/html/guide/practices/ui_guidelines/activity_task_design.jd

diff --git a/docs/html/guide/practices/ui_guidelines/activity_task_design.jd b/docs/html/guide/practices/ui_guidelines/activity_task_design.jd
index 05f61be..c8d241c 100644
--- a/docs/html/guide/practices/ui_guidelines/activity_task_design.jd
+++ b/docs/html/guide/practices/ui_guidelines/activity_task_design.jd
@@ -256,8 +256,8 @@
   to be able go to a subsequent screen B and then use the BACK key to go
   back to screen A, then the screen A needs to be implemented as an
   activity. The one exception to this rule is if your application 
-  <a href=#taking_over_back_key title="takes control of the BACK key"
-  takes control of the BACK key</a> and manages the navigation itself.
+  <a href="#taking_over_back_key">takes control of the BACK key</a> and manages the navigation
+itself.
 </p>