Doc change: adjust compatibility doc.

Change-Id: I74f9fba81de4d358ecccfe1ef0c69f0e83e1a7c5

1 files changed, 2 insertions, 9 deletions

diff --git a/docs/html/guide/practices/compatibility.jd b/docs/html/guide/practices/compatibility.jd
index d198166..4e4ec8d 100644
--- a/docs/html/guide/practices/compatibility.jd
+++ b/docs/html/guide/practices/compatibility.jd
@@ -46,11 +46,8 @@ make sure they reach the right audience.</p>
 
 <h3 id="defined">What does “Compatibility” mean?</h3>
 
-<p>A device is “Android compatible” if it can run apps written for the
-<em>Android execution environment</em>. The exact details of the Android
-execution environment are defined by the Android Compatibility Definition
-Document, but the single most to the ability to install and correctly run an
-Android <code>.apk</code> file.</p>
+<p>A device is “Android compatible” if it can correctly run apps written for the
+<em>Android execution environment</em>.</p>
 
 <p>There is exactly one Android API for each <a
 href="{@docRoot}guide/appendix/api-levels.html">API level</a>, and it’s the same
@@ -222,10 +219,6 @@ microphones.</li>
 ones, we will always take steps to protect existing applications so that they
 don’t end up being available to devices where they won’t work.</p>
 
-<p>This is implemented using the <code>aapt</code> tool in the SDK. To see which
-features your app explicitly requires or is implicitly assumed to require, you
-can use the command <code>aapt dump badging</code>.</p>
-
 <h3 id="conclusion">Conclusion</h3>
 
 <p>The goal of Android is to create a huge installed base for developers to take