Updated instances of passive voice via Copilot

_docs/_partners/additional_channels_and_extensions/additional_channels/instant_chat/dixa.md

@@ -71,7 +71,7 @@ Choose to show or hide the user's custom Braze events.
 
 #### Display a list of purchases
 
-Choose to show or hide a list products purchased by the user. Here, you can see how many times it was purchased. To view the first and last purchase date, hover above the item. 
+Choose to show or hide a list of products the user purchased. Here, you can see how many times the user purchased the product. To view the first and last purchase date, hover over the item. 
 
 ### Example integration
 

_docs/_partners/canvas_audience_sync/criteo_audience_sync.md

@@ -94,7 +94,7 @@ Enter a name for the new audience, select **Add Users to Audience**, and select
 
 ![Expanded view of the Custom Audience Canvas step. Here, the desired Ad account is selected, and a new audience is created.]({% image_buster /assets/img/criteo/criteo3.png %})
 
-Users will be notified at the top of the step editor if the audience is created successfully or if errors arise during this process. Users can also reference this audience for user removal later in the Canvas journey because the audience was created in draft mode.
+Braze displays a notification at the top of the step editor if the audience is created successfully or if errors arise. Users can reference this audience for user removal later in the Canvas journey because the audience was created in draft mode.
 
 ![An alert that appears after a new audience is created in the Canvas component.]({% image_buster /assets/img/criteo/criteo1.png %})
 
@@ -119,9 +119,9 @@ You can view the audience in Criteo by going into your ads manager account and t
 
 ## User syncing and rate limit considerations
 
-As users reach the Audience Sync step, Braze will sync these users in near real-time while also respecting Criteo's API rate limits. What this means in practice is that Braze will try to batch and process as many users every 5 seconds before sending these users to Criteo.
+As users reach the Audience Sync step, Braze syncs them in near real time while respecting Criteo's API rate limits. Braze batches and processes as many users as possible every five seconds before sending them to Criteo.
 
-Criteo's API rate limit states no more than 250 requests per minute. If a Braze customer reaches this rate limit, Braze the Canvas will retry the sync for up to ~13 hours. If the sync is not possible, these users are listed under the Users Errored metric. 
+Criteo's API rate limit allows no more than 250 requests per minute. If a customer reaches this limit, Braze retries the sync for up to ~13 hours. If the sync is still not possible, Braze lists these users under the Users Errored metric. 
 
 ## Understanding analytics
 

_docs/_partners/canvas_audience_sync/facebook_audience_sync.md

@@ -27,9 +27,9 @@ This feature allows brands to control what specific first-party data is shared w
 
 ## User syncing and rate limit considerations
 
-As users reach the Audience Sync step, Braze will sync these users in near real-time while also respecting Facebook's Marketing API rate limits. What this means in practice is that Braze will try to batch and process as many users every 5 seconds before sending these users to Facebook. 
+As users reach the Audience Sync step, Braze syncs them in near real time while respecting Facebook's Marketing API rate limits. Braze batches and processes as many users as possible every 5 seconds before sending them to Facebook. 
 
-Facebook's Marketing API rate limit states no more than ~190,000 API requests for each ad account in a one-hour time period. If a Braze customer reaches this rate limit, Braze the Canvas will retry the sync for up to ~13 hours. If the sync isn't possible, these users are listed under the Users Errored metric.
+Facebook's Marketing API rate limit allows no more than ~190,000 API requests per ad account in a one-hour period. If a customer reaches this limit, Braze retries the sync for up to ~13 hours. If the sync still isn't possible, Braze lists these users under the Users Errored metric.
 
 ## Prerequisites
 

_docs/_partners/canvas_audience_sync/linkedin_audience_sync.md

@@ -96,7 +96,7 @@ Next, save your audience by clicking the **Create Audience** button at the botto
 
 ![An example "leads" audience with the selected Braze ad account, "leads" audience, the action to add users to the audience, and email, Android GAID, and first and last name as fields to match.]({% image_buster /assets/img/linkedin/linkedin10.png %})
 
-Users will be notified at the top of the step editor if the audience is created successfully or if errors arise during this process. Users can also reference this audience for user removal later in the Canvas journey because the audience was created in draft mode.
+Braze displays a notification at the top of the step editor if the audience is created successfully or if errors arise. Users can reference this audience for user removal later in the Canvas journey because the audience was created in draft mode.
 
 ![Confirmation that the "leads" audience was created.]({% image_buster /assets/img/linkedin/linkedin9.png %})
 
