a few typoes and trivial wording updates

paths/customer_careprogram.yaml

@@ -4,7 +4,8 @@ get:
     - Customer management
   summary: Get all practices and their participation in any care program.
   description: |-
-    Enumerates all practices for which the current customer (user) is responsible in the care group. The customer identified with the JWT must be the group manager, otherwise the API will respond with a HTTP not authorized response. The care group must also be responsible for the underlying practices. Some care groups are organized in a way that they are not allowed to process data of the member practices. These groups are ignored by this API and produce empty output.
+    Enumerates all practices for which the current customer (user) is responsible in the care group. The customer identified with the JWT must be the group manager.
+    The care group must also be responsible for the underlying practices. Some care groups are organized in a way that they are not allowed to process data of the member practices.
   parameters: 
     - name: refDate
       in: query
@@ -49,13 +50,18 @@ post:
   operationId: setCustomerCareProgram
   summary: Add a practice to a care program.
   description: |-
-    Allows a care group manager to classify practices into care groups (ziektebeelden, ketens). 
+    Allows a care group manager to classify practices into care groups (ziektebeelden, ketens).
     
-    The caller must authorize itself as a care group (manager). If this requirement is not met, a 403 response is send back. 
+    The caller must authorize itself as a care group (manager).
     
-    The care group must be allowed to take responsibility for the practices it holds. If not, the request is ignored and an empty Json-object is send back to the caller. Indicating that processing was not successful. The practice must be one of the care group practices. If not, the request is ignored and an empty Json-object is send back to the caller. In all other cases a Json-object containing the same data as in the request with a timestamp added is send back in the response.
-
-    The operation is idempotent for the combination of: `careprogram`, `agb`, `periodStart` and `periodEnd`. If these are the same in any _subsequent call_ the request is processes as being fully accepted, showing the request data in the response, but the `employee` and `timestamp` aren't updated in the database. The timestamp of the original submit to this API is added to the response.
+    The care group must be allowed to take responsibility for the practices it holds. If not, the request is ignored and an empty Json-object is sent back to the caller. Indicating that processing was not successful.
+    
+    The practice must be one of the care group practices. If not, the request is ignored and an empty Json-object is sent back to the caller.
+    
+    In all other cases a Json-object containing the same data as in the request with a timestamp added is sent back in the response.
+    
+    The operation is idempotent for the combination of: `careprogram`, `agb`, `periodStart` and `periodEnd`. If these are the same in any _subsequent call_ the request is processed as being fully accepted, showing the request data in the response,
+    but the `employee` and `timestamp` aren't updated in the database. The timestamp and employee of the original submit to this API is included in the response instead of the provided values.
   requestBody: 
     content: 
       'application/x-www-form-urlencoded':
@@ -86,7 +92,7 @@ post:
   responses:
     '200':
       description: |-
-        If and only if, the request was successful processed down to the database, a Json-object with the following properties is send back to the caller, otherwise a non 200 HTTP response.
+        If and only if, the request was successful processed down to the database, a Json-object with the following properties is sent back to the caller, otherwise a non 200 HTTP response.
       content:
         'application/json':
           schema:
@@ -108,4 +114,3 @@ post:
       $ref: '../zoo-api.yaml/#/components/responses/NoAuth'
     '403':
       $ref: '../zoo-api.yaml/#/components/responses/NoAccess'
-      

paths/customer_careprogram_periodEnd.yaml

@@ -4,7 +4,8 @@ post:
   operationId: setCustomerCareProgramPeriodEnd
   summary: Update the period end of a practice in a care program.
   description: |-
-    This API allows to update only the period end date of the participation of a practice in a care program. This is equivalent to submitting a new participation to this API, but only the `periodStart` parameter is not needed.
+    Updates only the period end date of the participation of a practice in a care program. This is equivalent to submitting a new participation to this API, but, the `periodStart` parameter is not needed.
+    Requires that this practice already participates in the provided care program (and that participation will get its end date updated).
   requestBody: 
     content: 
       'application/x-www-form-urlencoded':
@@ -30,7 +31,7 @@ post:
   responses:
     '200':
       description: |-
-        If the request was successful processed a Json-object with the following properties is send back to the caller, otherwise a non 200 HTTP response. 
+        If the request was successfully processed, a Json-object with the following properties is send back to the caller, otherwise a non 200 HTTP response.
       content:
         'application/json':
           schema: