Merge pull request #114930 from FlorianBorn71/NetworkRequirementsFix

Make network requirements consistent

Author: PRMerger17

articles/remote-rendering/reference/network-requirements.md

@@ -15,7 +15,7 @@ A stable, low-latency network connection to an Azure data center is critical for
 
 The exact network requirements depend on your specific use case, such as the number and frequency of modifications to the remote scene graph as well as the complexity of the rendered view, but there are a number of guidelines to ensure that your experience is as good as possible:
 
-* Your internet connectivity needs to support at least **50 Mbps downstream** and **10 Mbps upstream** consistently for a single user session of Azure Remote Rendering, assuming there is no competing traffic on the network. We recommend higher rates for better experiences. With more users on the same network, these requirements scale up correspondingly.
+* Your internet connectivity needs to support at least **40 Mbps downstream** and **5 Mbps upstream** consistently for a single user session of Azure Remote Rendering, assuming there is no competing traffic on the network. We recommend higher rates for better experiences. With more users on the same network, these requirements scale up correspondingly.
 * Using the **5-GHz Wi-Fi band** will usually produce better results than the 2.4-GHz Wi-Fi band, though both should work.
 * If there are other Wi-Fi networks nearby, avoid using Wi-Fi channels in use by these other networks. You can use network scanning tools like [WifiInfoView](https://www.nirsoft.net/utils/wifi_information_view.html) to verify whether the channels your Wi-Fi network uses, are free of competing traffic.
 * Strictly **avoid using Wi-Fi repeaters** or LAN-over-powerline forwarding.