Feedback updates

Author: msjasteppe

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

@@ -72,7 +72,7 @@ Yes. It’s possible to store and reference custom templates. For more informati
 
 ## 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.
+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 strings that 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.
 

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

@@ -31,7 +31,7 @@ There isn’t a hard limit on the size of the messages allowed for the `$convert
 
 ## 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.
+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 strings that 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. 
 

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

@@ -21,9 +21,9 @@ This article describes features, enhancements, and bug fixes released in 2024 fo
 
 ### FHIR service
 
-#### Disabling .NET DataTime objects from JSON data supplied to $convert-data
+#### $convert-data: Allow dates in JSON data to be treated as strings
 
-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.
+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 strings that 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.