Apply suggestions from code review

Co-authored-by: Adrien Dupuis <61695653+adriendupuis@users.noreply.github.com>

Author: mnocon

docs/cdp/cdp_activation/cdp_configuration.md

@@ -92,7 +92,7 @@ For more information, see [Website tracking dataflow](https://content.raptorserv
 
 ### Configuration
 
-Add the `membership.activation_id` and `membership.api_key` credentials to your [`ibexa_cdp` configuration](#configuration), using the credentials for [CDP API activation](#set-up-cdp-api-activation).
+Add the `membership.activation_id` and `membership.api_key` credentials to your [`ibexa.system.<scope>.cdp` configuration](#configuration), using the credentials for [CDP API activation](#set-up-cdp-api-activation).
 To control how long resolved segment memberships are cached per visitor, use the `ibexa_segmentation.anonymous.cache` configuration key:
 
 ```yaml

docs/cdp/cdp_guide.md

@@ -105,7 +105,7 @@ You can also connect created audiences to the activations.
 
 ### Anonymous user segmentation
 
-[[= product_name_cdp =]] can build audiences for anonymour users, enabling personalised experiences for not logged-in visitors.
+[[= product_name_cdp =]] can build audiences for anonymous users, enabling personalised experiences for not logged-in visitors.
 
 When an anonymous visitor accesses your site, Raptor starts building an [anonymous profile](https://content.raptorservices.com/help-center/introduction-to-person-identifiers-and-profile-unification).