fixup

Author: brentmmarks

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

@@ -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. 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.
+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. We will create an announcement on our Discuss forum and along with additional outreach where possible.
 
 Generally we will aim to start EOL process within 3 months of a new version release.
 

jekyll/_cci2/linux-cuda-images-support-policy.adoc

@@ -101,7 +101,7 @@ A minor version release -- CUDA 11.8:
 
 Once a new even numbered minor version is released, that version will be added and the oldest existing version will be removed, provided that more than 3 minor versions exist.
 
-When an image is selected for deprecation and removal, we will create an announcement on our Discuss forum, along with reaching out via email to developers who have requested one of the deprecated images in their recent jobs. We will also plan brownouts to help ensure you are aware of the approaching removal of deprecated images.
+When an image is selected for deprecation and removal, we will create an announcement on our Discuss forum and along with additional outreach where possible.
 
 [#exceptions]
 == Exceptions

jekyll/_cci2/linux-vm-support-policy.adoc

@@ -82,7 +82,7 @@ Example: When Ubuntu 24.04 LTS is released
 | `current` and `edge` tags retained
 |===
 
-When an image is selected for deprecation and removal, we will create an announcement on our Discuss forum, along with reaching out via email to developers who have requested one of the deprecated images in their recent jobs.
+When an image is selected for deprecation and removal, we will create an announcement on our Discuss forum and along with additional outreach where possible.
 
 We will also plan brownouts to ensure users are aware of the approaching removal of deprecated images. Generally, we will aim to start an EOL process within 3 months of a new version release.
 

jekyll/_cci2/remote-docker-images-support-policy.adoc

@@ -93,7 +93,7 @@ Example: When Docker 28 is released:
 |===
 
 
-When an image is selected for deprecation and removal, we will create an announcement on our Discuss forum, along with reaching out via email to developers who have requested one of the deprecated images in their recent jobs.
+When an image is selected for deprecation and removal, we will create an announcement on our Discuss forum and along with additional outreach where possible.
 
 We will also plan brownouts to ensure users are aware of the approaching removal of deprecated images. Generally, we will aim to start an EOL process within 3 months of a new version release
 

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

@@ -92,7 +92,7 @@ Example: When Windows Server 2025 is released
 | `current` and `edge` tags retained
 |===
 
-When an image is selected for deprecation and removal, we will create an announcement on our Discuss forum, along with reaching out via email to developers who have requested one of the deprecated images in their recent jobs.
+When an image is selected for deprecation and removal, we will create an announcement on our Discuss forum and along with additional outreach where possible.
 
 We will also plan brownouts to ensure users are aware of the approaching removal of deprecated images. Generally, we will aim to start an EOL process within 3 months of a new version release.
 

jekyll/_cci2/xcode-policy.adoc

@@ -67,7 +67,7 @@ Future example, when Xcode 26 enters Beta:
 
 Betas of new major versions of Xcode are shipped by Apple during WWDC, which usually occurs in early-mid June each year.
 
-When an image is selected for deprecation and removal, we will create an announcement on our link:https://discuss.circleci.com/c/announcements/39[Discuss forum], along with reaching out via email to developers who have requested one of the deprecated images in their recent jobs. We will always aim to provide four weeks' notice where possible.
+When an image is selected for deprecation and removal, we will create an announcement on our link:https://discuss.circleci.com/c/announcements/39[Discuss forum], along with additional outreach where possible. We will always aim to provide four weeks' notice where possible.
 
 We will never automatically redirect requests for images to different `major.minor` versions, so when one of these images is removed, jobs will start to fail if the `.circleci/config.yml` has not been updated.