Merge pull request #174 from NHSDigital/ms-AMB-999-AMP-392-MESH-based-API-tweaks

Revised diagram

Author: SachinPath

specification/ambulance-analytics.yaml

@@ -19,7 +19,7 @@ info:
 
     The API is asynchronous - when you submit data, it acknowledges receipt without validating or processing the data first. To receive error notifications, you need to use [MESH](https://digital.nhs.uk/services/message-exchange-for-social-care-and-health-mesh). The following diagram illustrates the end-to-end process:
 
-    ![Ambulance Overview](https://github.com/NHSDigital/ambulance-analytics-api/blob/master/specification/diagrams/ADSOverview.svg?raw=true)
+    ![Ambulance Overview](https://github.com/NHSDigital/ambulance-analytics-api/blob/master/specification/diagrams/ADSOverview2.svg?raw=true)
 
     The following describes the end-to-end process:
     1. The ambulance trust system sends the ambulance data to the Ambulance Data Submission API.
@@ -33,7 +33,7 @@ info:
     This API can only be used where there is a legal basis to do so. Make sure you have a valid use case before you go too far with your development. You must do this before you can go live (see ‘Onboarding’ below).
 
     ## Related APIs
-    Use [Messaging Exchange for Social care and Health (MESH)](https://meshapi.docs.apiary.io/) to receive error notifications from DPS for this API.
+    Use [Messaging Exchange for Social care and Health (MESH)](https://digital.nhs.uk/services/message-exchange-for-social-care-and-health-mesh) to receive error notifications from DPS for this API.
 
     ## API status and roadmap
     This API is [stable](https://digital.nhs.uk/developer/guides-and-documentation/reference-guide#api-status):