From 0046284c0f08a46ae54de7f93e3c0fc8470420df Mon Sep 17 00:00:00 2001
From: Eric Schmidt <erschmid@google.com>
Date: Fri, 30 Sep 2016 09:53:54 -0700
Subject: docs: Broken at link in Memory article.

Change-Id: Ia06dea536a891dd321cadcbe47212acbf6c067cc
---
 docs/html/training/articles/memory.jd | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/html/training/articles/memory.jd b/docs/html/training/articles/memory.jd
index 885112168e25..a4e645a46b5a 100644
--- a/docs/html/training/articles/memory.jd
+++ b/docs/html/training/articles/memory.jd
@@ -365,8 +365,8 @@ private ActivityManager.MemoryInfo getAvailableMemory() {
   You should generally avoid use of persistent services because of
   the on-going demands they place on available memory. Instead, we
   recommend that you use an alternative implementation
-  such as {@llink android.app.job.JobScheduler}. For more information about
-  how to use {@llink android.app.job.JobScheduler} to schedule background
+  such as {@link android.app.job.JobScheduler}. For more information about
+  how to use {@link android.app.job.JobScheduler} to schedule background
   processes, see
   <a href="/topic/performance/background-optimization.html">Background Optimizations</a>.
 <p>
-- 
cgit v1.2.3-59-g8ed1b