@@ -123,9 +123,9 @@ You can view the audience on LinkedIn by going into your ad account and selectin
 
 ## User syncing and rate limit considerations
 
-As users reach the Audience Sync Step, Braze will sync these users in near real-time while respecting LinkedIn’s API rate limits. In practice, Braze will try to batch and process as many users every 5 seconds before sending these users to LinkedIn.
+As users reach the Audience Sync step, Braze syncs them in near real time while respecting LinkedIn’s API rate limits. Braze batches and processes as many users as possible every 5 seconds before sending them to LinkedIn.
 
-LinkedIn’s API rate limit states no more than ten queries per second and 100,000 users per request. If a Braze customer reaches this rate limit, Braze the Canvas will retry the sync for up to about 13 hours. If the sync is not possible, these users are listed under the Users Errored metric.
+LinkedIn’s API rate limit allows no more than ten queries per second and 100,000 users per request. If a customer reaches this limit, Braze retries the sync for up to about 13 hours. If the sync is still not possible, Braze lists these users under the Users Errored metric.
 
 ## Understanding analytics
 

_docs/_partners/canvas_audience_sync/pinterest_audience_sync.md

@@ -82,7 +82,7 @@ Enter a name for the new audience, select **Add Users to Audience**, and select
 
 ![Expanded view of the Custom Audience Canvas step. Here, the desired Ad account is selected, and a new audience is created.]({% image_buster /assets/img/audience_sync/pinterest_sync.png %})
 
-Users will be notified at the top of the step editor if the audience is created successfully or if errors arise during this process. Users can also reference this audience for user removal later in the Canvas journey because the audience was created in draft mode.
+Braze displays a notification at the top of the step editor if the audience is created successfully or if errors arise. Users can reference this audience for user removal later in the Canvas journey because the audience was created in draft mode.
 
 ![An alert that appears after a new audience is created in the Canvas component.]({% image_buster /assets/img/audience_sync/pinterest_sync3.png %})
 
@@ -107,9 +107,9 @@ You can view the audience on Pinterest by entering your ads manager account and
 
 ## User syncing and rate limit considerations
 
-As users reach the Audience Sync step, Braze will sync these users in near real-time while respecting Pinterest's Marketing API rate limits. In practice, Braze will try to batch and process as many users every 5 seconds before sending these users to Pinterest.
+As users reach the Audience Sync step, Braze syncs them in near real time while respecting Pinterest's Marketing API rate limits. Braze batches and processes as many users as possible every 5 seconds before sending them to Pinterest.
 
-Pinterest's Segment API rate limit states no more than seven queries per second per user and 1,900 users per request. If a Braze customer reaches this rate limit, Braze the Canvas will retry the sync for up to ~13 hours. If the sync is not possible, these users are listed under the Users Errored metric.
+Pinterest's Segment API rate limit allows no more than seven queries per second per user and 1,900 users per request. If a customer reaches this limit, Braze retries the sync for up to ~13 hours. If the sync is still not possible, Braze lists these users under the Users Errored metric.
 
 ## Understanding analytics
 

_docs/_partners/canvas_audience_sync/snapchat_audience_sync.md

@@ -83,7 +83,7 @@ Enter a name for the new audience, select **Add Users to Audience**, and select
 
 ![Expanded view of the Custom Audience Canvas step. Here, the desired Ad account is selected, and a new audience is created.]({% image_buster /assets/img/audience_sync/snapchat3.png %})
 
-Users will be notified at the top of the step editor if the audience is created successfully or if errors arise during this process. Users can also reference this audience for user removal later in the Canvas journey because the audience was created in draft mode.
+Braze displays a notification at the top of the step editor if the audience is created successfully or if errors arise. Users can reference this audience for user removal later in the Canvas journey because the audience was created in draft mode.
 
 ![An alert that appears after a new audience is created in the Canvas component.]({% image_buster /assets/img/audience_sync/snapchat2.png %})
 
@@ -109,9 +109,9 @@ You can view the audience in Snapchat by entering your ads manager account and s
 
 ## User syncing and rate limit considerations
 
-As users reach the Audience Sync step, Braze will sync these users in near real-time while respecting Snapchat's API rate limits. In practice, Braze will try to batch and process as many users every 5 seconds before sending these users to Snapchat.
+As users reach the Audience Sync step, Braze syncs them in near real time while respecting Snapchat's API rate limits. Braze batches and processes as many users as possible every 5 seconds before sending them to Snapchat.
 
