Merge pull request #91600 from john-par/patch-6

Update hana-network-architecture.md

Author: PRMerger7

articles/virtual-machines/workloads/sap/hana-network-architecture.md

@@ -135,7 +135,14 @@ By default deployment, three network routing considerations are important for SA
 * SAP HANA on Azure (Large Instances) units have an assigned IP address from the server IP pool address range that you submitted when requesting the HANA Large Instance deployment. For more information, see [SAP HANA (Large Instances) infrastructure and connectivity on Azure](hana-overview-infrastructure-connectivity.md?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json). This IP address is accessible through the Azure subscriptions and circuit  that connects Azure virtual networks to HANA Large Instances. The IP address assigned out of that server IP pool address range is directly assigned to the hardware unit. It's *not* assigned through NAT anymore, as was the case in the first deployments of this solution. 
 
 ### Direct Routing to HANA Large Instances
-By default the transitive routing between HANA Large Instance units and on-premise or between HANA Large Instance routing that are deployed in two different regions does not work. There are several possibilities to enable such a transitive routing.
+
+By default, the transitive routing does not work in these scenarios:
+
+* Between HANA Large Instance units and an on-premises deployment.
+
+* Between HANA Large Instance routing that are deployed in two different regions.
+
+There are three ways to enable transitive routing in those scenarios:
 
 - A reverse-proxy to route data, to and from. For example, F5 BIG-IP, NGINX with Traffic Manager deployed in the Azure virtual network that connects to HANA Large Instances and to on-premise as a virtual firewall/traffic routing solution.
 - Using [IPTables rules](http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_%3a_Ch14_%3a_Linux_Firewalls_Using_iptables#.Wkv6tI3rtaQ) in a Linux VM to enable routing between on-premises locations and HANA Large Instance units, or between HANA Large Instance units in different regions. The VM running IPTables needs to be deployed in the Azure virtual network that connects to HANA Large Instances and to on-premise. The VM needs to be sized accordingly, so, that the network throughput of the VM is sufficient for the expected network traffic. For details on VM network bandwidth, check the article [Sizes of Linux virtual machines in Azure](https://docs.microsoft.com/azure/virtual-machines/linux/sizes?toc=%2fazure%2fvirtual-network%2ftoc.json).
@@ -190,4 +197,4 @@ The figure shows how the different virtual networks in both regions are connecte
 > If you used multiple ExpressRoute circuits, AS Path prepending and Local Preference BGP settings should be used to ensure proper routing of traffic.
 
 **Next steps**
-- Refer [SAP HANA (Large Instances) storage architecture](hana-storage-architecture.md)
+- Refer [SAP HANA (Large Instances) storage architecture](hana-storage-architecture.md)