Merge branch 'master' of https://github.com/austinmccollum/azure-docs-pr into insights-mod-austinmc

Author: austinmccollum

articles/container-registry/anonymous-pull-access.md

@@ -10,7 +10,7 @@ ms.custom: ""
 
 Setting up an Azure container registry for anonymous (unauthenticated) pull access is an optional feature that allows any user with internet access the ability to pull any content from the registry.
 
-Anonymous pull access is a preview feature, available in the Standard and Premium [service tiers](container-registry-skus.md). To configure anonymous pull access, update a registry using the Azure CLI (version 2.21.0 or later). To install or upgrade, see [Install Azure CLI](/cli/azure-install-cli).
+Anonymous pull access is a preview feature, available in the Standard and Premium [service tiers](container-registry-skus.md). To configure anonymous pull access, update a registry using the Azure CLI (version 2.21.0 or later). To install or upgrade, see [Install Azure CLI](/cli/azure/install-azure-cli).
 
 ## About anonymous pull access
 

articles/frontdoor/front-door-faq.yml

@@ -105,7 +105,7 @@ sections:
           
           - Configure IP ACLing for your backends to accept traffic from Azure Front Door's backend IP address space and Azure's infrastructure services only. Refer the IP details below for ACLing your backend:
            
-              - Refer *AzureFrontDoor.Backend* section in [Azure IP Ranges and Service Tags](https://www.microsoft.com/download/details.aspx?id=56519) for Front Door's IPv4 backend IP address range or you can also use the service tag *AzureFrontDoor.Backend* in your [network security groups](../virtual-network/network-security-groups-overview.md#security-rules).
+              - Refer *AzureFrontDoor.Backend* section in [Azure IP Ranges and Service Tags](https://www.microsoft.com/download/details.aspx?id=56519) for Front Door's backend IP address range or you can also use the service tag *AzureFrontDoor.Backend* in your [network security groups](../virtual-network/network-security-groups-overview.md#security-rules).
               - Azure's [basic infrastructure services](../virtual-network/network-security-groups-overview.md#azure-platform-considerations) through virtualized host IP addresses: `168.63.129.16` and `169.254.169.254`
           
               > [!WARNING]

articles/frontdoor/standard-premium/faq.md

@@ -91,7 +91,7 @@ Alternative way to lock down your application to accept traffic only from your s
 
 * Configure IP ACLing for your backends to accept traffic from Azure Front Door's backend IP address space and Azure's infrastructure services only. Refer to the IP details below for ACLing your backend:
 
-    * Refer *AzureFrontDoor.Backend* section in [Azure IP Ranges and Service Tags](https://www.microsoft.com/download/details.aspx?id=56519) for Front Door's IPv4 backend IP address range. You can also use the service tag *AzureFrontDoor.Backend* in your [network security groups](../../virtual-network/network-security-groups-overview.md#security-rules).
+    * Refer *AzureFrontDoor.Backend* section in [Azure IP Ranges and Service Tags](https://www.microsoft.com/download/details.aspx?id=56519) for Front Door's backend IP address range. You can also use the service tag *AzureFrontDoor.Backend* in your [network security groups](../../virtual-network/network-security-groups-overview.md#security-rules).
     * Azure's [basic infrastructure services](../../virtual-network/network-security-groups-overview.md#azure-platform-considerations) through virtualized host IP addresses: `168.63.129.16` and `169.254.169.254`.
 
     > [!WARNING]

articles/healthcare-apis/github-projects.md

@@ -5,7 +5,7 @@ services: healthcare-apis
 author: ginalee-dotcom
 ms.service: healthcare-apis
 ms.topic: reference
-ms.date: 10/13/2021
+ms.date: 10/18/2021
 ms.author: ginle
 ---
 # GitHub Projects
@@ -14,7 +14,7 @@ We have many open-source projects on GitHub that provide you the source code and
 
 ## Healthcare APIs samples
 
-* This repo contains [samples for Healthcare APIs](https://github.com/microsoft/healthcare-apis-samples), including FHIR, DICOM, IoT connector, and data-related services.
+* This repo contains [samples for Healthcare APIs](https://github.com/microsoft/healthcare-apis-samples), including Fast Healthcare Interoperability Resources (FHIR®), DICOM, IoT connector, and data-related services.
 
 ## FHIR Server
 
@@ -41,14 +41,14 @@ We have many open-source projects on GitHub that provide you the source code and
 * Released to Visual Studio Marketplace
 * Used for authoring Liquid templates to be used in the FHIR Converter
 
-## IoT Connector
+## IoT connector
 
 #### Integration with IoT Hub and IoT Central
 
 * [microsoft/iomt-fhir](https://github.com/microsoft/iomt-fhir): integration with IoT Hub or IoT Central to FHIR with data normalization and FHIR conversion of the normalized data
 * Normalization: device data information is extracted into a common format for further processing
 * FHIR Conversion: normalized and grouped data is mapped to FHIR. Observations are created or updated according to configured templates and linked to the device and patient.
-* [Tools to help build the conversation map](https://github.com/microsoft/iomt-fhir/tree/master/tools/data-mapper): visualize the mapping configuration for normalizing the device input data and transform it to the FHIR resources. Developers can use this tool to edit and test the mappings, device mapping and FHIR mapping, and export them for uploading to the IoT Connector in the Azure portal.
+* [Tools to help build the conversation map](https://github.com/microsoft/iomt-fhir/tree/master/tools/data-mapper): visualize the mapping configuration for normalizing the device input data and transform it to the FHIR resources. Developers can use this tool to edit and test the Device and FHIR destination mappings and export them for uploading to the IoT connector in the Azure portal.
 
 #### HealthKit and FHIR Integration