Updates based on feedback

Author: msjasteppe

articles/healthcare-apis/iot/frequently-asked-questions.md

@@ -35,6 +35,10 @@ The MedTech service supports the [HL7 FHIR® R4](https://www.hl7.org/impleme
 
 The MedTech service requires device and FHIR destination mappings to perform normalization and transformation processes on device message data. To learn how the MedTech service transforms device message data into [FHIR Observations](https://www.hl7.org/fhir/observation.html), see [Understand the MedTech service device message processing stages](understand-service.md). 
 
+### Is JSONPATHContent still supported by the MedTech service device mapping?
+
+Yes. JSONPathContent can be used as a template type within [CollectionContent](overview-of-device-mapping.md#collectioncontent). It's recommended that CalculatedContent is used as it supports all of the features of JSONPathContent with extra support for more advanced features.
+
 ### How long does it take for device message data to show up in the FHIR service?
 
 The MedTech service buffers [FHIR Observations](https://www.hl7.org/fhir/observation.html) created during the transformation stage and provides near real-time processing. However, this buffer can potentially delay the persistence of FHIR Observations to the FHIR service up to ~five minutes. To learn how the MedTech service transforms device message data into FHIR Observations, see [Understand the MedTech service device message processing stages](understand-service.md).

articles/healthcare-apis/iot/overview-of-device-mapping.md

@@ -66,7 +66,7 @@ You can use these template types within CollectionContent depending on your use
 
 and/or
 
-- [IotJsonPathContent](how-to-use-iotjsonpathcontenttemplate-mappings.md) for device messages being routed through [Azure IoT Hub](/azure/iot-hub/iot-concepts-and-iot-hub) to your MedTech service event hub. IotJsonPathContent supports [JSONPath](https://goessner.net/articles/JsonPath/), [JMESPath](https://jmespath.org/), and [JMESPath functions](https://jmespath.org/specification.html#built-in-functions). The MedTech service [custom functions](how-to-use-custom-functions.md) aren't supported using IotJsonPathContent. 
+- [IotJsonPathContent](how-to-use-iotjsonpathcontenttemplate-mappings.md) for device messages being routed through [Azure IoT Hub](/azure/iot-hub/iot-concepts-and-iot-hub) to your MedTech service event hub. IotJsonPathContent supports [JSONPath](https://goessner.net/articles/JsonPath/). 
 
 :::image type="content" source="media/overview-of-device-mapping/device-mapping-templates-diagram.png" alt-text="Diagram showing MedTech service device mapping templates architecture." lightbox="media/overview-of-device-mapping/device-mapping-templates-diagram.png":::