Skip to content

Commit e31b3c6

Browse files
committed
acro fix
1 parent 3355657 commit e31b3c6

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

windows-365/enterprise/report-cloud-pc-connection-quality.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -36,9 +36,9 @@ The **Cloud PC connection quality** report helps you evaluate your users' connec
3636

3737
To get to the **Cloud PC connection quality** report, sign in to [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** > **Cloud PC performance** > **View report** (under **Cloud PCs with connection quality issues**).
3838

39-
![Screenshot of getting to the Cloud PC connection quality report](./media/report-cloud-pc-utilization/view-report-connection-quality.png)
39+
![Screenshot of getting to the Cloud PC connection quality report](./media/report-cloud-connection-quality/view-report-connection-quality.png)
4040

41-
This histogram shows aggregated round-trip times of all the Cloud PCs in your tenant. The round-trip time is how many milliseconds it took to connect tto the Cloud PC.
41+
This histogram shows aggregated round-trip times of all the Cloud PCs in your tenant. The round-trip time is how many milliseconds it took to connect to the Cloud PC.
4242

4343
- **Good**: Less than 100 milliseconds.
4444
- **Average**: 100-200 milliseconds.
@@ -50,7 +50,7 @@ Below that is a list of individual Cloud PCs with the following columns:
5050
- **Available bandwidth (P50)**: Internet bandwidth during the user's attempt to connect to their Cloud PC.
5151
- **Remoting sign-in time (P50)**: The number of seconds it took the user to complete the sign-in process.
5252

53-
Each metric is aggregated to a P50 median level over the last 24 hours.This is to ensure spikes and troughs are smoothed in order to provide a good understanding of the overall end-user connectivity experience.
53+
Each metric is aggregated to a P50 median level over the last 24 hours. This is to ensure spikes and troughs are smoothed in order to provide a good understanding of the overall end-user connectivity experience.
5454

5555
You can use **Add filter** to limit the histogram and table data to specific time spans and round-trip time ranges.
5656

0 commit comments

Comments
 (0)