Skip to content

Commit 1d3fa57

Browse files
authored
apply review suggestion
1 parent c220a63 commit 1d3fa57

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/engage/journeys/event-triggered-journeys-steps.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,7 @@ The following table explains the parameters you can configure for the Delay step
128128
| Minimum delay | 5 minutes |
129129
| Maximum delay | 182 days (around 6 months) |
130130

131-
### Configure the Delay step
131+
To configure the Delay step:
132132

133133
1. Drag the Delay step onto the journey canvas, or click **+** to add it.
134134
2. (*Optional*) Give the step a unique name.
@@ -250,4 +250,4 @@ There may be cases where events sent to Segment are missing specific properties
250250
- If an event property is mapped but is missing in the Track event, Segment still includes the mapped key in the payload but with a value of `undefined`.
251251
- Similarly, if a mapped trait is missing on the profile, the key is included in the payload with a value of `undefined`.
252252

253-
Carefully configuring mappings and handling missing attributes can help you maintain data integrity and avoid errors in downstream systems.
253+
Carefully configuring mappings and handling missing attributes can help you maintain data integrity and avoid errors in downstream systems.

0 commit comments

Comments
 (0)