diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/API-Spec-Change-Log/1.3.0.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/API-Spec-Change-Log/1.3.0.page.md
index 49c98b98..375c018d 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/API-Spec-Change-Log/1.3.0.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/API-Spec-Change-Log/1.3.0.page.md
@@ -15,8 +15,8 @@ topic: TRN-API-1.3.0
| Change | Description | Impact |
|----------------------------------------------|---------------------------------------------------------------------|--------|
| {{render:handshake}}
- Additional patient demographic parameters added to GET /Appointment | 1.9.0 | Patient demographic parameters (Name, Date of Birth and Address) added to support patient lookup for cancellation and update workflows. | Addition |
-| {{render:handshake}}
- - Additional patient demographic parameters added to GET /ServiceRequest | 1.9.0 | Patient demographic parameters (Name, Date of Birth and Address) added to support patient lookup for cancellation and update workflows. | Addition |
-| Fixed incorrect character display on GET /Slot description | 1.9.0 | Character display for a double quote was displaying oddly. | correction |
+| {{render:handshake}}
- Additional patient demographic parameters added to GET /ServiceRequest | 1.9.0 | Patient demographic parameters (Name, Date of Birth and Address) added to support patient lookup for cancellation and update workflows. | Addition |
+| Fixed incorrect character display on GET /Slot description | 1.9.0 | Character display for a double quote was illegible. | correction |
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/API-Spec-Change-Log/Global.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/API-Spec-Change-Log/Global.page.md
index 110bfb2c..9bff9a62 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/API-Spec-Change-Log/Global.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/API-Spec-Change-Log/Global.page.md
@@ -9,8 +9,8 @@ topic: TRN-API-global
| Change | BaRS Version | Description | Impact |
|------------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|
| {{render:handshake}}
- Additional patient demographic parameters added to GET /Appointment | 1.9.0 | Patient demographic parameters (Name, Date of Birth and Address) added to support patient lookup for cancellation and update workflows. | Addition |
-| {{render:handshake}}
- - Additional patient demographic parameters added to GET /ServiceRequest | 1.9.0 | Patient demographic parameters (Name, Date of Birth and Address) added to support patient lookup for cancellation and update workflows. | Addition |
-| Fixed incorrect character display on GET /Slot description | 1.9.0 | Character display for a double quote was displaying oddly. | correction |
+| {{render:handshake}}
- Additional patient demographic parameters added to GET /ServiceRequest | 1.9.0 | Patient demographic parameters (Name, Date of Birth and Address) added to support patient lookup for cancellation and update workflows. | Addition |
+| Fixed incorrect character display on GET /Slot description | 1.9.0 | Character display for a double quote was illegible. | correction |
| Removal of use-context HTTP header | 1.8.2 |Restricted the use of the use-context header to non-write operations | correction |
| Improvments to header documentation | 1.8.2 |Added better explanations for most of the headers needed | Addition |
| Addition of the use-context HTTP header | 1.8.1 | A new header to assist in {{pagelink:core-EndToEndWorkflow-Logging-1.0.5, text: audting and logging}} | Addition |
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.0/Standard-Pattern-Composite-Messages/Find-Resource.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.0/Standard-Pattern-Composite-Messages/Find-Resource.md
index 0aae8726..d12ea91a 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.0/Standard-Pattern-Composite-Messages/Find-Resource.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.0/Standard-Pattern-Composite-Messages/Find-Resource.md
@@ -7,7 +7,7 @@ topic: core-SPFindResource-1.3.0
A prerequisite, when undertaking any update routine, is to perform a read (GET) of either the booking or referral to be amended (including cancellation routines). This ensures the Sender has the most recent version of the resource being updated and verifies they can proceed with the workflow. For example, to engage in a cancellation workflow, the status of the entity being cancelled must currently be classed as 'active'.
-As a first step the Sender **must** obtain the (resource).Id of the booking (Appointment) or referral/validation (ServiceRequest) and they are several ways to do this. If the Sender made the original request, they will likely know this and can directly request the specific resource to check the status, using the GET (read) by Id endpoint. Alternatively, if they did not generate the original request (or there was a problem with the synchronous response being received) the full resource can be obtained by searching for active bookings or referrals for the patient, either by using the national identifier (NHS No.) or patient demographics (Name (as defined by [FHIR](https://simplifier.net/packages/hl7.fhir.r4.core/4.0.1/files/2834389 )), Date of Birth, Home Address Postcode). This will return a (FHIR) bundle of responses (typically, containing only one entry) which the Sender can match, based on dateTime (elements dependent on resource) and use-case category values, to identify the resource of interest. If the Sender cannot accurately match the resource they should advise the user the update cannot be performed and to revert to manual options instead. The diagram under 'Options for obtaining booking or referral' outlines the options above.
+As a first step the Sender **must** obtain the (resource).Id of the booking (Appointment) or referral/validation (ServiceRequest) and there are several ways to do this. If the Sender made the original request, they will likely know this and can directly request the specific resource to check the status, using the GET (read) by Id endpoint. Alternatively, if they did not generate the original request (or there was a problem with the synchronous response being received) the full resource can be obtained by searching for active bookings or referrals for the patient, either by using the national identifier (NHS No.) or patient demographics (Name (as defined by [FHIR](https://simplifier.net/packages/hl7.fhir.r4.core/4.0.1/files/2834389 )), Date of Birth, Home Address Postcode). This will return a (FHIR) bundle of responses (typically, containing only one entry) which the Sender can match, based on dateTime (elements dependent on resource) and use-case category values, to identify the resource of interest. If the Sender cannot accurately match the resource they should advise the user the update cannot be performed and to revert to manual options instead. The diagram under 'Options for obtaining booking or referral' outlines the variations above.
#### Options for obtaining booking or referral