-Snapchat's API rate limit states no more than ten queries per second and 100,000 users per request. If a Braze customer reaches this rate limit, Braze the Canvas will retry the sync for up to ~13 hours. If the sync is not possible, these users are listed under the Users Errored metric.
+Snapchat's API rate limit allows no more than ten queries per second and 100,000 users per request. If a customer reaches this limit, Braze retries the sync for up to ~13 hours. If the sync is still not possible, Braze lists these users under the Users Errored metric.
 
 ### Understanding analytics
 

_docs/_partners/canvas_audience_sync/tiktok_audience_sync.md

@@ -82,7 +82,7 @@ Enter a name for the new audience, select **Add Users to Audience**, and select
 
 ![]({% image_buster /assets/img/audience_sync/tiktok3.png %})
 
-Users will be notified at the top of the step editor if the audience is created successfully or if errors arise during this process. Users can also reference this audience for user removal later in the Canvas journey because the audience was created in draft mode.
+Braze displays a notification at the top of the step editor if the audience is created successfully or if errors arise. Users can reference this audience for user removal later in the Canvas journey because the audience was created in draft mode.
 
 ![]({% image_buster /assets/img/audience_sync/tiktok2.png %})
 
@@ -108,9 +108,9 @@ You can view the audience in TikTok by entering your **Ads Manager Account** and
 
 ## User syncing and rate limit considerations
 
-As users reach the Audience Sync step, Braze will sync these users in near real-time while respecting TikTok's Marketing API rate limits. This means that Braze will try to batch and process as many users every 5 seconds before sending these users to TikTok.
+As users reach the Audience Sync step, Braze syncs them in near real time while respecting TikTok's Marketing API rate limits. Braze batches and processes as many users as possible every 5 seconds before sending them to TikTok.
 
-TikTok's Segment API rate limit states no more than 50 queries per second and 10k users per request. If a Braze customer reaches this rate limit, the Canvas will retry the sync for up to ~13 hours. If the sync is not possible, these users are listed under the Users Errored metric.
+TikTok's Segment API rate limit allows no more than 50 queries per second and 10k users per request. If a customer reaches this limit, Braze retries the sync for up to ~13 hours. If the sync is still not possible, Braze lists these users under the Users Errored metric.
 
 ## Understanding analytics
 

_docs/_partners/ecommerce/ordering_payments_subscription/recurly.md

