diff --git a/contents/docs/feature-flags/creating-feature-flags.mdx b/contents/docs/feature-flags/creating-feature-flags.mdx index 49569745b248..17618b1facbd 100644 --- a/contents/docs/feature-flags/creating-feature-flags.mdx +++ b/contents/docs/feature-flags/creating-feature-flags.mdx @@ -281,6 +281,7 @@ Flags without evaluation contexts continue to evaluate for all requests (default - SDKs must send the `evaluation_contexts` parameter with matching contexts for the flag to evaluate (the legacy `evaluation_environments` parameter is also supported) - Flags with no evaluation contexts will evaluate for all requests (default behavior) - At least one evaluation context must match for the flag to be included in the evaluation +- Evaluation contexts and (and evaluation runtime) do not affect local evaluation behavior diff --git a/contents/docs/product-analytics/funnels.mdx b/contents/docs/product-analytics/funnels.mdx index f799cfbedc0a..e32c41f157ad 100644 --- a/contents/docs/product-analytics/funnels.mdx +++ b/contents/docs/product-analytics/funnels.mdx @@ -209,7 +209,7 @@ In this case, you can choose from which step the properties should be selected f ##### 1. First touchpoint -In this case, the first property value seen in any of the steps is chosen. +In this case, the first property value seen in any occurrences of the funnel events. Consider this example sequence of events: