Merge pull request #536 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/connections/functions/destination-functions.md

@@ -13,7 +13,7 @@ All functions are scoped to your workspace, so members of other workspaces can't
 > info ""
 > Functions is available to all customer plan types with a free allotment of usage hours. Read more about [Functions usage limits](/docs/connections/functions/usage/), or see [your workspace's Functions usage stats](https://app.segment.com/goto-my-workspace/settings/usage?metric=functions){:target="_blank"}.
 
-![An illusrative graphic showing information flowing from the Segment app, into code, and then into Slack](images/destination_functions_overview.png)
+![An illustrative graphic showing information flowing from the Segment app, into code, and then into Slack](images/destination_functions_overview.png)
 
 
 > note ""
@@ -352,7 +352,7 @@ A function can throw errors, or Segment might encounter errors while invoking yo
 - **Bad Request** - Any error thrown by the function code that is not covered by the other errors.
 - **Invalid Settings** - A configuration error prevented Segment from executing your code. If this error persists for more than an hour, [contact Segment Support](https://segment.com/help/contact/){:target="_blank"}.
 - **Message Rejected** - Your code threw `InvalidEventPayload` or `ValidationError` due to invalid input.
-- **Unsupported Event Type** - Your code does not implement a specific event type (`onTrack()`, etc.) or threw a `EventNotSupported` error.
+- **Unsupported Event Type** - Your code doesn't implement a specific event type (for example, `onTrack()`) or threw a `EventNotSupported` error.
 - **Retry** - Your code threw `RetryError` indicating that the function should be retried.
 
 Segment only attempts to send the event to your destination function again if a **Retry** error occurs.

src/connections/functions/environment.md

@@ -15,7 +15,7 @@ When you create a function, write code for it, and save it, the function appears
 
 Only [Functions admins](#functions-permissions) can create or edit functions.
 
-1. From your workspace, go to the Catalog and click the [Functions tab](https://app.segment.com/goto-my-workspace/functions/catalog).
+1. From your workspace, go to the Catalog and click the [Functions tab](https://app.segment.com/goto-my-workspace/functions/catalog){:target="_blank"}.
 2. Click **New Function**.
 3. Select the type of function you want to build, and click **Build**.
 
@@ -24,7 +24,7 @@ Only [Functions admins](#functions-permissions) can create or edit functions.
 5. Once you finish writing your function, click **Configure** to give it a name.
 6. Click **Create Function** to save your work and make this function available in your workspace.
 
-After you click **Create Function**, the function appears on the [Functions catalog page](https://app.segment.com/goto-my-workspace/functions/catalog/) in your workspace.
+After you click **Create Function**, the function appears on the [Functions catalog page](https://app.segment.com/goto-my-workspace/functions/catalog/){:target="_blank"} in your workspace.
 
 
 ## Editing a function
@@ -40,7 +40,7 @@ You can also choose to **Save & Deploy** to push changes to all, or specific fun
 > note ""
 > You must be a **Workspace Owner** or **Source Admin** to connect an instance of your function in your workspace.
 
-1. From the [Functions tab](https://app.segment.com/goto-my-workspace/functions/catalog), locate the source function you want to deploy.
+1. From the [Functions tab](https://app.segment.com/goto-my-workspace/functions/catalog){:target="_blank"}, locate the source function you want to deploy.
 2. Click **Connect Source** and follow the prompts to configure the source. (You can access these settings later by navigating to the Source Settings page for your source function.)
 3. Locate the webhook URL for the source, either on the **Overview** or **Settings → Endpoint** page.
 4. Copy this URL and paste it into the upstream tool or service.

src/connections/functions/index.md

@@ -7,7 +7,7 @@ Functions let you create your own sources and destinations directly within your
 > info ""
 > Functions is available to all customer plan types with a free allotment of usage hours. Read more about [Functions usage limits](/docs/connections/functions/usage/), or see [your workspace's Functions usage stats](https://app.segment.com/goto-my-workspace/settings/usage?metric=functions).
 
-![](images/functions_overview.png)
+![An image illustrating source functions and destination functions in a Segment workspace](images/functions_overview.png)
 
 ## What can you do with Functions?
 Functions can help you bring external data into Segment ([Source Functions](/docs/connections/functions/source-functions)) and send data in Segment out to external destinations ([Destination Functions](/docs/connections/functions/destination-functions)). Functions are scoped to your specific workspace. If you're a technology partner and want to build a new integration and publish it in Segment's catalog, see the [Developer Center documentation](/docs/partners/).

src/connections/functions/source-functions.md

@@ -254,9 +254,9 @@ Segment.set({
 
 The `Segment.set()` method accepts an object with the following fields:
 
-- `collection` - Collection name.
-- `id` - Object's unique identifier.
-- `properties` - Object with free-form data.
+- `collection` - A collection name, which must be lowercase.
+- `id` - An object's unique identifier.
+- `properties` - An object with free-form data.
 
 > warning ""
 > When you use the `set()` method, you won't see events in the Source Debugger. Segment only sends events to connected warehouses.

src/connections/functions/usage.md

@@ -6,19 +6,19 @@ Functions are billed to your account using the total execution time per month.
 
 An **individual function's execution time** is the total time it takes for the function to process events, including mapping, transformations, and requests to external APIs. Generally, requests to external APIs can greatly add to your total execution time.
 
-Your **total execution time** is the execution time for all of your active functions accumulated over the course of a month. You can see your current execution time on the [Functions tab of the Usage page](https://app.segment.com/goto-my-workspace/settings/usage?metric=functions&period=current) in each workspace. You will receive notifications of your usage when you've reached 75%, 90% and 100% of your allotted execution time.
+Your **total execution time** is the execution time for all of your active functions accumulated over the course of a month. You can see your current execution time on the [Functions tab of the Usage page](https://app.segment.com/goto-my-workspace/settings/usage?metric=functions&period=current){:target="_blank"} in each workspace. You will receive notifications of your usage when you've reached 75%, 90%, and 100% of your allotted execution time.
 
-The amount of time you are allotted changes depending on your [Segment pricing plan](http://segment.com/pricing).
+The amount of time you are allotted changes depending on your [Segment pricing plan](http://segment.com/pricing){:target="_blank"}.
 
 ## Measuring execution time
 
-We measure execution time from when the function first receives an event to the time the function either returns successfully or throws an error. If Segment retries your function (for example, if there was a timeout), those retries also count as billable execution time.
+Segment measures execution time from when the function first receives an event to the time the function either returns successfully or throws an error. If Segment retries your function (for example, if there was a timeout), those retries also count as billable execution time.
 
-Starting on April 8, 2021 Functions usage is measured in millisecond increments. This makes your usage and billing much more precise. Prior to this change, Functions was measured in 100ms increments, and then rounded up. For example, a function that took 80ms to complete was previously billed as 100ms. Using the new usage calculation, it is billed as 80ms. 
+Starting on April 8, 2021 Functions usage is measured in millisecond increments. This makes your usage and billing much more precise. Prior to this change, Functions was measured in 100ms increments, and then rounded up. For example, a function that took 80ms to complete was previously billed as 100ms. Using the new usage calculation, it is billed as 80ms.
 
 ## Execution timeouts
 
-Functions have a timeout of 5 seconds. If a function takes longer than 5 seconds, execution halts and the function is retried periodically for up to 4 hours.
+Functions have a timeout of five seconds. If a function takes longer than five seconds, execution halts and the function is retried periodically for up to four hours.
 
 
 
@@ -40,15 +40,15 @@ You can (and should!) use [Destination Filters](/docs/connections/destinations/d
 
 In the most cases, functions are slow due to external requests using the `fetch()` call. The external API may be under heavy load or it may simply take a long time to process your request.
 
-If you're making many requests that could be done in parallel, ensure that you're not doing them sequentially. If the external API takes 400ms to respond and you issue 10 requests, it would take 4 seconds to do them sequentially versus 400ms to do them in parallel. For example, if you're waiting for requests to complete inside of a loop you're making your requests sequentially:
+If you're making many requests that could be done in parallel, ensure that you're not doing them sequentially. If the external API takes 400ms to respond and you issue 10 requests, it would take four seconds to do them sequentially versus 400ms to do them in parallel. For example, if you're waiting for requests to complete inside of a loop you're making your requests sequentially:
 
 ```js
 for (const objectId of event.properties.objects) {
    const response = await fetch('https://example.com/?id=' + objectId, {
        method: 'POST',
        body: event.properties
    })
-   
+
    console.log(response.json())
 }
 ```