From ece522e3c7a3ec090ca6dbd50ca21fe1efa09e0d Mon Sep 17 00:00:00 2001 From: Dirk Dougherty Date: Tue, 15 Mar 2016 17:05:51 -0700 Subject: [PATCH] More edits to preview docs. Change-Id: I5a405ff3e2a0703f1d899abb6a252e41c7d9bdd5 --- docs/html/preview/behavior-changes.jd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/html/preview/behavior-changes.jd b/docs/html/preview/behavior-changes.jd index bc7dbc735d494..cd4d27e9067f3 100644 --- a/docs/html/preview/behavior-changes.jd +++ b/docs/html/preview/behavior-changes.jd @@ -166,7 +166,7 @@ page.image=images/cards/card-n-changes_2x.png

If your app uses any of these intents, you should remove dependencies on them as soon as possible so that you can target Android N devices properly. The Android framework provides several solutions to mitigate the need for - these implicit broadcasts or background services. For example, the {@link + these implicit broadcasts. For example, the {@link android.app.job.JobScheduler} API provides a robust mechanism to schedule network operations when specified conditions, such as connection to an unmetered network, are met. You can even use {@link @@ -174,7 +174,7 @@ page.image=images/cards/card-n-changes_2x.png

- For more information about this behavior change and how to adapt your app, + For more information about background optimizations in N and how to adapt your app, see Background Optimizations.