Additional updates and formatting

Author: msjasteppe

articles/healthcare-apis/fhir/convert-data-faq.md

@@ -46,12 +46,6 @@ For more information, see [Access the FHIR service in Azure Health Data Services
 
 The experience and core `$convert-data` operation functionality is similar for both Azure API for FHIR and the FHIR service in Azure Health Data Services(../../healthcare-apis/fhir/overview.md). The only difference exists in the setup for the Azure API for FHIR version of the `$convert-data` operation, which requires assigning permissions to the right resources. 
 
-## Why are my dates being converted when transforming JSON data?
- 
-Its possible for dates supplied within JSON data to be returned in a different format than what was supplied. During deserialization of the JSON payload, string values, which are identified as dates get converted into .NET DateTime objects. These objects then get converted back to strings before going through the Liquid template engine. This conversion can cause the date value to be reformatted and represented in the local timezone of the FHIR service.
-
-The coercion of strings to .NET DateTime objects can be disabled using the boolean parameter `jsonDeserializationTreatDatesAsStrings`. When set to `true`, the supplied data is treated as a string and won't be modified before being supplied to the Liquid engine.
-
 Learn more:
 
 [Azure API for FHIR: Data conversion for Azure API for FHIR](../../healthcare-apis/azure-api-for-fhir/convert-data.md)
@@ -76,6 +70,12 @@ Yes. You can use the [FHIR Converter Visual Studio Code extension](https://mar
 
 Yes. It’s possible to store and reference custom templates. For more information, see [Configure settings for $convert-data by using the Azure portal](convert-data-configuration.md).
 
+## Why are my dates being converted when transforming JSON data?
+ 
+Its possible for dates supplied within JSON data to be returned in a different format than what was supplied. During deserialization of the JSON payload, string values, which are identified as dates get converted into .NET DateTime objects. These objects then get converted back to strings before going through the Liquid template engine. This conversion can cause the date value to be reformatted and represented in the local timezone of the FHIR service.
+
+The coercion of strings to .NET DateTime objects can be disabled using the boolean parameter `jsonDeserializationTreatDatesAsStrings`. When set to `true`, the supplied data is treated as a string and won't be modified before being supplied to the Liquid engine.
+
 ## If I need support with troubleshooting, where can I go?
 
 Depending on the version of `$convert-data` you’re using, you can:

articles/healthcare-apis/fhir/convert-data-troubleshoot.md

@@ -27,19 +27,19 @@ Any loops or iterations in the templates can have large impacts on performance.
 The `$convert-data` operation applies post processing logic after the template is applied to the input. This post processing logic can result in the output looking different or unexpected errors compared to if you ran the default Liquid template directly. Post processing ensures the output is valid JSON and removes any duplicates based on the ID properties generated for resources in the template. To see the post processing logic in more detail, see the [FHIR-Converter GitHub repository](https://github.com/microsoft/FHIR-Converter/blob/main/src/Microsoft.Health.Fhir.Liquid.Converter/OutputProcessors/PostProcessor.cs).
 
 ## Message size
-There isn’t a hard limit on the size of the messages allowed for the `$convert-data` operation, however, for content with a request size  greater than 10 MB, server 500 errors are possible. If you're receiving 500 server errors, ensure your requests are under 10 MB. 
+There isn’t a hard limit on the size of the messages allowed for the `$convert-data` operation, however, for content with a request size  greater than 10 MB, server 500 errors are possible. If you're receiving 500 server errors, ensure your requests are under 10 MB.
+
+## Why are my dates being converted when transforming JSON data?
+ 
+Its possible for dates supplied within JSON data to be returned in a different format than what was supplied. During deserialization of the JSON payload, string values, which are identified as dates get converted into .NET DateTime objects. These objects then get converted back to strings before going through the Liquid template engine. This conversion can cause the date value to be reformatted and represented in the local timezone of the FHIR service.
+
+The coercion of strings to .NET DateTime objects can be disabled using the boolean parameter `jsonDeserializationTreatDatesAsStrings`. When set to `true`, the supplied data is treated as a string and won't be modified before being supplied to the Liquid engine. 
 
 ## Default templates and customizations
 Default template implementations for many common scenarios can be found on the [FHIR-Converter GitHub repository](https://github.com/microsoft/FHIR-Converter/tree/main/data/Templates). The default templates can be used as a guide and reference for customizing and creating your own templates. In addition to the default templates, the `$convert-data` operation supports several customer Liquid [filters and tags](https://github.com/microsoft/FHIR-Converter/blob/main/docs/Filters-and-Tags.md) that help simplify common scenarios. 
 
 ## Debugging and testing
 In addition to testing templates on an instance of the service, a [Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-health-fhir-converter) is available. The extension can be used to modify templates and test them with sample data payloads. There are also several existing test scenarios in the [FHIR Converter GitHub repository](https://github.com/microsoft/FHIR-Converter/tree/main/src/Microsoft.Health.Fhir.Liquid.Converter.FunctionalTests) that can be used as a reference.
-
-## Why are my dates being converted when transforming JSON data?
- 
-Its possible for dates supplied within JSON data to be returned in a different format than what was supplied. During deserialization of the JSON payload, string values, which are identified as dates get converted into .NET DateTime objects. These objects then get converted back to strings before going through the Liquid template engine. This conversion can cause the date value to be reformatted and represented in the local timezone of the FHIR service.
-
-The coercion of strings to .NET DateTime objects can be disabled using the boolean parameter `jsonDeserializationTreatDatesAsStrings`. When set to `true`, the supplied data is treated as a string and won't be modified before being supplied to the Liquid engine.
 
 ## Next steps
 [Overview of $convert-data](convert-data-overview.md)
@@ -48,4 +48,4 @@ The coercion of strings to .NET DateTime objects can be disabled using the boole
 
 [$convert-data-faq](convert-data-faq.md).
 
-[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]
+[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/release-notes-2024.md

@@ -21,7 +21,7 @@ This article describes features, enhancements, and bug fixes released in 2024 fo
 
 ### FHIR service
 
-#### Disabling .NET DataTime objects from JSON data supplied to the $convert-data operation
+#### Disabling .NET DataTime objects from JSON data supplied to $convert-data
 
 It's possible for dates supplied within JSON data to be returned in a different format than what was supplied. During deserialization of the JSON payload, string values, which are identified as dates get converted into .NET DateTime objects. These objects then get converted back to strings before going through the Liquid template engine. This conversion can cause the date value to be reformatted and represented in the local timezone of the FHIR service.