@@ -82,11 +82,11 @@ For effective customer engagement, you must [configure custom events]({{site.bas
 
 Because Recurly uses the Braze `/users/track` endpoint, the integration is subject to standard Braze rate limits of 50,000 requests per minute.
 
-Recurly batches certain subscription lifecycle events as single API calls to Braze to reduce the number of calls made.
+Recurly batches certain subscription lifecycle events into single API calls to Braze to reduce the number of requests.
 
-- Creation of multiple subscriptions at the same time are batched and sent to Braze as a single request.
-- When multiple subscriptions are renewed at the same time for an account, each of those renewals is batched into a single request.
-- Same model subscription lifecycle events are sent as a single request. An example being a newly created invoice with a payment would send a single API request with both the `Recurly Invoice Created` and `Recurly Successful Payment` custom events.
+- Recurly batches and sends multiple subscriptions created at the same time as a single request.
+- Recurly batches multiple same-time renewals for an account into a single request.
+- Recurly sends same-model subscription lifecycle events in a single request. For example, a newly created invoice with a payment results in one API request containing both the `Recurly Invoice Created` and `Recurly Successful Payment` custom events.
 
 Batches are sent to Braze in groups of up to 75 events at a time. For example, if 100 subscriptions were created at once, Recurly would make two API requests to Braze. See [batching User Track requests]({{site.baseurl}}/api/api_limits/#batch-user-track) for details.
 

_docs/_partners/message_orchestration/attribution/adjust.md

@@ -84,9 +84,9 @@ Here, you will find the REST endpoint and generate your Braze data import key. A
 
 ### Step 4: Confirm the integration
 
-Once Braze receives attribution data from Adjust, the status connection indicator on the Adjust technology partners page in Braze will change from "Not Connected" to "Connected". A timestamp of the last successful request will also be included. 
+After Braze receives attribution data from Adjust, the status connection indicator on the Adjust technology partners page in Braze changes from "Not Connected" to "Connected" and includes a timestamp of the last successful request.
 
-Note that this will not happen until we receive data about an attributed install. Organic installs, which should be excluded from the Adjust postback, are ignored by our API and are not counted when determining if a successful connection was established.
+This status changes only after Braze receives data about an attributed install. Braze ignores organic installs (excludes them from the Adjust postback) and does not count them when determining if the connection is successful.
 
 ## Available data fields
 

_docs/_partners/message_orchestration/attribution/airbridge.md

@@ -212,9 +212,9 @@ For more detailed instructions, visit [Airbridge](https://help.airbridge.io/en/g
 
 ### Step 4: Confirm the integration
 
-Once Braze receives attribution data from Airbridge, the status connection indicator on the Airbridge technology partners page in Braze will change from "Not Connected" to "Connected". A timestamp of the last successful request will also be included.
+After Braze receives attribution data from Airbridge, the status connection indicator on the Airbridge technology partners page in Braze changes from "Not Connected" to "Connected" and includes a timestamp of the last successful request.
 
-Note that this will not happen until we receive data about an attributed install. Organic installs, which should be excluded from the Airbridge postback, are ignored by our API and are not counted when determining if a successful connection was established.
+This status changes only after Braze receives data about an attributed install. Braze ignores organic installs (excludes them from the Airbridge postback) and does not count them when determining if the connection is successful.
 
 ## Available data fields
 

_docs/_partners/message_orchestration/attribution/branch_for_attribution.md

@@ -95,9 +95,9 @@ Here, you will find the REST endpoint and generate your Braze data import key. A
 
 ### Step 4: Confirm the integration
 
-Once Braze receives attribution data from Branch, the status connection indicator on the Branch technology partners page in Braze will change from "Not Connected" to "Connected". A timestamp of the last successful request will also be included. 
+After Braze receives attribution data from Branch, the status connection indicator on the Branch technology partners page in Braze changes from "Not Connected" to "Connected" and includes a timestamp of the last successful request.
 
-Note that this will not happen until we receive data about an attributed install. Organic installs, which should be excluded from the Branch postback, are ignored by our API and are not counted when determining if a successful connection was established.
+This status changes only after Braze receives data about an attributed install. Braze ignores organic installs (excludes them from the Branch postback) and does not count them when determining if the connection is successful.
 
 ## Facebook and X (formerly Twitter) attribution data
 

_docs/_partners/message_orchestration/attribution/kochava.md

@@ -72,9 +72,9 @@ Here, you will find the REST endpoint and generate your Braze data import key. A
 
 ### Step 4: Confirm the integration
 
-Once Braze receives attribution data from Kochava, the status connection indicator on the Kochava technology partners page in Braze will change from "Not Connected" to "Connected". A timestamp of the last successful request will also be included. 
+After Braze receives attribution data from Kochava, the status connection indicator on the Kochava technology partners page in Braze changes from "Not Connected" to "Connected" and includes a timestamp of the last successful request.
 
-Note that this will not happen until we receive data about an attributed install. Organic installs, which should be excluded from the Kochava postback, are ignored by our API and are not counted when determining if a successful connection was established.
+This status changes only after Braze receives data about an attributed install. Braze ignores organic installs (excludes them from the Kochava postback) and does not count them when determining if the connection is successful.
 
 ## Facebook and X (formerly Twitter) attribution data
 

_docs/_partners/message_orchestration/attribution/singular.md

@@ -82,9 +82,9 @@ You will need to provide the data import key and REST endpoint to your Singular
 
 ### Step 3: Confirm the integration
 
-Once Braze receives attribution data from Singular, the status connection indicator on the Singular technology partners page in Braze will change from "Not Connected" to "Connected". A timestamp of the last successful request will also be included. 
+After Braze receives attribution data from Singular, the status connection indicator on the Singular technology partners page in Braze changes from "Not Connected" to "Connected" and includes a timestamp of the last successful request.
 
-Note that this will not happen until we receive data about an attributed install. Organic installs, which should be excluded from the Singular postback, are ignored by our API and are not counted when determining if a successful connection was established.
+This status changes only after Braze receives data about an attributed install. Braze ignores organic installs (excludes them from the Singular postback) and does not count them when determining if the connection is successful.
 
 ## Facebook and X (formerly Twitter) attribution data