Clarified recommended use cases for NDK.

Added - "game engines" officially supported use case for NDK
Removed - "self-contained" ambiguous in general and confusing to someone who is trying to do game development in C++
Removed - "that don't allocate a lot of memory" game engines do allocate a lot of memory.

Change-Id: I098de65bf0c4b4ab4a85611426b68613692e52c5
(cherry picked from commit 8da272f4fe4f1d50543afe488406d56b669364a1)

diff --git a/docs/html/tools/sdk/ndk/index.jd b/docs/html/tools/sdk/ndk/index.jd
index a22dc90..0ac1881 100644 (file)
--- a/docs/html/tools/sdk/ndk/index.jd
+++ b/docs/html/tools/sdk/ndk/index.jd
@@ -245,8 +245,8 @@ This is the Android Software Development Kit License Agreement
   but it always increases your app complexity. In general, you should only use the NDK
   if it is essential to your app&mdash;never because you simply prefer to program in C/C++.</p>
 
-  <p>Typical good candidates for the NDK are self-contained, CPU-intensive operations that don't
-  allocate much memory, such as signal processing, physics simulation, and so on. When examining
+  <p>Typical good candidates for the NDK are CPU-intensive workloads such as game engines,
+  signal processing, physics simulation, and so on. When examining
   whether or not you should develop in native code, think about your requirements and see if the
   Android framework APIs provide the functionality that you need.</p>