acrolinx fixes

Author: shellyhaverkamp

articles/healthcare-apis/fhir/migration-faq.md

@@ -22,7 +22,7 @@ Due to the transition from Azure API for FHIR to Azure Health Data Services, aft
 
 ## Why is Microsoft retiring Azure API for FHIR?
 
-Azure API for FHIR is a service that was purpose built for protected health information (PHI), meeting regional compliance requirements. In March 2022, we announced the general availability of Azure Health Data Services, which enables quick deployment of managed, enterprise-grade FHIR, DICOM, and MedTech services for diverse health data integration. See below for detailed benefits of migrating to Azure Health Data Services FHIR service. With this new experience, we’re retiring Azure API for FHIR.
+Azure API for FHIR is a service that was purpose built for protected health information (PHI), meeting regional compliance requirements. In March 2022, we announced the general availability of Azure Health Data Services, which enables quick deployment of managed, enterprise-grade FHIR, DICOM, and MedTech services for diverse health data integration. With this new experience, we’re retiring Azure API for FHIR.
 
 ## What are the benefits of migrating to Azure Health Data Services FHIR service?
 
@@ -37,9 +37,9 @@ AHDS FHIR service offers a rich set of capabilities such as:
 
 ## What are the steps to enable SMART on FHIR in Azure Health Data Service FHIR service?
 
-SMART on FHIR proxy will be retiring. Organizations need to transition to the SMART on FHIR (Enhanced), which uses Azure Health Data and AI OSS samples by **September 21, 2026**. After September 21, 2026, applications relying on SMART on FHIR proxy will report errors when accessing the FHIR service.
+SMART on FHIR proxy is retiring. Organizations need to transition to the SMART on FHIR (Enhanced), which uses Azure Health Data and AI OSS samples by **September 21, 2026**. After September 21, 2026, applications relying on SMART on FHIR proxy will report errors when accessing the FHIR service.
 
-SMART on FHIR (Enhanced) provides added capabilities than SMART on FHIR proxy and can be considered to meet requirements with SMART on FHIR Implementation Guide (v 1.0.0) and §170.315(g)(10) Standardized API for patient and population services criterion.
+SMART on FHIR (Enhanced) provides more capabilities than SMART on FHIR proxy, and meets requirements in the SMART on FHIR Implementation Guide (v 1.0.0) and §170.315(g)(10) Standardized API for patient and population services criterion.
 
 ## What will happen after the service is retired on September 30, 2026?
 
@@ -51,4 +51,4 @@ After September 30, 2026 customers won't be able to:
 - Access customer support (phone, email, web)
 - Where can customers go to learn more about migrating to Azure Health Data Services FHIR service?
 
-Start with [migration strategies](migration-strategies.md) to learn more about Azure API for FHIR to Azure Health Data Services FHIR service migration. Note that the migration from Azure API for FHIR to Azure Health Data Services FHIR service involves data migration as well updating the applications to use Azure Health Data Services FHIR service. You can find more documentation on the step-by-step approach to migrating your data and applications in this [migration tool](https://github.com/Azure/apiforfhir-migration-tool/blob/main/v0/V0_README.md).
+Start with [migration strategies](migration-strategies.md) to learn more about Azure API for FHIR to Azure Health Data Services FHIR service migration. The migration from Azure API for FHIR to Azure Health Data Services FHIR service involves data migration and updating the applications to use Azure Health Data Services FHIR service. Find more documentation on the step-by-step approach to migrating your data and applications in this [migration tool](https://github.com/Azure/apiforfhir-migration-tool/blob/main/v0/V0_README.md).