Skip to content

Commit 31ef26b

Browse files
authored
Fix typos and improve grammar in tutorial
1 parent d17f189 commit 31ef26b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/nat-gateway/tutorial-hub-spoke-route-nat.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ A hub and spoke network is one of the building blocks of a highly available mult
1717
For outbound traffic to the internet, the network virtual appliance would typically have one network interface with an assigned public IP address. The NVA after inspecting the outbound traffic forwards the traffic out the public interface and to the internet. Azure NAT Gateway eliminates the need for the public IP address assigned to the NVA. Associating a NAT gateway with the public subnet of the NVA changes the routing for the public interface to route all outbound internet traffic through the NAT gateway. The elimination of the public IP address increases security and allows for the scaling of outbound source network address translation (SNAT) with multiple public IP addresses and or public IP prefixes.
1818

1919
> [!IMPORTANT]
20-
> The NVA used in this article is for demonstration purposes only and is simulated with an Ubuntu virtual machine. The solution doesn't include a load balancer for high availability of the NVA deployment. Replace the Ubuntu virtual machine in this article with an NVA of your choice. Consult the vendor of the chosen NVA for routing and configuration instructions. A load balancer and availability zones is recommended for a highly available NVA infrastructure.
20+
> The NVA used in this article is for demonstration purposes only and is simulated with an Ubuntu virtual machine. The solution doesn't include a load balancer for high availability of the NVA deployment. Replace the Ubuntu virtual machine in this article with an NVA of your choice. Consult the vendor of the chosen NVA for routing and configuration instructions. A load balancer and availability zones are recommended for a highly available NVA infrastructure.
2121
2222
In this tutorial, you learn how to:
2323

@@ -1475,7 +1475,7 @@ $vmConfigParams = @{
14751475
$vmConfig = New-AzVMConfig @vmConfigParams
14761476
```
14771477
1478-
Use [Set-AzVMOperatingSystem](/powershell/module/az.compute/set-azvmoperatingsystem) and [Set-AzVMSourceImage](/powershell/module/az.compute/set-azvmsourceimage) to create the rest of the VM configuration. The following example creates an Windows Server virtual machine:
1478+
Use [Set-AzVMOperatingSystem](/powershell/module/az.compute/set-azvmoperatingsystem) and [Set-AzVMSourceImage](/powershell/module/az.compute/set-azvmsourceimage) to create the rest of the VM configuration. The following example creates a Windows Server virtual machine:
14791479
14801480
```azurepowershell
14811481
$osParams = @{
@@ -2126,7 +2126,7 @@ $vmConfigParams = @{
21262126
$vmConfig = New-AzVMConfig @vmConfigParams
21272127
```
21282128
2129-
Use [Set-AzVMOperatingSystem](/powershell/module/az.compute/set-azvmoperatingsystem) and [Set-AzVMSourceImage](/powershell/module/az.compute/set-azvmsourceimage) to create the rest of the VM configuration. The following example creates an Windows Server virtual machine:
2129+
Use [Set-AzVMOperatingSystem](/powershell/module/az.compute/set-azvmoperatingsystem) and [Set-AzVMSourceImage](/powershell/module/az.compute/set-azvmsourceimage) to create the rest of the VM configuration. The following example creates a Windows Server virtual machine:
21302130
21312131
```azurepowershell
21322132
$osParams = @{

0 commit comments

Comments
 (0)