diff --git a/website/docs/how-to/how-to-capture-impression-data.mdx b/website/docs/how-to/how-to-capture-impression-data.mdx
index bdfeeb486f..5ae9ed1e31 100644
--- a/website/docs/how-to/how-to-capture-impression-data.mdx
+++ b/website/docs/how-to/how-to-capture-impression-data.mdx
@@ -5,7 +5,7 @@ import ApiRequest from '@site/src/components/ApiRequest'
 import VideoContent from '@site/src/components/VideoContent.jsx'
 
 :::info Placeholders
-Placeholders in code samples below are delimited by angle brackets (i.e. `<placeholder-name>`). You will need to replace them with the values that are correct in _your_ situation for the code samples to run properly.
+Placeholders in the code samples below are delimited by angle brackets (i.e. `<placeholder-name>`). You will need to replace them with the values that are correct in _your_ situation for the code samples to run properly.
 :::
 
 Unleash allows you to gather [**impression data**](../advanced/impression-data.md) from your feature toggles, giving you complete visibility into who checked what toggles and when. What you do with this data is entirely up to you, but a common use case is to send it off to an aggregation and analytics service such as [Posthog](https://posthog.com/) or [Google Analytics](https://analytics.google.com/), either just for monitoring purposes or to facilitate [A/B testing](../topics/a-b-testing.md).