Merge pull request #4233 from braze-inc/develop

Leftover Deploy - October 13, 2022

_docs/_developer_guide/platform_integration_guides/unity/sdk_integration/android.md

@@ -76,15 +76,6 @@ If your app does not have an `AndroidManifest.xml`, you can use the following as
         <action android:name="com.google.firebase.MESSAGING_EVENT" />
       </intent-filter>
     </service>
-
-    <!-- BroadcastReceiver used to forward certain Braze push notification events to Unity -->
-    <receiver android:name="com.appboy.unity.AppboyUnityPushBroadcastReceiver" android:exported="false" >
-      <intent-filter>
-        <action android:name="com.braze.push.intent.NOTIFICATION_OPENED" />
-        <action android:name="com.braze.push.intent.NOTIFICATION_RECEIVED" />
-        <action android:name="com.braze.push.intent.NOTIFICATION_DELETED" />
-      </intent-filter>
-    </receiver>
   </application>
 </manifest>
 ```

_docs/_developer_guide/platform_integration_guides/web/push_notifications/integration.md

@@ -61,7 +61,11 @@ If you wish to unsubscribe a user, you can do so by calling `braze.unregisterPus
 Recent versions of Safari and Firefox require that you call this method from a short-lived event handler (e.g., from a button click handler or soft push prompt). This is consistent with [Chrome's user experience best practices](https://docs.google.com/document/d/1WNPIS_2F0eyDm5SS2E6LZ_75tk6XtBSnR1xNjWJ_DPE) for push registration.
 {% endalert %}
 
-### Step 3: Configure Safari push
+### Step 3: Configure Safari push {#safari}
+
+{% alert info %}
+Safari 16 on macOS 13 or later uses modern push standards, and this step is no longer required. If you want to support older macOS Safari versions, this step is required.
+{% endalert %}
 
 If you wish to support push notifications for Safari on Mac OS X, follow these additional instructions: