Update create-asset.md

docs/Frontend/Providing/create-asset.md

@@ -40,8 +40,8 @@ By enabling parameterization, you can offer data consumers, to configure paramet
 **Available parameterizations**
 - **Method Parameterization**: You can allow your consumer to define the method (e.g. GET, POST, etc.) on how you fetch the data from your data source.
 - **Path Parameterization**: You can allow your consumer to define additional path segments of your data source on a data transfer request. If you have your data URL https://api.coincap.io/v2/assets and allow fetching specific data by adding "/{coin_name}", you could for example allow consumers to fetch data from https://api.coincap.io/v2/assets/bitcoin by enabling this option.
-- **Query Param Parameterization**: You can allow your consumer to define the parameters on a data transfer request. If you have your data at https://api.myorg.com/data and could fetch data for a specific product with URL https://api.myorg.com/data?product=001 you can add as data-source URL https://api.myorg.com/data and enable param parameterization. Thus, consumers could define the query-parameters of the data-source themselves. 
-- **Request Body Parameterization**: On methods like POST or PUT, HTTP allows to send additional data in the body of the request to your data-source. For example if the pre-selected method is POST and the https://api.myorg.com/data endpoint allows to add data in the request-body, the consumer could send it's data within a data transfer request which is then used to send towards the data-source as body.
+- **Query Param Parameterization**: You can allow your consumer to define the query parameters on a data transfer request. Thus, consumers could define query-parameters of the data-source themselves. 
+- **Request Body Parameterization**: On methods like POST or PUT, HTTP allows to send additional data in the body of the request to your data-source. For example if the pre-selected method is POST and the endpoint allows to add data in the request-body, the consumer could send it's data within a data transfer request which is then used to send towards the data-source as body.
 
 #### Authentication
 By specifying the header "Authorization", you could for example enable basic HTTP-auth or bearer-token authentication. Optionally a single header can be marked as authentication header and can have its value supplied by a vault-secret in our vault connected to your CaaS, "Header with Vault Secret".