BD-3311: Update images

_docs/_user_guide/message_building_by_channel/push/android/rich_notifications.md

@@ -18,14 +18,18 @@ tool:
 
 ## Requirements
 
-- Note that the expanded notification view is only available on devices using Jelly Bean (Android 4.1) or later. If a user's device is not running on these systems, they will not see the notification image.
+- Android rich notifications aren't available when creating a quick push campaign.
+- The expanded notification view is only available on devices using Jelly Bean (Android 4.1) or later. If a user's device isn't running on these systems, they will not see the notification image.
 - Android Extended Notification images must be 2:1 ratio, but do not have a size limit.
-- Android also allows for setting a separate image for the standard notification view. <br>Recommended size images: 512x256 for Small, 1024x512 for Medium, and 2048x1024 for Large.
+- Android also allows for setting a separate image for the standard notification view. These are the recommended size images: 
+  - Small: 512x256
+  - Medium: 1024x512 
+  - Large: 2048x1024
 - Currently, Android rich notifications only allow for static images, including JPEG and PNG image formats. GIF and other image formats are not yet supported.
-- Note, adding action buttons to your push notification may affect the area of the image that is displayable. Test with the dashboard preview and live devices to ensure that results are as expected.
+- Adding action buttons to your push notification may affect the area of the image that is displayable. Test with the dashboard preview and live devices to ensure that results are as expected.
 
 {% alert note %}
-While Braze provides instructions on how to set up rich push, the actual rendering of rich push notifications can vary depending on outside factors such as device aspect ratio, Android version, OEM-specific constraints, etc. We recommend doing a send test to multiple Android devices to make sure your rich push notifications are appearing as you intend them to.
+While Braze provides instructions on how to set up rich push, the actual rendering of rich push notifications can vary depending on outside factors such as device aspect ratio, Android version, OEM-specific constraints, and others. We recommend doing a send test to multiple Android devices to make sure your rich push notifications appear as you intend them to.
 {% endalert %}
 
 ## Setting up your Android rich notification

_docs/_user_guide/message_building_by_channel/push/ios/rich_notifications.md

@@ -19,17 +19,20 @@ tool:
 
 ## Requirements
 
+
 - To ensure your app can send rich notifications, follow the [iOS push integration][1] instructions, as your developer will need to add a service extension to your app.
 - You should also reference [Apple's documentation][2] for media limitations and specs.
-
-> As of January 2020, iOS rich push notifications can handle images 1038x1038 as long as they are under 10 MB, but we recommend using as small a file size as possible. In practice, sending large files can cause both unnecessary network stress and make download timeouts more common.
-
+- iOS rich notifications aren't available when creating a quick push campaign.
 - iOS will scale images to fit in the screen and will scale rich images for the active or locked view.
 - File types that we currently support for direct uploading within our dashboard include JPEG, PNG, or GIF. These files can also be entered into the templatable URL field along with these additional file types: AIF, M4A, MP3, MP4, or WAV.
 
+{% alert note %}
+As of January 2020, iOS rich push notifications can handle images 1038x1038 that are under 10 MB, but we recommend using as small a file size as possible. In practice, sending large files can cause both unnecessary network stress and make download timeouts more common.
+{% endalert %}
+
 ### Character count
 
-While we can't provide a hard and fast rule for the precise number of characters to include in a push, we [provide some guidelines]({{site.baseurl}}/user_guide/message_building_by_channel/push/best_practices/message_format/) to consider while designing iOS messages. There may be some variance depending on the presence of an image, the notification state and display setting of the user's device, as well as the size of the device. When in doubt, keep it short and sweet.
+While we can't provide a hard and fast rule for the precise number of characters to include in a push, we [provide some guidelines]({{site.baseurl}}/user_guide/message_building_by_channel/push/best_practices/message_format/) to consider while designing iOS messages. There may be some variance depending on the presence of an image, the notification state and display setting of the user's device, and the size of the device. When in doubt, keep it short and sweet.
 
 > As a general rule of thumb, Braze recommends keeping each line of text for both the optional title and message body to approximately 30-40 characters in a mobile push notification.