summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
author Kevin Hufnagle <khufnagle@google.com> 2016-09-26 23:17:38 +0000
committer android-build-merger <android-build-merger@google.com> 2016-09-26 23:17:38 +0000
commit329cf34008cb87585bd34acd94e5c2f7c1c7ebca (patch)
tree4707f5a093ed8f91dc3ac81ed9e1c588c9ecb1f5
parented4fa320201fc2a0fc622f4649eee9c70f2b9220 (diff)
parent4bd6ab2ecf94aa82ddc8573fe020881562f20b29 (diff)
docs: Fixed typo in first paragraph of connectivity monitoring page am: c3dc9a1c8e
am: 4bd6ab2ecf Change-Id: I9f7f3ec307b6db8a2264a236b765ae4f53662525
-rw-r--r--docs/html/training/monitoring-device-state/connectivity-monitoring.jd2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/html/training/monitoring-device-state/connectivity-monitoring.jd b/docs/html/training/monitoring-device-state/connectivity-monitoring.jd
index 2dd904f325f7..c63822bea116 100644
--- a/docs/html/training/monitoring-device-state/connectivity-monitoring.jd
+++ b/docs/html/training/monitoring-device-state/connectivity-monitoring.jd
@@ -33,7 +33,7 @@ next.link=manifest-receivers.html
<p>Some of the most common uses for repeating alarms and background services is to schedule regular
updates of application data from Internet resources, cache data, or execute long running downloads.
But if you aren't connected to the Internet, or the connection is too slow to complete your
-download, why both waking the device to schedule the update at all?</p>
+download, why bother waking the device to schedule the update at all?</p>
<p>You can use the {@link android.net.ConnectivityManager} to check that you're actually
connected to the Internet, and if so, what type of connection is in place.</p>