diff --git a/docs/html/guide/topics/renderscript/compute.jd b/docs/html/guide/topics/renderscript/compute.jd index 14a16822c6139..c62510b2383fc 100644 --- a/docs/html/guide/topics/renderscript/compute.jd +++ b/docs/html/guide/topics/renderscript/compute.jd @@ -10,7 +10,7 @@ parent.link=index.html
  1. Writing a RenderScript Kernel
  2. -
  3. Accessing RenderScript Java APIs +
  4. Accessing RenderScript APIs
    1. Setting Up Your Development Environment
    @@ -150,19 +150,24 @@ beneficial on some architectures due to additional optimizations only available precision (such as SIMD CPU instructions).

    -

    Accessing RenderScript Java APIs

    +

    Accessing RenderScript APIs

    -

    When developing an Android application that uses RenderScript, you can access its Java API in - one of two ways. The APIs are available in the {@link android.renderscript} package - on devices running Android 3.0 (API level 11) and higher. These are the original APIs for - RenderScript. The APIs are also available as a Support Library in the - {@link android.support.v8.renderscript} package, which allow you to use them on devices running - Android 2.2 (API level 8) and higher.

    +

    When developing an Android application that uses RenderScript, you can access its API in + one of two ways:

    + +

    We strongly recommend using the Support Library APIs for accessing RenderScript because they include the latest improvements to the RenderScript compute framework and provide a wider range - of device compatibility. Using the RenderScript APIs in the Support Library requires specific - setup procedures for your development environment, which is described in the next section.

    + of device compatibility.

    Using the RenderScript Support Library APIs

    @@ -218,9 +223,9 @@ import android.support.v8.renderscript.*; back to a compatible version if the device it is running on does not support the target version.
  5. {@code sdk.buildtools} - The version of the Android SDK build tools to use. This value - should be set to 18.1.0 or higher. If this option is not specified, the highest installed build - tools version is used. You should always set this value to ensure the consistency of builds - across development machines with different configurations.
  6. + should be set to {@code 18.1.0} or higher. If this option is not specified, the highest + installed build tools version is used. You should always set this value to ensure the + consistency of builds across development machines with different configurations.