Fixing build warnings

Author: msjasteppe

.openpublishing.redirection.healthcare-apis.json

@@ -637,7 +637,7 @@
         "redirect_url": "/azure/healthcare-apis/iot/how-to-use-calculatedcontent-mappings",
         "redirect_document_id": false
     },
-    {   "source_path_from_root": "/articles/healthcare-apis/iot/calculatedcontenttemplate-mappings.md",
+    {   "source_path_from_root": "/articles/healthcare-apis/iot/how-to-use-calculatedcontenttemplate-mappings.md",
         "redirect_url": "/azure/healthcare-apis/iot/how-to-use-calculatedcontent-mappings",
         "redirect_document_id": false
     },

articles/healthcare-apis/iot/how-to-configure-device-mappings.md

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 1/12/2023
+ms.date: 02/09/2023
 ms.author: jasteppe
 ---
 
@@ -198,7 +198,7 @@ You can define one or more templates within the MedTech service device mapping.
 
 |Template Type|Description|
 |-------------|-----------|   
-|[CalculatedContentTemplate](how-to-use-calculatedcontenttemplate-mappings.md)|A template that supports writing expressions using one of several expression languages. Supports data transformation via the use of JMESPath functions.|
+|[CalculatedContent](how-to-use-calculatedcontent-mappings.md)|A template that supports writing expressions using one of several expression languages. Supports data transformation via the use of JMESPath functions.|
 |[IotJsonPathContentTemplate](how-to-use-iot-jsonpath-content-mappings.md)|A template that supports messages sent from Azure Iot Hub or the Legacy Export Data feature of Azure Iot Central.
 
 > [!TIP]

articles/healthcare-apis/iot/how-to-use-calculatedcontent-mappings.md

@@ -13,7 +13,7 @@ ms.author: jasteppe
 
 This article describes how to use CalculatedContent mappings with MedTech service device mappings.
 
-## CalculatedContent
+## CalculatedContent mappings
 
 The MedTech service provides an expression-based content template to both match the wanted template and extract values. **Expressions** may be used by either JSONPath or JMESPath. Each expression within the template may choose its own expression language. 
 
@@ -67,7 +67,7 @@ The default expression language to use for a MedTech service device mappings can
     }
 ```
 
-The CalculatedContentTemplate allows matching on and extracting values from an Azure Event Hubs message using **Expressions** as defined below:
+The CalculatedContent mappings allow matching on and extracting values from an Azure Event Hubs message using **Expressions** as defined below:
 
 |Property|Description|Example|
 |--------|-----------|-------|
@@ -92,13 +92,13 @@ When specifying the language to use for the expression, the below values are val
 | JMESPath            | **JmesPath** |
 
 >[!TIP]
-> For more information on JSONPath, see [JSONPath](https://goessner.net/articles/JsonPath/). [CalculatedContent](#calculatedcontent) uses the [JSON .NET implementation](https://www.newtonsoft.com/json/help/html/QueryJsonSelectTokenJsonPath.htm) for resolving JSONPath expressions.
+> For more information on JSONPath, see [JSONPath](https://goessner.net/articles/JsonPath/). CalculatedContent mappings use the [JSON .NET implementation](https://www.newtonsoft.com/json/help/html/QueryJsonSelectTokenJsonPath.htm) for resolving JSONPath expressions.
 >
-> For more information on JMESPath, see [JMESPath](https://jmespath.org/specification.html). [CalculatedContent](#calculatedcontent) uses the [JMESPath .NET implementation](https://github.com/jdevillard/JmesPath.Net) for resolving JMESPath expressions.
+> For more information on JMESPath, see [JMESPath](https://jmespath.org/specification.html). CalculatedContent mappings use the [JMESPath .NET implementation](https://github.com/jdevillard/JmesPath.Net) for resolving JMESPath expressions.
 
 ### Custom functions
 
-A set of MedTech service custom functions is also available. The MedTech service custom functions are outside of the functions provided as part of the JMESPath specification. For more information on the MedTech service custom functions, see [How to use MedTech service custom functions](how-to-use-custom-functions.md).
+A set of MedTech service custom functions are also available. The MedTech service custom functions are outside of the functions provided as part of the JMESPath specification. For more information on the MedTech service custom functions, see [How to use MedTech service custom functions](how-to-use-custom-functions.md).
 
 ### Matched Token
 
@@ -547,6 +547,6 @@ In this article, you learned how to configure the MedTech service device mapping
 To learn how to configure FHIR destination mappings, see
 
 > [!div class="nextstepaction"]
-> [How to configure the FHIR destination mappings](how-to-configure-fhir-mappings.md)
+> [How to configure FHIR destination mappings](how-to-configure-fhir-mappings.md)
 
 (FHIR®) is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.

articles/healthcare-apis/release-notes.md

@@ -543,7 +543,7 @@ Enabled DICOM service to work with workspaces that have names beginning with a l
 
 **MedTech service normalized improvements with calculations to support and enhance health data standardization.** 
 
-See [Use Device mappings](./../healthcare-apis/iot/how-to-use-device-mappings.md) and [Calculated Content Templates](./../healthcare-apis/iot/how-to-use-calculatedcontenttemplate-mappings.md)  
+See [Use device mappings](./../healthcare-apis/iot/how-to-use-device-mappings.md) and [CalculatedContent](./../healthcare-apis/iot/how-to-use-calculatedcontent-mappings.md)