From 4af1c79d02706c2d573528a8aee57d0b2c9c0bdd Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Mon, 15 Apr 2024 11:11:38 -0700 Subject: [PATCH] Typo --- .../operate/windows-autopatch-reliability-report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md index 660527685b..e3a3f4b0c5 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md @@ -46,7 +46,7 @@ The Reliability report relies on device policies being configured properly. It's | No | - | - | No report available.

In this state, a ribbon appears on the landing page alerting the user that the diagnostic data needed to generate a report appears to be turned off. The report is available 24 and 48 hours after the following conditions are met:

| | Yes | 0 | - | The report includes only the historical comparison baseline and service-level score. The tenant and module impact scores are unavailable until 100 devices are updated. | | Yes | 0 < n < 100 | 0 < n < 100 | The report includes module failure details, historical comparison baseline, and service-level score. The tenant score is unavailable until 100 devices are updated. | -| Yes | n >= 100 | n >= 100 | The report includes module failure details, historical comparison baseline score, and service-level score. The tenant and module impact scores are unavailable until 100 devices are updated. | +| Yes | n >= 100 | 0 < n < 100 | The report includes module failure details, historical comparison baseline score, and service-level score. The tenant and module impact scores are unavailable until 100 devices are updated. | | Yes | n >= 100 | n >= 100 | Full reporting available | ## View the Reliability report