summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLyssa2023-10-26 19:35:59 +0000
committerGitHub2023-10-26 19:35:59 +0000
commit2264d72d3b0caa881a631eca3b3e71bcecfcadcb (patch)
tree67e54d594724a7daf9321f08dfcf1efe75b442ad
parentf3fa2a7e1cb8fe93c539f7a07b9e4c0f30356231 (diff)
downloadmassgrave.dev-2264d72d3b0caa881a631eca3b3e71bcecfcadcb.zip
minor fix
-rw-r--r--office-license-is-not-genuine.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/office-license-is-not-genuine.md b/office-license-is-not-genuine.md
index 83ff9e9..624c9c8 100644
--- a/office-license-is-not-genuine.md
+++ b/office-license-is-not-genuine.md
@@ -14,7 +14,7 @@ pagetitle: Get genuine Office banner
- Office Click-to-Run builds (since February 2021) that are activated with KMS check the existence of a KMS server name in the registry. If the KMS server is not present, a banner is shown in Office programs notifying that "Office isn't licensed properly"
-- If 32-bit Office installed on 64-bit Windows, Office checks the KMS server existence in the corresponding WOW6432Node registry key as well.
+- If 32-bit Office is installed on 64-bit Windows, Office checks the KMS server existence in the corresponding WOW6432Node registry key as well.
- Apart from this, they also detect if a registered KMS server is on their blacklist or not. As far as I know, the below 3 addresses are blacklisted.