From c87292d3d9560313194d3ac4c4690b5da40f5469 Mon Sep 17 00:00:00 2001 From: Mike Wasson Date: Mon, 9 Apr 2018 10:26:13 -0700 Subject: [PATCH] Fix typo Fixes #483 --- .../hybrid-networking/shared-services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference-architectures/hybrid-networking/shared-services.md b/docs/reference-architectures/hybrid-networking/shared-services.md index 1ded26e727f..373647ad922 100644 --- a/docs/reference-architectures/hybrid-networking/shared-services.md +++ b/docs/reference-architectures/hybrid-networking/shared-services.md @@ -75,7 +75,7 @@ As you move workloads from your on-premises environment to Azure, some of these You can use network virtual appliances (NVAs) in Azure to host different types of security and performance services. If you are familiar with a given set of appliances on-premises today, it is recommended to use the same virtualized appliances in Azure, where applicable. > [!NOTE] -> The deployment scripts for this reference architecture use an Ubuntu VM with IP forwarding enbaled to mimic a network virtual appliance. +> The deployment scripts for this reference architecture use an Ubuntu VM with IP forwarding enabled to mimic a network virtual appliance. ## Considerations