diff --git a/docs/cdp/cdp_data_export_schedule.md b/docs/cdp/cdp_data_export_schedule.md
index b7b5c9c6f3..b0507d3b3a 100644
--- a/docs/cdp/cdp_data_export_schedule.md
+++ b/docs/cdp/cdp_data_export_schedule.md
@@ -7,7 +7,7 @@ description: Data export schedule in Ibexa CDP.
 ## Configuration key
 
 Configuration in [[= product_name_cdp =]] allows you to automate the process of exporting Content, Users and Products.
-A global `ibexa_cdp` [configuration key](configuration.md#configuration-files) looks as below:
+An `ibexa_cdp.data_export` [configuration key](configuration.md#configuration-files) looks as below:
 
 ```yaml
 ibexa_cdp:
@@ -39,9 +39,9 @@ ibexa_cdp:
 Under the `schedule` setting you can find separate sections for exporting User, Content, and Product. 
 Structure of each section is exactly the same and includes `interval` and `options` elements:
 
-- **Interval** - sets the frequency of the command invoke, for example, '*/30 * * * *' means "every 30 minutes", '0 */12 * * *' means "every 12 hours".
+- `interval` - sets the frequency of the command invoke, for example, '*/30 * * * *' means "every 30 minutes", '0 */12 * * *' means "every 12th hour".
 It uses a standard `crontab` format, see [examples](https://crontab.guru/examples.html).
-- **Options** - allows you to add arguments that have to be passed to the export command.
+- `options`- allows you to add arguments that have to be passed to the export command.
 
 This configuration allows you to provide multiple export workflows with parameters.
 It's important, because each type of content/product must have its own parameters on the CDP side, where each has a different Stream ID key and different required values, which are configured per data source.