14.08: rewording last update

Change-Id: I3a819b472ba8dbdeaa956f326f6831040b1c4474
Signed-off-by: Ryan Harkin <ryan.harkin@linaro.org>

2 files changed, 20 insertions, 20 deletions

diff --git a/members/arm/android/images/armv8-android-juno-lsk/HOWTO_releasenotes.txt b/members/arm/android/images/armv8-android-juno-lsk/HOWTO_releasenotes.txt
index 0635376..49233e2 100644
--- a/members/arm/android/images/armv8-android-juno-lsk/HOWTO_releasenotes.txt
+++ b/members/arm/android/images/armv8-android-juno-lsk/HOWTO_releasenotes.txt
@@ -7,40 +7,40 @@ The ARMv8-A reference software stack combined with the Juno ARM Development Plat
 
 For those with access to Juno, this release can be used to examine the internals of the Android Open Source Project in a running system. Application developers, particularly those working in Java, will also be able to develop applications via the recently announced Android 'L' preview SDK.
 
-In this release the focus has been on two major component SELinux enabled boot and latest AOSP NDK built with Linaro tool chains.
+In this release, the focus has been on two major components: SELinux enabled boot and latest AOSP NDK built with Linaro tool chains.
 
-The release contains Android ARMv8 optimizations for OpenSSL, LibPNG and BIONIC cortex C strings that were submitted by Linaro to AOSP. The release enables ART runtime as default in "compiler" mode. As part of our release validation we have observed few standard benchmark and generic applications failing to run due to 64 bit compatibility of Android frameworks, the list is included as part of the test report to members. The other known issues and bugs found in this release are captured below.
+The release contains Android ARMv8 optimizations for OpenSSL, LibPNG and BIONIC cortex C strings that were submitted by Linaro to AOSP. The release enables ART runtime as default in "compiler" mode. As part of our release validation we have observed a few standard benchmark and generic applications failing to run due to 64 bit compatibility of Android frameworks. The list is included as part of the test report to members. The other known issues and bugs found in this release are captured below.
 
 The Android AOSP software provided in this release is functionally tested with CTS version 4.4 and the CTS results are shared with members. The BIONIC component is validated with Android BIONIC tests. Android Monkey tests were run for stress testing. Multi-arch support has been validated using examples provided in Android NDK.
 
 The Linaro Android releases for Juno appear monthly. Sources are also made available so you can build your own images (see the "Building from Source tab":https://releases.linaro.org/14.08/members/arm/android/images/armv8-android-juno-lsk/#tabs-3). 
 
-NOTE : 
 
-h3. Linaro Android NDK 
+h3. Linaro Android NDK
 
-The build process for Linaro NDK has been completely revamped - instead of repackaging the latest upstream release with just a few components replaced, we're now building the NDK completely from source, allowing us to pick up changes more recent than the latest release. This has also given us the flexibility to merge the ndk32 and ndk64 into one ndk that can target any supported processor.
+The build process for Linaro NDK has been completely revamped - instead of repackaging the latest upstream release with just a few components replaced, we're now building the NDK completely from source, allowing us to pick up changes more recent than the latest release. This has also given us the flexibility to merge ndk32 and ndk64 into one ndk that can target any supported processor.
 
 Installation instructions: Download the NDK from tools directory of the release page and uncompress ndk-linaro-2014.08.tar.xz to your location of choice (e.g. /opt). Point the project you wish to compile at the directory created that way (e.g. /opt/ndk-linaro-2014.08). Since Linaro NDK is a drop-in replacement for upstream NDK, there will usually be no need to change anything.
 
-A notable difference that may require some modifications to code using the NDK is that Linaro NDK defaults to using a gcc 4.9 based compiler for every architecture (not just 64 bit). Code that only compiles with older compilers will have to be fixed.
+A notable difference that may require some modifications to code using the NDK is that Linaro NDK defaults to using a GCC 4.9 based compiler for every architecture (not just 64 bit). Code that only compiles with older compilers will have to be fixed.
 
 h3. SELinux
 
 The SElinux feature is not enabled in the release by default, user can set the UEFI boot argument to enable SELinux.
 
-Inorder to use pre-built images from release and to boot Android with SELinux feature user can follow either of these options
+In order to use pre-built images from the release and boot Android with SELinux feature, the user can follow either of these options:
 
-a) Download the Android images with .tar extension on a ubuntu 14.04 host machine that includes tar command with --selinux option and use the linaro-android-media create utility to create the Android image.
+a) Download the Android images with .tar extension on a ubuntu 14.04 host machine that includes the tar command with the --selinux option and use the linaro-android-media create utility to create the Android image.
 
 ./linaro-image-tools/linaro-android-media-create --image_file mmc.img --dev vexpress --system system.tar.bz2 --userdata userdata.tar.bz2 --boot boot.tar.bz2
 
