Merge pull request #461 from segmentio/repo-sync

repo sync

Author: bot-docsteam

.github/styles/Vocab/Docs/accept.txt

@@ -22,6 +22,7 @@ Amberflo
 Appboy
 Appsflyer
 async
+background(?:ed|ing)
 Blitzllama
 blocklist
 boolean
@@ -100,4 +101,5 @@ viewability
 waitlist
 WebKit
 Wootric
+Xcode
 Zendesk

src/connections/destinations/catalog/mixpanel/index.md

@@ -47,13 +47,18 @@ If you want to track the `page` or `screen` calls to Mixpanel with the name or c
 > info ""
 > Beginning with "Consolidate Page" calls, the following options are each *mutually exclusive*. [See the code for details](https://github.com/segmentio/analytics.js-integrations/blob/master/integrations/mixpanel/lib/index.js#L96-L139){:target="_blank"}.
 
+### Prioritization of settings
 
+When you use the Mixpanel destination in Cloud-mode, Segment sends events for each option you select. This may result in Mixpanel receiving duplicate events for a single page call.
 
-If you select "Track all Pages to Mixpanel", all `page` calls regardless of how you have customized it will send a `Loaded A Page`. Even if you have the other options enabled, Segment sends this call to prevent double counting your pageviews.
+When you use the Mixpanel destination in Device-mode, Segment prioritizes the options to prevent duplicate calls as follows:
 
-If you select "Track Categorized Pages to Mixpanel", Segment sends a `Viewed [category] Page` event.
 
-If you select "Track Named Pages to Mixpanel", Segment sends a `Viewed [name] Page` event.
+- If you select "Track all Pages to Mixpanel", all `page` calls regardless of how you have customized it will send a `Loaded A Page`. Even if you have the other options enabled, Segment sends this call to prevent double counting your pageviews.
+
+- If you select "Track Categorized Pages to Mixpanel", Segment sends a `Viewed [category] Page` event.
+
+- If you select "Track Named Pages to Mixpanel", Segment sends a `Viewed [name] Page` event.
 
 > info ""
 > If both Option 2 and 3 are enabled, Segment gives precedence to `category`. If you pass both `category` and `name`, (for example, `analytics.page('category', 'name');`), Segment sends a `Viewed category name Page` to Mixpanel.
@@ -339,9 +344,6 @@ Segment doesn't map `$library_version` since that is reserved for Mixpanel's lib
 
 ## Features
 
-### Autotrack
-
-Mixpanel discontinued the Autotrack feature in February 2021. The feature is no longer available for use.
 
 ### People
 
@@ -584,7 +586,7 @@ You can check a specific user profile in Mixpanel for Computed Traits by going t
 
 Computed traits without a lookback window search across all historical events, and update in real time.
 
-Computed traits with a lookback window only search across events that occurred within the specified timeframe. Computed traits *with* a lookback window are updated hourly.
+Computed traits with a lookback window only search across events that occurred within the specified time frame. Computed traits *with* a lookback window are updated hourly.
 
 ![](images/pers-03-lookback.png)
 
@@ -624,7 +626,7 @@ You can check a specific user profile in Mixpanel for audience events by going t
 
 Audiences without a lookback window searches across all historical events and update in real time.
 
-Audiences with a lookback window only search across events that occurred within the specified timeframe. Audiences *with* a lookback window are updated hourly.
+Audiences with a lookback window only search across events that occurred within the specified time frame. Audiences *with* a lookback window are updated hourly.
 
 
 ![](images/pers-10-lookback.png)

src/connections/event-delivery.md

@@ -6,16 +6,16 @@ The Event Delivery tool helps you understand if data is reaching your destinatio
 
 Segment sends billions of events to destinations every week. If Segment encounters any errors when attempting to deliver your data, Segment reports them in the Event Delivery tool.
 
-Here is an example of what the Event Delivery tool looks like:
+Here's an example of what the Event Delivery tool looks like:
 
-![](images/edelivery_jXaoBuF6.png)
+![An Event Delivery example](images/edelivery_jXaoBuF6.png)
 
 ## When to use Event Delivery
 
 Scenarios when this tool will be useful: 
 
 - **When data seems to be missing in your destination.**
-  For example, you have Google Analytics set up as a destination and your recent data looks incomplete
+  For example, you have Google Analytics set up as a destination and your recent data looks incomplete.
 - **When setting up a destination for the first time.** 
   For example, you are connecting Google Analytics to your Node Source. Once you've entered your credentials and turned the destination on, you can use this feature to see whether events are successfully making it to GA in near realtime. 
 
@@ -27,32 +27,32 @@ Scenarios when this tool will be useful: 
 This feature is only available for server side integrations (also known as cloud-mode destinations). You will not be able to use this for client side / device-mode destinations as device-mode data is sent directly to the tool's API. To be report on deliverability, the data must be sent to Destinations using Segment's APIs. 
 
 > warning ""
-> **Not available for Warehouses or Amazon S3**. These destinations work differently to our other destinations, and aren't supported at this time.
+> **Not available for Warehouses or Amazon S3**. These destinations work differently from other destinations in Segment, and aren't supported at this time.
 
 
 ## Where do I find it? 
 
 Event Delivery can be accessed within any supported destination in the App. It's located on the tab under "Settings" for each destination. 
 
-![](images/find-edelivery.png)
+![Where you can find Event Delivery in the app](images/find-edelivery.png)
 
 
 ## How do I use Event Delivery?
 
-The UI consists of 3 key parts that report on Segment's ability to deliver your source data - Key Metrics, Error Details and Delivery Trends. Reporting on core functionality from top to bottom: 
+The UI consists of three key parts that report on Segment's ability to deliver your source data - Key Metrics, Error Details, and Delivery Trends. Reporting on core functionality from top to bottom: 
 
 ## 1. Time period
 
 
-There is a drop down menu to select your time period. All of the UI is updated based on the time period you select. 
+There's a drop down menu to select your time period. All of the UI is updated based on the time period you select. 
 
-![](images/edelivery_Qs4r85sc.png)
+![Select a time period](images/edelivery_Qs4r85sc.png)
 
 ## 2. Key Metrics
 
 From left to right in the above graphic:
 
-- **Delivered:** This tells you the number of messages Segment successfully delivered to a destination in the time period you selected
+- **Delivered:** This tells you the number of messages Segment successfully delivered to a destination in the time period you selected.
 
 - **Not Delivered:** This count tells you the number of messages Segment was unable to deliver. If this number is higher than zero, you will see the reasons for this failure in the errors table below. 
 
@@ -63,45 +63,48 @@ From left to right in the above graphic:
 
 The purpose of the table is to provide you a summary of the different errors we've seen in a given period and the most important information on them. All of the rows in the table are clickable and expand to give you more information. 
 
-![](images/edelivery_V6hldpCl.png)
+![View error details](images/edelivery_V6hldpCl.png)
+
+> info ""
+> View Segment's list of [Integration Error Codes](/docs/connections/integration_error_codes/) for more information about what might cause an error.
 
 ### Error detail view
 
-When we see an error, we want to give you as much information to help you solve your problem. See below for an example of what this view looks like. 
+When there's an error, Segment wants to give you as much information as possible to help you resolve the issue. See below for an example of what this view looks like. 
 
-![](images/edelivery_CgNb4wVN.png)
+![An example of the error details view](images/edelivery_CgNb4wVN.png)
 
 This view includes: 
 
 #### Description
 
-The event delivery UI provides a human-friendly summary of the error, based on the payload we received back from the partner
+The event delivery UI provides a human-friendly summary of the error, based on the payload Segment received back from the partner.
 
 #### Actions
 
-These are actions we think you can take to solve the issue, based on what we know about the issue. 
+These are actions you can take, based on what Segment knows about the issue. 
 
 #### More Info
 
-Links to any documentation that we think could be helpful to you 
+This section displays links to any documentation that might be helpful to you. 
 
 
 #### Sample payloads
 
-To help you debug we provide sample payloads from every step of the data's journey through Segment
+To help you debug, Segment provides sample payloads from every step of the data's journey:
 
-- **You Sent** - the data you sent to Segment's API
+- **You Sent** - the data you sent to Segment's API.
 
-- **Request to Destination** - the request we made to the Partner API. This payload will likely be different from what you sent it because Segment is mapping your event to the partner's spec to ensure the message is successfully delivered. 
+- **Request to Destination** - the request Segment made to the Partner API. This payload will likely be different from what you sent it because Segment is mapping your event to the partner's spec to ensure the message is successfully delivered. 
 
-- **Response from Destination** - the response we received from the Partner API. This will have the raw partner error. If you need to troubleshoot an issue with a Partner's Success team, this is usually something they'll want to see. 
+- **Response from Destination** - the response Segment received from the Partner API. This will have the raw partner error. If you need to troubleshoot an issue with a Partner's Success team, this is usually something they'll want to see. 
 
 
 ## 4. Trends
 
-When debugging, it's helpful to see when issues start, stop and trend over time. 
+When debugging, it's helpful to see when issues start, stop, and trend over time. 
 
-![](images/edelivery_9FRFTAso.png)
+![Event Delivery trends](images/edelivery_9FRFTAso.png)
 
 #### Event Delivery
 

src/connections/functions/destination-functions.md

@@ -17,7 +17,7 @@ All functions are scoped to your workspace, so members of other workspaces can't
 
 
 > note ""
-> Destination functions does not accept data from [Object Cloud sources](/docs/connections/sources/#object-cloud-sources).
+> Destination functions doesn't accept data from [Object Cloud sources](/docs/connections/sources/#object-cloud-sources).
 
 ## Create a destination function
 
@@ -35,9 +35,9 @@ When you click **Build**, a code editor appears. Use the editor to write the cod
 Segment invokes a separate part of the function (called a "handler") for each event type that you send to your destination function.
 
 > info ""
-> Your function is not invoked for an event if you've configured a [destination filter](/docs/connections/destinations/destination-filters/), and the event doesn't pass the filter.
+> Your function isn't invoked for an event if you've configured a [destination filter](/docs/connections/destinations/destination-filters/), and the event doesn't pass the filter.
 
-The default source code template includes handlers for all event types. You do not need to implement all of them - just use the ones you need, and skip the ones you don't.
+The default source code template includes handlers for all event types. You don't need to implement all of them - just use the ones you need, and skip the ones you don't.
 
 Destination functions can define handlers for each message type in the [Segment spec](/docs/connections/spec/):
 
@@ -129,7 +129,7 @@ async function onTrack(event) {
 }
 
 ```
-If you do not supply a function for an event type, Segment throws an `EventNotSupported` error by default.
+If you don't supply a function for an event type, Segment throws an `EventNotSupported` error by default.
 
 You can read more about [error handling](#destination-functions-logs-and-errors) below.
 
@@ -271,15 +271,15 @@ async function onIdentifyBatch(events, settings) {
 
 ### Configure your batch parameters
 
-By default, Functions waits up to 10 seconds to form a batch of 20 events. You can increase the number of events included in each batch (up to 400 events per batch) by contacting [Segment support](https://segment.com/help/contact/){:target="_blank"}. Segment recommends users who wish to include fewer than 20 events per batch use destination functions without the `onBatch` handler. 
+By default, Functions waits up to 10 seconds to form a batch of 20 events. You can increase the number of events included in each batch (up to 400 events per batch) by contacting [Segment support](https://segment.com/help/contact/){:target="_blank"}. Segment recommends users who wish to include fewer than 20 events per batch use destination functions without the `onBatch` handler.
 
 ### Test the batch handler
 
-The [Functions editing environment](/docs/connections/functions/environment/) supports testing batch handlers. 
+The [Functions editing environment](/docs/connections/functions/environment/) supports testing batch handlers.
 
-To test the batch handler: 
-1. In the right panel of the Functions editor, click **customize the event yourself** to enter Manual Mode. 
-2. Add events as a JSON array, with one event per element. 
+To test the batch handler:
+1. In the right panel of the Functions editor, click **customize the event yourself** to enter Manual Mode.
+2. Add events as a JSON array, with one event per element.
 3. Click **Run** to preview the batch handler with the specified events.
 
 > note ""
@@ -291,7 +291,7 @@ The [Config API](/docs/config-api/) Functions/Preview endpoint also supports tes
 
 ### Handling batching errors
 
-Standard [function error types](/docs/connections/functions/destination-functions/#destination-functions-error-types) apply to batch handlers. Segment attempts to retry the batch in the case of Timeout or Retry errors. For all other error types, Segment discards the batch. It is also possible to report a partial failure by returning status of each event in the batch. Segment retries only the failed events in a batch until those events are successful or until they result in a permanent error.
+Standard [function error types](/docs/connections/functions/destination-functions/#destination-functions-error-types) apply to batch handlers. Segment attempts to retry the batch in the case of Timeout or Retry errors. For all other error types, Segment discards the batch. It's also possible to report a partial failure by returning status of each event in the batch. Segment retries only the failed events in a batch until those events are successful or until they result in a permanent error.
 
 ```json
 [
@@ -357,6 +357,8 @@ A function can throw errors, or Segment might encounter errors while invoking yo
 
 Segment only attempts to send the event to your destination function again if a **Retry** error occurs.
 
+You can view Segment's list of [Integration Error Codes](/docs/connections/integration_error_codes/) for more information about what might cause an error.
+
 ### Destination functions logs
 
 If your function throws an error, execution halts immediately. Segment captures the event, any outgoing requests/responses, any logs the function might have printed, as well as the error itself.
@@ -470,6 +472,6 @@ The [Event Delivery tab](/docs/connections/event-delivery/) continues to show me
 
 ##### How does batching impact function use and cost?
 
-A function's use depends on the number of times it is invoked, and the amount of time it takes to execute. When you enable batching, Segment invokes your function _once per batch_ rather than once per event. The volume of events flowing through the function determines the number of batches, which determines the number of invocations.
+A function's use depends on the number of times it's invoked, and the amount of time it takes to execute. When you enable batching, Segment invokes your function _once per batch_ rather than once per event. The volume of events flowing through the function determines the number of batches, which determines the number of invocations.
 
 If you're sending your batch to an external service, the execution time of the function depends on the end-to-end latency of that service's batch endpoint, which may be higher than an endpoint that receives a single event.

src/connections/integration_error_codes.md

@@ -13,4 +13,4 @@ id: integrationerrors
 | errors.awaiting-retry.429          | Rate limit exceeded. contact the partner to raise your limit or avoid sending events in burst.                                                                                                                                                                                                                                      |
 | errors.awaiting-retry.5xx          | The partner's API report an internal error. Consider disabling this integration or contact the integration partner to address this issue.                                                                                                                                                                                           |
 | errors.awaiting-retry.ENOTFOUND<br>errors.awaiting-retry.ECONNREFUSED <br>errors.awaiting-retry.ECONNRESET<br>errors.awaiting-retry.ECONNABORTED<br>errors.awaiting-retry.EHOSTUNREACH<br>errors.awaiting-retry.EAI_AGAIN | Segment is unable to establish a connection with the partner's server. This could mean your Segment configurations contain some invalid settings or that the integration is no longer operational.  If your configurations are valid, consider disabling this integration or contact the integration partner to address this issue. |
-| Others                             | Refer to the error message you receive for more information. Refer to our <a href="/docs/connections/test-connections/"> How do I test my connections guide</a> for more debugging help.
+| Others                             | Refer to the error message you receive for more information. See the article, [Testing Connections](/docs/connections/test-connections/) for more debugging help.