Skip to content

Commit cebfcae

Browse files
pwsegrchinn1
andauthored
Update src/engage/audiences/index.md
Co-authored-by: rchinn-segment <[email protected]>
1 parent a9b759a commit cebfcae

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/engage/audiences/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ You can also use computed traits in an Audience definition. For example, you can
4242
> info ""
4343
> Engage supports nested traits, but the Audience builder doesn’t support accessing objects nested in arrays. When you send arrays of objects, they are flattened into strings. As a result, the same conditions that work on strings will work on the array. Within the builder, you can only use string operations like `contains` and `does not contain` to look for individual characters or a set of characters in the flattened array.
4444
45-
### Time Comparision
45+
### Time comparison
4646

4747
You can use various time comparison operators in your Audience definition. Such operators are: before date, after date, within last, within next, before last, after next. Only ISO timestamps can be used with these operators.
4848
If the timestamp is not a valid ISO timestamp (for example, a trailing 'Z' is missing), it will not be processed by Real-time compute. See [Real-time compute compared to batch](docs/engage/audiences/#real-time-compute-compared-to-batch)

0 commit comments

Comments
 (0)