From c39439811b6b0189c3a3d3772f3fd30eb9d2c159 Mon Sep 17 00:00:00 2001
From: Andrew Solovay <asolovay@google.com>
Date: Thu, 10 Mar 2016 16:35:15 -0800
Subject: [PATCH] docs: Quick fix to broken link

bug: 27595415
Change-Id: I6e665d5d4d06914b5b58c64d6fb06e59850db902
---
 docs/html/preview/features/notification-updates.jd | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/html/preview/features/notification-updates.jd b/docs/html/preview/features/notification-updates.jd
index f234831856652..d3042ada1f259 100644
--- a/docs/html/preview/features/notification-updates.jd
+++ b/docs/html/preview/features/notification-updates.jd
@@ -183,7 +183,7 @@ When the user responds via {@link android.support.v4.app.RemoteInput},
 
 <p>Android N provides developers with a new way to represent
  a queue of notifications: <i>bundled notifications</i>. This is similar to the
-  <a href="{@docRoot}/training/wearables/notifications/stacks.html">Notification
+  <a href="{@docRoot}training/wearables/notifications/stacks.html">Notification
   Stacks</a> feature in Android Wear. For example, if your app creates notifications
   for received messages, when more than one message is received, bundle the
  notifications together as a single group. You can