-b) If user does not have access to ubuntu 14.04 host machine, then download img files boot.tar.bz2, system.img, userdata.img and use the command linaro-android-media-create to create the Android image. The .img files are quite big in size compared to .tar files, so downloading these .img files might take considerable time.
+b) If the user does not have access to ubuntu 14.04 host machine, then download the files boot.tar.bz2, system.img, userdata.img and use the command linaro-android-media-create to create the Android image. The .img files are quite big in size compared to .tar files, so downloading these .img files might take considerable time.
 
 ./linaro-image-tools/linaro-android-media-create --image_file mmc.img --dev vexpress --systemimage system.img --userdataimage userdata.img --boot boot.tar.bz2
 
 Finally, pass selinux=1 as the boot parameter in the UEFI bootargs configuration.
 
+
 h2. About the Juno ARM Development Platform
 
 The Juno ARM Development Platform (ADP) is a software development platform for ARMv8-A. It includes:
@@ -59,11 +59,11 @@ h2. About the Linaro Stable Kernel (LSK)
 
 The Linaro Stable Kernel (LSK) is produced, validated and released by Linaro and is based on the Linux stable kernel tree. The LSK focuses on quality and stability and is therefore a great foundation for product development. It also includes backports of commonly desired features, provided they meet the quality requirements, and also any bug fixes.
 
