Skip to content

Commit 2a64fe8

Browse files
Apply suggestions from code review
1 parent 7321bbc commit 2a64fe8

File tree

1 file changed

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

1 file changed

+2
-2
lines changed

src/connections/destinations/catalog/actions-s3/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -103,12 +103,12 @@ To finish the setup, enable the AWS S3 (Actions) Destination in your workspace:
103103

104104
{% include components/actions-fields.html settings="true"%}
105105

106-
## Step 3: Configure the AWS S3 (Actions) Destination mappings
106+
### Step 3: Configure the AWS S3 (Actions) Destination mappings
107107
To finish the configuration, add mappings to your new AWS S3 (Actions) Destination:
108108

109109
1. Add a new **Sync to S3** Action into the destination.
110110
2. Define the Event Trigger. If multiple types are accepted in the Event Trigger, the generated files will automatically be split by type in S3 (for example, you might have a Track events file and an Identify events file).
111111
3. Configure the Column Mappings. If you don't need any of the default columns, leave the value blank. You can also choose to add new mapping fields to set up customized columns as needed.
112112
4. Configure any additional settings as required.
113113
5. Enable the Mapping.
114-
6. Verify the Segment data is stored in the S3 bucket by navigating to the `<your_S3_bucket>/` in the AWS console.
114+
6. Verify that Segment is sending data to your S3 bucket by navigating to `<your_S3_bucket>/` in the AWS console.

0 commit comments

Comments
 (0)