Clarify where UDPs can come from

Author: m-mohr

extensions/processing-parameters/README.md

@@ -13,9 +13,14 @@ Extensions can not change or break existing behavior of the openEO API.
 This extension adds a new endpoint (`GET /processing_parameters`, see [OpenAPI document](openapi.yaml))
 to discover the additional processing parameters that a back-end offers.
 
-Additionally, this extension allows to provide specific default values for user-defined processes (UDPs, see below).
+Additionally, this extension allows to provide specific default values for user-defined processes (UDPs),
+which includes:
 
-In both cases, the parameters and its values are provided separately for each processing mode.
+- UDPs submitted directly for synchronouzs processing, as batch jobs, or as secondary webservices
+- UDPs stored through the `/process_graphs` endpoints
+- UDPs stored external to the API and retrieved through the [Remote Process Definition Extension](../remote-process-definition/README.md)
+
+The parameters and its values are provided separately for each processing mode.
 
 ## Processing Parameters in UDPs
 

extensions/remote-process-definition/README.md

@@ -13,9 +13,10 @@ This extension enables user to load user-defined processes that are hosted exter
 The openEO API defines the `namespace` property in a process node of a process graph as follows:
 
 > The following options are predefined by the openEO API, but additional namespaces may be introduced by back-ends or in a future version of the API.
-> * `null` [...]
-> * `backend` [...]
-> * `user` [...]
+>
+> - `null` [...]
+> - `backend` [...]
+> - `user` [...]
 
 This makes it possible for this extension to add additional allowed values to the `namespace` property.