Skip to content

Commit 0422017

Browse files
tweak
1 parent 768a914 commit 0422017

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/virtual-network/nat-gateway-resource.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.devlang: na
1313
ms.topic: overview
1414
ms.tgt_pltfrm: na
1515
ms.workload: infrastructure-services
16-
ms.date: 03/30/2020
16+
ms.date: 03/31/2020
1717
ms.author: allensu
1818
---
1919

@@ -177,7 +177,7 @@ NAT gateways take precedence over outbound scenarios of the subnet. Basic load b
177177
#### Zone isolation with zonal stacks
178178

179179
<p align="center">
180-
<img src="media/nat-overview/az-directions.svg" width="425" title="Virtual Network NAT with availability zones">
180+
<img src="media/nat-overview/az-directions.svg" width="425" title="Virtual Network NAT with zone isolation, creating multiple "zonal stacks"">
181181
</p>
182182

183183
*Figure: Virtual Network NAT with zone isolation, creating multiple "zonal stacks"*
@@ -203,7 +203,7 @@ If your scenario requires inbound endpoints, you have two options:
203203
#### Cross-zone outbound scenarios not supported
204204

205205
<p align="center">
206-
<img src="media/nat-overview/az-directions2.svg" width="425" title="zone-spanning Virtual Network NAT">
206+
<img src="media/nat-overview/az-directions2.svg" width="425" title="Virtual Network NAT not compatible with zone-spanning subnet">
207207
</p>
208208

209209
*Figure: Virtual Network NAT not compatible with zone-spanning subnet*

0 commit comments

Comments
 (0)