Apply suggestions

Author: AlliterativeAlice

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

@@ -141,7 +141,7 @@ If you are using URL rules, these will be matched whenever Segment sends an even
 
 ### Conversion Tracking with Backend Events
 
-When you send events to Segment from your backend which are forwarded to StackAdapt using Segment's backend SDKs, the user agent and IP address of the user who originated the event must be included in the event context in order for conversions to be tracked. This is because StackAdapt uses the user agent and IP address to attribute the conversion to the correct event to a user who has interacted with your ads. Examples of how to do this can be found in the documentation for Segment's SDKs. For example, for the [Python SDK](/docs/connections/sources/catalog/libraries/server/python/#override-context-value) this can be done as follows:
+When you send events to Segment from your backend, which are forwarded to StackAdapt using Segment's backend SDKs, the user agent and IP address of the user who originated the event must be included in the event context for conversions to be tracked. StackAdapt uses the user agent and IP address to attribute the conversion to the correct event to a user who has interacted with your ads. Examples of how to do this can be found in the documentation for Segment's SDKs. For example, for the [Python SDK](/docs/connections/sources/catalog/libraries/server/python/#override-context-value) this can be done as follows:
 
 ```python
 analytics.track('user_id', 'Order Completed', context={