From 705f300b41103acc7011b0ed12d6cc5a9647fb9c Mon Sep 17 00:00:00 2001 From: Christopher Tate Date: Mon, 13 Jun 2022 10:11:33 -0700 Subject: [PATCH] Fix typo in reference docs Fixes: 214900783 Test: m offline-sdk-docs Change-Id: Ib95c8fb0fd2e0ea89679bdc74713225b3eaf14ab --- core/java/android/content/BroadcastReceiver.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/java/android/content/BroadcastReceiver.java b/core/java/android/content/BroadcastReceiver.java index 2a19d37c596bf..c7a3b52097af2 100644 --- a/core/java/android/content/BroadcastReceiver.java +++ b/core/java/android/content/BroadcastReceiver.java @@ -361,7 +361,7 @@ public abstract class BroadcastReceiver { * to avoid glitching the main UI thread due to disk IO. * *

As a general rule, broadcast receivers are allowed to run for up to 10 seconds - * before they system will consider them non-responsive and ANR the app. Since these usually + * before the system will consider them non-responsive and ANR the app. Since these usually * execute on the app's main thread, they are already bound by the ~5 second time limit * of various operations that can happen there (not to mention just avoiding UI jank), so * the receive limit is generally not of concern. However, once you use {@code goAsync}, though