minor adjustments

Author: shellyhaverkamp

articles/healthcare-apis/azure-api-for-fhir/index.yml

@@ -28,7 +28,7 @@ landingContent:
       - linkListType: how-to-guide
         links:
           - text: Migrate to Azure Health Data Services
-            url: ../../fhir/migration-strategies.md
+            url: ../fhir/migration-strategies.md
 
   - title: Access Azure API for FHIR
     linkLists:

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

@@ -10,36 +10,36 @@ author: evachen96
 ms.date: 9/27/2023
 ---
 
-# Migration from Azure API for FHIR FAQ
+# FAQ about migration from Azure API for FHIR
 
-**1. When will Azure API for FHIR be retired?**
+## When will Azure API for FHIR be retired?
 
 Azure API for FHIR will be retired on September 30, 2026.
 
-**2. Why is Microsoft retiring Azure API for FHIR?**
+## 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.
 
-**3. What are the benefits of migrating to Azure Health Data Services FHIR service?**
+## What are the benefits of migrating to Azure Health Data Services FHIR service?
 
 AHDS FHIR service offers a rich set of capabilities such as:
 
-- Consumption-based pricing model where customers pay only for used storage & throughput
+- Consumption-based pricing model where customers pay only for used storage and throughput
 - Support for transaction bundles
 - Chained search improvements
-- Improved ingress & egress of data with \$import, \$export including new features such as incremental import (preview)
+- Improved ingress and egress of data with \$import, \$export including new features such as incremental import (preview)
 - Events to trigger new workflows when FHIR resources are created, updated or deleted
 - Connectors to Azure Synapse Analytics, Power BI and Azure Machine Learning for enhanced analytics
 
-**4. SMART on FHIR Proxy is planned for deprecation in Gen2. When we migrate from Gen1, what are the steps for enabling SMART on FHIR in Gen2?**
+## SMART on FHIR Proxy is planned for deprecation in Gen2. When we migrate from Gen1, what are the steps for enabling SMART on FHIR in Gen2?
 
 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 in 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.
 
-**5. What will happen after the service is retired on September 30, 2026?**
+## What will happen after the service is retired on September 30, 2026?
 
-Customers won't be able to do the following:
+After September 20, 2026 customers won't be able to:
 
 - Create or manage Azure API for FHIR accounts
 - Access the data through the Azure portal or APIs/SDKs/client tools
@@ -49,13 +49,13 @@ Customers won't be able to do the following:
 
 Start with \<Link to Azure Docs migration guidance \> to learn more about Azure API for FHIR to Azure Health Data Services FHIR service migration. Please be advised 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 \<Link to github repo\>.
 
-**6.Where can customers go to get answers to their questions?**
+## Where can customers go to get answers to their questions?
 
 There are multiple ways to get your questions answered.
 
 - Get answers from community experts in Microsoft Q&A \<Link to Microsoft Q&A Page\>
 
-- If you have a support plan and require technical support, [contact us.](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest)
+- If you have a support plan and require technical support, [contact us](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
 
 1. For **Issue type**, select **Technical**.
 

articles/healthcare-apis/includes/healthcare-apis-azure-api-fhir-retirement.md

@@ -7,7 +7,8 @@ ms.date: 09/27/2023
 ms.author: jasteppe
 ---
 
-[!Important]
-**Azure API for FHIR will be retired on September 30, 2026.** Follow the [migration guidance](../fhir/migration-strategies.md) to transition to Azure Health Data Services FHIR service by that date. Due to the transition of Azure API for FHIR to Azure Health Data Services, new deployments won't be allowed beginning April 1, 2025. 
+> [!IMPORTANT]
+> **Azure API for FHIR will be retired on September 30, 2026.** Follow the [migration guidance](../fhir/migration-strategies.md) to transition to Azure Health Data Services FHIR service by that date. Due to the transition of Azure API for FHIR to Azure Health Data Services, new deployments won't be allowed beginning April 1, 2025. 
 
-[Azure Health Data Services FHIR service](../healthcare-apis-overview.md) is the evolved version of Azure API for FHIR that enables customers to manage [FHIR](../fhir/overview.md), DICOM, and MedTech services with integrations into other Azure services. 
+[Azure Health Data Services FHIR service](../healthcare-apis-overview.md) is the evolved version of Azure API for FHIR that enables customers to manage [FHIR](../fhir/overview.md), DICOM, and MedTech services with integrations into other Azure services.
+ 

articles/healthcare-apis/index.yml

@@ -11,7 +11,7 @@ metadata:
   ms.topic: hub-page # Required
   author: msjasteppe #Required; your GitHub user alias, with correct capitalization.
   ms.author: jasteppe #Required; microsoft alias of author; optional team alias.
-  ms.date: 09/11/2023 #Required; mm/dd/yyyy format.
+  ms.date: 09/27/2023 #Required; mm/dd/yyyy format.
 
 highlightedContent:
   items:
@@ -26,7 +26,7 @@ highlightedContent:
           url: ./get-access-token.md
        -  title: Migrate your data from Azure API for FHIR
           itemType: how-to-guide
-          url: ./migration-strategies.md
+          url: ./fhir/migration-strategies.md    
        -  title: Azure Health Data Services 
           itemType: training
           url: https://learn.microsoft.com/training/browse/?term=iot&terms=health%20data%20services