Replacing Onboarding links

Author: luci-davies

guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/About-BaRS/Quick-Start-Guide.page.md

@@ -11,7 +11,7 @@ We recommend reading the following documentation as part of the discovery stage
 * [BaRS FHIR API specification](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1.3.0)
 
 ### Onboarding
-{{pagelink:Home/Build/Testing-and-Environments/Onboarding.page.md, text:Onboarding}} with our platform is a self-service process. This step is required to make requests of the BaRS API and have requests forwarded to your endpoint, as a Receiver. This **must** occur on both Integration (INT) and Production environments. The {{pagelink:Home/Build/Testing-and-Environments/Onboarding.page.md, text: full step-by-step onboarding guide}} can be followed by any solution on either environment. 
+{{pagelink:Testing-and-Environments, text:Connecting to environments}} on our platform is a self-service process. This step is required to make requests of the BaRS API and have requests forwarded to your endpoint, as a Receiver. This **must** occur on both Integration (INT) and Production environments.  
 
 Full details of the security model adopted by the platform can be found under the [security](https://digital.nhs.uk/developer/guides-and-documentation/security-and-authorisation/application-restricted-restful-apis-signed-jwt-authentication) section.
 

guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/BaRS-Principles-and-Prerequisites/Principles-and-prerequisites.page.md

@@ -26,7 +26,7 @@ This page describes BaRS principles and prerequisites for suppliers. Elements of
 3. Systems MUST support JSON formats for all API interactions
 4. Systems SHOULD have a FHIR Server or FHIR functionality in place
 5. Systems SHOULD implement RESTful behaviour patterns
-6. System Suppliers MUST complete the {{pagelink:Home/Build/Testing-and-Environments/Onboarding.page.md, text:BaRS onboarding process}}
+6. System Suppliers MUST complete the {{pagelink:Testing-and-Environments, text:BaRS connecting to environments process}}
 7. Systems MUST support Service Discovery
 
 <br>

guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Certificates.page.md

@@ -7,7 +7,7 @@ The BaRS API and supplier solution will be secured by HTTPS/TLS, for both inboun
 
 In order to establish a connection to and from any environment, a chain of trust must be set up using the certificates detailed below. 
 
-For information on obtaining certificates as a Receiver see the {{pagelink:onboarding}} section.
+For information on obtaining certificates as a Receiver see the {{pagelink:Testing-and-Environments, text: Connect as a receiver}} section.
 
 ## Inbound