Merge pull request #216990 from KapilAnanth-MSFT/patch-9

(AzureCXP) fixed TCP Window size formula

Author: prmerger-automator[bot]

articles/virtual-network/virtual-network-tcpip-performance-tuning.md

@@ -184,11 +184,11 @@ But the TCP header value for TCP window size is only 2 bytes long, which means t
 
 The scale factor is also a setting that you can configure in an operating system. Here's the formula for calculating the TCP window size by using scale factors:
 
-`TCP window size = TCP window size in bytes \* (2^scale factor)`
+`TCP window size = TCP window size in bytes * (2^scale factor)`
 
 Here's the calculation for a window scale factor of 3 and a window size of 65,535:
 
-`65,535 \* (2^3) = 262,140 bytes`
+`65,535 * (2^3) = 262,140 bytes`
 
 A scale factor of 14 results in a TCP window size of 14 (the maximum offset allowed). The TCP window size will be 1,073,725,440 bytes (8.5 gigabits).
 
@@ -367,4 +367,4 @@ Still, these packet types are indications that TCP throughput isn't achieving it
 
 ## Next steps
 
-Now that you've learned about TCP/IP performance tuning for Azure VMs, you might want to read about other considerations for [planning virtual networks](./virtual-network-vnet-plan-design-arm.md) or [learn more about connecting and configuring virtual networks](./index.yml).
+Now that you've learned about TCP/IP performance tuning for Azure VMs, you might want to read about other considerations for [planning virtual networks](./virtual-network-vnet-plan-design-arm.md) or [learn more about connecting and configuring virtual networks](./index.yml).