From c3dc9a1c8e947353fb86f0976c42acf2e7533ac7 Mon Sep 17 00:00:00 2001 From: Kevin Hufnagle Date: Thu, 8 Sep 2016 22:23:49 -0700 Subject: [PATCH] docs: Fixed typo in first paragraph of connectivity monitoring page Bug: 25649961 Change-Id: Idb5456b2a6190c84abbd1ca026f60db2c2edb08f --- .../training/monitoring-device-state/connectivity-monitoring.jd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/html/training/monitoring-device-state/connectivity-monitoring.jd b/docs/html/training/monitoring-device-state/connectivity-monitoring.jd index 2dd904f325f74..c63822bea116b 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

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?

+download, why bother waking the device to schedule the update at all?

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.