Update release note with suggested change

doc/release-notes/9276-allow-flexible-params-in-retrievaluri-cvoc.md

@@ -8,8 +8,7 @@ You are now able to add HTTP request headers required by the service you are imp
 
 #### Flexible params in retrievalUri
 
-You can now use `managed-fields` field names `term-uri-field` field name as parameters of `retrieval-uri`.
-`{0}` default parameter is still working for a question of backward compatibility.
+You can now use `managed-fields` field names as well as the `term-uri-field` field name as parameters in the `retrieval-uri` when configuring an external vocabulary service. `{0}` as an alternative to using the `term-uri-field` name is still supported for backward compatibility.
 Also you can specify if the value must be url encoded with `encodeUrl:`. (#10404)
 
 For example : `"retrieval-uri": "https://data.agroportal.lirmm.fr/ontologies/{keywordVocabulary}/classes/{encodeUrl:keywordTermURL}"`