Merge pull request #274509 from dknappettmsft/patch-2

Update rdp-bandwidth.md

Author: prmerger-automator[bot]

articles/virtual-desktop/rdp-bandwidth.md

@@ -11,7 +11,7 @@ ms.author: femila
 
 Remote Desktop Protocol (RDP) is a sophisticated technology that uses various techniques to perfect the server's remote graphics' delivery to the client device. Depending on the use case, availability of computing resources, and network bandwidth, RDP dynamically adjusts various parameters to deliver the best user experience.
 
-Remote Desktop Protocol multiplexes multiple Dynamic Virtual Channels (DVCs) into a single data channel sent over different network transports. There are separate DVCs for remote graphics, input, device redirection, printing, and more. Azure Virtual Desktop partners can also use their extensions that use DVC interfaces.
+RDP multiplexes multiple Dynamic Virtual Channels (DVCs) into a single data channel sent over different network transports. There are separate DVCs for remote graphics, input, device redirection, printing, and more. Azure Virtual Desktop partners can also use their extensions that use DVC interfaces.
 
 The amount of the data sent over RDP depends on the user activity. For example, a user may work with basic textual content for most of the session and consume minimal bandwidth, but then generate a printout of a 200-page document to the local printer. This print job will use a significant amount of network bandwidth.
 
@@ -23,11 +23,11 @@ RDP uses various compression algorithms for different types of data. The table b
 
 | Type of Data | Direction | How to estimate |
 |---|---|---|
-| Remote Graphics | Session host to client | [See the detailed guidelines](#estimating-bandwidth-used-by-remote-graphics) |
-| Heartbeats | Both directions | ~ 20 bytes every 5 seconds  |
-| Input | Client to session Host | Amount of data is based on the user activity, less than 100 bytes for most of the operations  |
-| File transfers | Both directions | File transfers are using bulk compression. Use .zip compression for approximation |
-| Printing | Session host to client | Print job transfer depends on the driver and using bulk compression, use .zip compression for approximation |
+| Remote graphics | Session host to client | [See the detailed guidelines](#estimating-bandwidth-used-by-remote-graphics). |
+| Heartbeats | Bidirectional | ~ 20 bytes every 5 seconds. |
+| Input | Client to session host | Amount of data is based on the user activity, less than 100 bytes for most of the operations. |
+| File transfers | Bidirectional | File transfers are using bulk compression. Use `.zip` compression rates for an approximation. |
+| Printing | Session host to client | Print job transfer depends on the driver and using bulk compression, use `.zip` compression rates for an approximation. |
 
 Other scenarios can have their bandwidth requirements change depending on how you use them, such as:
 
@@ -41,10 +41,10 @@ It's tough to predict bandwidth use by the remote desktop. The user activities g
 
 The best way to understand bandwidth requirements is to monitor real user connections. Monitoring can be performed by the built-in performance counters or by the network equipment.
 
-However, in many cases, you may estimate network utilization by understanding how Remote Desktop Protocol works and by analyzing your users' work patterns.
+However, in many cases, you may estimate network utilization by understanding how RDP works and by analyzing your users' work patterns.
 
-The remote protocol delivers the graphics generated by the remote server to display it on a local monitor. More specifically, it provides the desktop bitmap entirely composed on the server.
-While sending a desktop bitmap seems like a simple task at first approach, it requires a significant amount of resources. For example, a 1080p desktop image in its uncompressed form is about 8Mb in size. Displaying this image on the locally connected monitor with a modest screen refresh rate of 30 Hz requires bandwidth of about 237 MB/s.
+RDP delivers the graphics generated by the remote server to display it on a local monitor. More specifically, it provides the desktop bitmap entirely composed on the server.
+While sending a desktop bitmap seems like a simple task at first approach, it requires a significant amount of resources. For example, a 1080p desktop image in its uncompressed form is about 8Mb in size. Displaying this image on the locally connected monitor with a modest screen refresh rate of 30Hz requires bandwidth of about 237 Mbps.
 
 To reduce the amount of data transferred over the network, RDP uses the combination of multiple techniques, including but not limited to