Skip to content

Commit 3fc3830

Browse files
authored
typo/ wording fix
1 parent b53ef10 commit 3fc3830

File tree

1 file changed

+2
-2
lines changed
  • src/connections/destinations/catalog/actions-braze-web

1 file changed

+2
-2
lines changed

src/connections/destinations/catalog/actions-braze-web/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,8 @@ Braze web-mode (Actions) provides the following benefits over Braze (Classic):
2929
3. Choose which of your sources to connect the destination to and follow the steps to create your destination.
3030
> warning "Mapping settings"
3131
> Some events require specific property names to map correctly into Braze.
32-
> For example, purchase events must use a `products` arry with `product_id` and `price.
33-
> See [Braze-web settings mappings](#braze-web-settings-mapping) for the full list before setting up mappings.
32+
> For example, purchase events must use a `products` array with `product_id` and `price.
33+
> See [Braze-web settings mappings](#braze-web-settings-mapping) for the full list of requirements before setting up mappings.
3434
4. In the **Settings** tab, configure the connection settings. **API Key**, **SDK Endpoint**, and **REST Endpoint** are required settings.
3535

3636
After setting up your Braze web-mode (Action) destination in the Segment app, Segment's Analytics.js library starts asynchronously loading the Braze SDK on your page and sending data. Data appears in the Segment CDN in about 45 minutes.

0 commit comments

Comments
 (0)