Merge pull request #31 from camaraproject/jgarciahospital-patch-1

Editorial fix on RC2

code/API_definitions/population-density-data.yaml

@@ -89,11 +89,22 @@ info:
     density information in the specified area.
 
     # Authorization and Authentication
-    CAMARA guidelines defines a set of authorization flows which can grant API clients access to the API functionality, as outlined in the document [CAMARA-API-access-and-user-consent.md](https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-API-access-and-user-consent.md). Which specific authorization flows are to be used will be determined during onboarding process, happening between the API Client and the Telco Operator exposing the API, taking into account the declared purpose for accessing the API, while also being subject to the prevailing legal framework dictated by local legislation.
-    It is important to remark that in cases where personal user data is processed by the API, and users can exercise their rights through mechanisms such as opt-in and/or opt-out, the use of 3-legged access tokens becomes mandatory. This measure ensures that the API remains in strict compliance with user privacy preferences and regulatory obligations, upholding the principles of transparency and user-centric data control.
+    CAMARA guidelines defines a set of authorization flows which can grant API clients access
+    to the API functionality, as outlined in the document [CAMARA-API-access-and-user-consent.md](https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-API-access-and-user-consent.md).
+    Which specific authorization flows are to be used will be determined during
+    onboarding process, happening between the API Client and the Telco Operator
+    exposing the API, taking into account the declared purpose for accessing the API,
+    while also being subject to the prevailing legal framework dictated by local legislation.
+    It is important to remark that in cases where personal user data is processed by the API,
+    and users can exercise their rights through mechanisms such as opt-in and/or opt-out,
+    the use of 3-legged access tokens becomes mandatory. This measure ensures that the API remains
+    in strict compliance with user privacy preferences and regulatory obligations, upholding the 
+    principles of transparency and user-centric data control.
 
-    Population Density Data API ensures the usage of anonymized information and do not trear personal data neither as input nor output. 
-    Therefore, the acceess to Population Density Data API is defined as Client Credentials - 2-legged as described in [CAMARA-API-access-and-user-consent.md - Client Credentials](https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-API-access-and-user-consent.md#client-credentials)
+    Population Density Data API ensures the usage of anonymized information and do not treat
+    personal data neither as input nor output. 
+    Therefore, the acceess to Population Density Data API is defined as 
+    Client Credentials - 2-legged as described in [CAMARA-API-access-and-user-consent.md - Client Credentials](https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-API-access-and-user-consent.md#client-credentials)
 
     # Further info and support