[ERSSUP-89272]-[]-[changed some text]-[NR]

Author: Rastogi

specification/components/stu3/schemas/endpoints/a016-book-or-defer-appointment.yaml

@@ -31,7 +31,7 @@ description: |
 
   When appointment slots are booked using this endpoint, it may be necessary to provide the named clinician details. This is because slots can be setup with or without a named clinician. Your integrated application must support both scenarios.
 
-  When booking a slot using [[HYPERLINK_A016]], the named clinician details must be added to the “Appointment.partcipant” list. As shown in the “Booking with named clinician” example.
+  When booking a slot using [[HYPERLINK_A016]], the named clinician details must be added to the "Appointment.partcipant" list. As shown in the "Booking with named clinician" example.
 
   ## Use case
   As an authenticated user

specification/components/stu3/schemas/endpoints/a025-retrieve-advice-and-guidance-conversation.yaml

@@ -5,8 +5,6 @@ description: |
   Use this endpoint to retrieve the advice and guidance conversation between the referring organisation 
   and service providing organisation.
 
-  A 'conversation' takes the form of the messages between a referrer (seeking advice) and a provider or specialist. Messages can include attachments.
-
   A conversation takes the form of messages between a referrer (seeking advice) and a provider or specialist. Messages can include file attachments. These must be retrieved via [[HYPERLINK_A042]]
 
   [Read](https://digital.nhs.uk/developer/guides-and-documentation/building-healthcare-software/referrals-and-bookings/e-referral-service/retrieve-clinical-referral-information-as-a-service-provider) our building healthcare software guide for detailed information.

specification/e-referrals-service-api.yaml

@@ -128,11 +128,9 @@ info:
       
     ### Healthcare worker, user-restricted access
 
-    This access mode is [[HYPERLINK_PRODUCTION]]. We are onboarding Partners to use it.
-    
-    This access mode allows you to use all endpoints. A human user must be present and authenticated.
-    
-    For more information, please see [[HYPERLINK_NETWORK_ACCESS]].
+    This access mode is [[HYPERLINK_PRODUCTION]], meaning:
+      - we avoid making routine [breaking changes](https://digital.nhs.uk/services/e-referral-service/api/updates-and-releases/sunsetting-policy#breaking-changes), except in exceptional circumstances
+      - if we need to deprecate an endpoint, we will give advance notice on our [board](https://digital.nhs.uk/services/e-referral-service/api/updates-and-releases/deprecation-notices). Our [sunsetting page](https://digital.nhs.uk/services/e-referral-service/api/updates-and-releases/sunsetting-policy) details our deprecation and retirement policy.
 
     ### Roadmap
 
@@ -251,7 +249,7 @@ info:
 
     ## Onboarding
 
-    You need to get your software approved by us before you can go live with this API. We call this onboarding. The onboarding process can sometimes be quite long, so it’s worth planning well ahead.
+    You need to get your software approved by us before you can go live with this API. We call this onboarding. The onboarding process can sometimes be quite long, so it's worth planning well ahead.
 
     We use the Supplier Conformance Assessment List (SCAL) process. [Learn more](https://digital.nhs.uk/services/e-referral-service/api/integration-process/stage-1-design#1-7-learn-how-to-onboard) about onboarding.