From 10594f3cb392ea18283b2c6e4a05309b37ff913e Mon Sep 17 00:00:00 2001
From: David Friedman <dmail@google.com>
Date: Wed, 9 Mar 2016 02:20:34 -0800
Subject: [PATCH] Docs: Fixes to Behavior Changes page for N-Preview

Change-Id: I77cd81e8fd7feb559e49d3d7a7673e7febc5a5c7
---
 docs/html/preview/behavior-changes.jd | 21 +++++++++------------
 1 file changed, 9 insertions(+), 12 deletions(-)

diff --git a/docs/html/preview/behavior-changes.jd b/docs/html/preview/behavior-changes.jd
index b64f3bbb17aed..b6ef1105e698b 100644
--- a/docs/html/preview/behavior-changes.jd
+++ b/docs/html/preview/behavior-changes.jd
@@ -523,24 +523,21 @@ JavaVM::AttachCurrentThread from &lt;jni.h&gt;.
 <h2 id="other">Other important points</h2>
 
 <ul>
-<li>On Android N, apps should be able to gracefully handle an out-of-memory
-condition, or they might crash when the user changes display size and then
-restores the app from Recents.</li>
-
-<li>
-Apps running on Android N but targeting lower API levels must be able to
-gracefully handle their process being killed; they should
-not crash on subsequent launches.
+<li>When an app is running on Android N, but targets a lower API level,
+and the user changes display size, the app process is killed. The app
+must be able to gracefully handle this scenario. Otherwise, it crashes
+when the user restores it from Recents.
 
 <p>
-You can diagnose this behavior by causing an identical crash
-when killing the app manually via DDMS or automatically in a low-
-or out-of-memory condition.
+You should test your app to ensure
+that this behavior does not occur.
+You can do so by causing an identical crash
+when killing the app manually via DDMS.
 </p>
 
 <p>
 Apps targeting N and above are not automatically killed on density changes;
-however, they may still respond poorly to configuration changes
+however, they may still respond poorly to configuration changes.
 </p>
 </li>