fixup

Author: brentmmarks

jekyll/_cci2/android-images-support-policy.adoc

@@ -18,11 +18,11 @@ This document outlines the CircleCI Android image release, update, and deprecati
 [#release-policy]
 == Release policy
 
-Android images are released once a quarter, with patch releases potentially being made for security issues. These images are generally built on top of the latest version of our most recent stable base Ubuntu image with added packages for Android.
+Android images are released once a quarter, with patch releases potentially made for security issues. These images are generally built on top of the latest version of our most recent stable base Ubuntu image with added packages for Android.
 
 - We install the most up-to-date versions of each tool/package in newly built images.
 - We aim to package 6 levels of the Android API within each image release.
-- As this image is not specifically designed for the Android Gradle Plugin (AGP), some updates may come later than desired. However, we aim to follow compatibility matrices for link:https://docs.gradle.org/current/userguide/compatibility.html[AGP] and link:https://developer.android.com/build/releases/gradle-plugin#updating-gradle[Gradle].
+- As this image is not specifically designed for the Android Gradle Plugin (AGP), some updates may come later than desired. We aim to follow compatibility matrices for link:https://docs.gradle.org/current/userguide/compatibility.html[AGP] and link:https://developer.android.com/build/releases/gradle-plugin#updating-gradle[Gradle].
 
 Releases may be skipped if there are no material updates to core Android functionality, such as `sdkmanager`, `ndk` or platform versions.
 
@@ -40,7 +40,7 @@ For the latest major version of Docker:
 [#critical-cve-patches]
 == Critical CVE patches
 
-When critical CVEs are disclosed that affect the versions of the operating system or software stack in our Docker convenience images, we will investigate the impact that this has on our images being used within the CircleCI execution environment. If customers are impacted by these CVEs we will push a patch fix to the released image(s), and this image will supersede the original image.
+When critical CVEs are disclosed that affect the versions of the operating system or software stack, we will investigate the impact that this has on the image within the CircleCI execution environment. If customers are impacted by these CVEs we will push a patch fix to the released image(s), and this image will supersede the original image.
 
 [#bug-reports-issues-and-prs]
 == Bug reports, issues, and PRs
@@ -50,7 +50,7 @@ File a link:https://support.circleci.com/hc/en-us/requests/new[Support Ticket wi
 [#image-lifespan-eol]
 == Image lifespan / EOL
 
-When a new API Level for Android is released we will release it to edge and give a 3 month warning before the default image will have oldest version no longer supported. We will create an announcement on our Discuss forum, along with reaching out via email to developers who may be impacted by this change.
+When a new API Level for Android is released we will release it to edge. We will give a 3 month warning before the default image will have oldest version no longer supported. In these cases, an announcement will be posted on our Discuss Forum, along with additional outreach, such as an email notice, where possible.
 
 Generally we will aim to start EOL process within 3 months of a new version release.