Update Changelog.md

releases/3.2.0/Changelog.md

@@ -33,7 +33,7 @@ The following additional issues were raised during the public review and approve
 | --- | --- | --- | --- | --- |
 | P3 | - | The range of Administrative Territorial Unit is changed to dct:Location, the usage not with recommendation for ATU is kept. | Use of specific code list did not align with definition, usage note and Style Guide rule [CMC-R14](https://semiceu.github.io/style-guide/1.0.0/gc-conceptual-model-conventions.html#sec:cmc-r14). | [#123](https://github.com/SEMICeu/CPSV-AP/issues/123) |
 | R3 | - | The optional relationship dct:isPartOf towards dcat:Dataset from cv:Evidence and cv:Ouput is added. | The need to relate cv:Output and cv:Evidence to dcat:Dataset using an optional relation was expressed by the community. Specifically it was requested for a relation for Once Only implementations where evidences and outputs are required to be related to a Dataset. | [#125](https://github.com/SEMICeu/CPSV-AP/issues/125) |
-| R3 | - | 1) Explicitly add the “execution” use case to the introduction of the specification and reference the use case in cv:Evidence & cv:Output's usage note. 2) Update language definition to allow description and execution of a Public Service. 3) Update the _relatedDocumentation_ usage note. | 1) How to use cv:Evidence and cv:Output when describing a cpsv:PublicService? 2) Update Language definition to allow both usages of CPSV-AP for the description and execution of Public Services because it does not allow the usage of CPSV-AP in both high-level use cases described below. Therefore, it will be rephrased. 3) Update the relatedDocumentation usage note to allow the “execution” use case, making it more generic. | [#128](https://github.com/SEMICeu/CPSV-AP/issues/128) |
+| R3 | - | 1) Explicitly add the “execution” use case to the introduction of the specification and reference the use case in cv:Evidence & cv:Output's usage note. 2) Update language definition to allow description and execution of a Public Service. 3) Update the _relatedDocumentation_ usage note. | 1) How to use cv:Evidence and cv:Output when describing a cpsv:PublicService? 2) Update Language definition to allow both usages of CPSV-AP for the description and execution of Public Services because it does not allow the usage of CPSV-AP in both high-level use cases described below. 3) Update the relatedDocumentation usage note to allow the “execution” use case, making it more generic. | [#128](https://github.com/SEMICeu/CPSV-AP/issues/128) |