markdown and content edits

Author: KendalBond007

articles/healthcare-apis/azure-api-for-fhir/carin-implementation-guide-blue-button-tutorial.md

@@ -54,7 +54,7 @@ To assist with creation of these search parameters and profiles, we have a [samp
 
 ## Touchstone read test
 
-After testing the capabilities statement, we'll test the [read capabilities](https://touchstone.aegis.net/touchstone/testdefinitions?selectedTestGrp=/FHIRSandbox/CARIN/CARIN-4-BlueButton/01-Read&activeOnly=false&contentEntry=TEST_SCRIPTS) in Azure API for FHIR against the C4BB IG. This is a test of conformance against the eight profiles you loaded in the first test. You'll need to have resources loaded that conform to the profiles. We recommend testing against resources that you already have in your database, but we also have an [http file](https://github.com/microsoft/fhir-server/blob/main/docs/rest/C4BB/C4BB_Sample_Resources.http) available with sample resources pulled from the examples in the IG that you can use to create the resources and test against.
+After testing the capabilities statement, test the [read capabilities](https://touchstone.aegis.net/touchstone/testdefinitions?selectedTestGrp=/FHIRSandbox/CARIN/CARIN-4-BlueButton/01-Read&activeOnly=false&contentEntry=TEST_SCRIPTS) in Azure API for FHIR against the C4BB IG. This is a test of conformance against the eight profiles you loaded in the first test. You'll need to have resources loaded that conform to the profiles. We recommend testing against resources that you already have in your database, but we also have a [http file](https://github.com/microsoft/fhir-server/blob/main/docs/rest/C4BB/C4BB_Sample_Resources.http) available with sample resources pulled from the examples in the IG that you can use to create the resources and test against.
 
 :::image type="content" source="media/cms-tutorials/test-execution-results-touchstone.png" alt-text="Touchstone read test execution results.":::
 

articles/healthcare-apis/azure-api-for-fhir/centers-for-medicare-tutorial-introduction.md

@@ -29,7 +29,7 @@ There are three main pieces to the Interoperability and Patient Access ruling:
 
 * **Provider Directory API (Required July 1, 2021)** – CMS-regulated payers are required by this portion of the rule to make provider directory information publicly available via a standards-based API. Through making this information available, third-party application developers are able to create services that help patients find providers for specific care needs and clinicians find other providers for care coordination.  
 
-* **Payer-to-Payer Data Exchange (Originally required Jan 1, 2022 - [Currently Delayed](https://www.cms.gov/Regulations-and-Guidance/Guidance/Interoperability/index))** – CMS-regulated payers are, at the patient’s request, required to exchange with other payers certain patient clinical data. While there's no requirement to follow any kind of standard, applying FHIR® to exchange this data is encouraged. 
+* **Payer-to-Payer Data Exchange (Originally required Jan 1, 2022 - [Currently Delayed](https://www.cms.gov/Regulations-and-Guidance/Guidance/Interoperability/index))** – CMS-regulated payers are, at the patient’s request, required to exchange with other payers certain patient clinical data. While there's no requirement to follow any kind of standard, applying FHIR to exchange this data is encouraged. 
 
 ## Key FHIR concepts
 
@@ -62,7 +62,7 @@ The Provider Directory API describes adherence to one implementation guide.
 
 ## Touchstone
 
-To test adherence to the various implementation guides, [Touchstone](https://touchstone.aegis.net/touchstone/) is a great resource. Throughout the upcoming tutorials, we focus on ensuring that the Azure API for FHIR is configured to successfully pass various Touchstone tests. The Touchstone site has extensive documentation to help you get up and running.
+[Touchstone](https://touchstone.aegis.net/touchstone/) is a great resource to test adherence to the various implementation guides. Throughout the upcoming tutorials, we focus on ensuring that the Azure API for FHIR is configured to successfully pass various Touchstone tests. The Touchstone site has extensive documentation to help you get up and running.
 
 ## Next steps