From a1e8f0b0d9f787163a4dffa652a2d805b0f1696a Mon Sep 17 00:00:00 2001
From: Kristoff Tan <48010214+kristofftan@users.noreply.github.com>
Date: Wed, 12 Apr 2023 17:17:48 +0800
Subject: [PATCH] Update encryption-office-365-tls-certificates-changes.md

Maybe 2023???
---
 .../encryption-office-365-tls-certificates-changes.md        | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/microsoft-365/compliance/encryption-office-365-tls-certificates-changes.md b/microsoft-365/compliance/encryption-office-365-tls-certificates-changes.md
index 8b8957fcc1e..7c52aa7a265 100644
--- a/microsoft-365/compliance/encryption-office-365-tls-certificates-changes.md
+++ b/microsoft-365/compliance/encryption-office-365-tls-certificates-changes.md
@@ -49,7 +49,7 @@ All certificate information in this article was previously provided in [Microsof
 
 ## When will this change happen?
 
-Services began transitioning to the new Root CAs in January 2022 and will continue through October 2022.
+Services began transitioning to the new Root CAs in January 2022 and will continue through October 2023.
 
 ## What is changing?
 
@@ -157,7 +157,8 @@ Administrators can identify and troubleshoot the issue by inspecting the CAPI2 L
 ```text
 Log Name:      Microsoft-Windows-CAPI2/Operational
 Source:        Microsoft-Windows-CAPI2
-Date:          6/23/2022 8:36:39 AM
+Date:          6/23/
+8:36:39 AM
 Event ID:      11
 Task Category: Build Chain
 Level:         Error