-LSK releases appear monthly. Sources are also made available so you can build your own images (see the "'Building from Source'":https://releases.linaro.org/14.07/members/arm/android/images/armv8-android-juno-lsk/#tabs-3 tab).
+LSK releases appear monthly. Sources are also made available so you can build your own images (see the "'Building from Source'":https://releases.linaro.org/14.08/members/arm/android/images/armv8-android-juno-lsk/#tabs-3 tab).
 
 h2. License
 
-The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.07/members/arm/android/images/armv8-android-juno-lsk/#tabs-5.
+The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.08/members/arm/android/images/armv8-android-juno-lsk/#tabs-5.
 
 h2. Support
 
diff --git a/members/arm/android/images/armv8-juice-juno-lsk/HOWTO_releasenotes.txt b/members/arm/android/images/armv8-juice-juno-lsk/HOWTO_releasenotes.txt
index 19f8ed9..5bbee92 100644
--- a/members/arm/android/images/armv8-juice-juno-lsk/HOWTO_releasenotes.txt
+++ b/members/arm/android/images/armv8-juice-juno-lsk/HOWTO_releasenotes.txt
@@ -5,29 +5,29 @@ The Linaro Android release is based on a snapshot of the Android AOSP master tak
 
 The Android AOSP software provided in this release is thoroughly tested with CTS version 4.4 and the CTS results are shared with members. The BIONIC component is validated with Android BIONIC tests. Android Monkey tests were run for stress testing.
 
-The Linaro Android releases for Juno (32-bit) appear monthly. Sources are also made available so you can build your own images (see the Building from Source tab). 
+The Linaro Android releases for Juno (32-bit) appear monthly. Sources are also made available so you can build your own images (see the Building from Source tab).
 
-In this release the focus has been on two major component SELinux enabled boot and latest AOSP NDK built with Linaro tool chains.
+In this release, the focus has been on two major components: SELinux enabled boot and latest AOSP NDK built with Linaro tool chains.
 
 h3. Linaro Android NDK
 
-The build process for Linaro NDK has been completely revamped - instead of repackaging the latest upstream release with just a few components replaced, we're now building the NDK completely from source, allowing us to pick up changes more recent than the latest release. This has also given us the flexibility to merge the ndk32 and ndk64 into one ndk that can target any supported processor.
+The build process for Linaro NDK has been completely revamped - instead of repackaging the latest upstream release with just a few components replaced, we're now building the NDK completely from source, allowing us to pick up changes more recent than the latest release. This has also given us the flexibility to merge ndk32 and ndk64 into one ndk that can target any supported processor.
 
 Installation instructions: Download the NDK from tools directory of the release page and uncompress ndk-linaro-2014.08.tar.xz to your location of choice (e.g. /opt). Point the project you wish to compile at the directory created that way (e.g. /opt/ndk-linaro-2014.08). Since Linaro NDK is a drop-in replacement for upstream NDK, there will usually be no need to change anything.
 
-A notable difference that may require some modifications to code using the NDK is that Linaro NDK defaults to using a gcc 4.9 based compiler for every architecture (not just 64 bit). Code that only compiles with older compilers will have to be fixed.
+A notable difference that may require some modifications to code using the NDK is that Linaro NDK defaults to using a GCC 4.9 based compiler for every architecture (not just 64 bit). Code that only compiles with older compilers will have to be fixed.
 
 h3. SELinux
 
 The SElinux feature is not enabled in the release by default, user can set the UEFI boot argument to enable SELinux.
 
-Inorder to use pre-built images from release and to boot Android with SELinux feature user can follow either of these options
+In order to use pre-built images from the release and boot Android with SELinux feature, the user can follow either of these options:
 
-a) Download the Android images with .tar extension on a ubuntu 14.04 host machine that includes tar command with --selinux option and use the linaro-android-media create utility to create the Android image.
+a) Download the Android images with .tar extension on a ubuntu 14.04 host machine that includes the tar command with the --selinux option and use the linaro-android-media create utility to create the Android image.
 
 ./linaro-image-tools/linaro-android-media-create --image_file mmc.img --dev vexpress --system system.tar.bz2 --userdata userdata.tar.bz2 --boot boot.tar.bz2
 
-b) If user does not have access to ubuntu 14.04 host machine, then download img files boot.tar.bz2, system.img, userdata.img and use the command linaro-android-media-create to create the Android image. The .img files are quite big in size compared to .tar files, so downloading these .img files might take considerable time.
+b) If the user does not have access to ubuntu 14.04 host machine, then download the files boot.tar.bz2, system.img, userdata.img and use the command linaro-android-media-create to create the Android image. The .img files are quite big in size compared to .tar files, so downloading these .img files might take considerable time.
 
 ./linaro-image-tools/linaro-android-media-create --image_file mmc.img --dev vexpress --systemimage system.img --userdataimage userdata.img --boot boot.tar.bz2
 
@@ -52,11 +52,11 @@ h2. About the Linaro Stable Kernel (LSK)
 
 The Linaro Stable Kernel (LSK) is produced, validated and released by Linaro and is based on the Linux stable kernel tree. The LSK focuses on quality and stability and is therefore a great foundation for product development. It also includes backports of commonly desired features, provided they meet the quality requirements, and also any bug fixes.
 
-LSK releases appear monthly. Sources are also made available so you can build your own images (see the "'Building from Source'":https://releases.linaro.org/14.07/members/arm/android/images/armv8-juice-juno-lsk/#tabs-3 tab).
+LSK releases appear monthly. Sources are also made available so you can build your own images (see the "'Building from Source'":https://releases.linaro.org/14.08/members/arm/android/images/armv8-juice-juno-lsk/#tabs-3 tab).
 
 h2. License
 
-The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.07/members/arm/android/images/armv8-juice-juno-lsk/#tabs-5.
+The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.08/members/arm/android/images/armv8-juice-juno-lsk/#tabs-5.
 
 h2. Support