From 8a52f3d6836aec401034a6afa9443e68f7fde662 Mon Sep 17 00:00:00 2001
From: Scott Main <smain@google.com>
Date: Wed, 28 Jul 2010 14:14:40 -0700
Subject: fix markup error bug:2871538

Change-Id: I7ab4a9bb722ee8b3e5d740f79143776be8b56a6f
---
 docs/html/guide/practices/ui_guidelines/activity_task_design.jd | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'docs/html/guide')

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 @@ page.title=Activity and Task Design Guidelines
   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>
 
 
-- 
cgit v1.1