From e5ab74c2d9c6aa641d60df0769f42f54e3e8ea13 Mon Sep 17 00:00:00 2001
From: awuctl <61098069+awuctl@users.noreply.github.com>
Date: Fri, 21 Jan 2022 09:19:31 +0100
Subject: [PATCH] Fix NSLP description

Made an oopsie - NSLP is definitely not "an SLP equivalent" as the activation is not authorized by the OEM.
---
 README.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 6c1b1f8..17f1fda 100644
--- a/README.md
+++ b/README.md
@@ -69,10 +69,9 @@ There are multiple types of keys that will accompany OEM licenses. Those are:
 The differences between them are pretty extreme but ultimately do not matter
 that much. In short, **SLP** keys do not require Microsoft's activation servers
 to activate - the OEM marks a machine as activated during manufacturing,
-**DM** are the "BIOS keys" you might have seen/heard about and **NSLP**s are the
-**SLP** equivalent for when the OEM doesn't want to bother with activation
-during manufacturing. In terms more people might understand, NSLP is analogous
-to COA.
+**DM** are the "BIOS keys" you might have seen/heard about and **NSLP**s are for
+when the OEM doesn't want to bother with activation during manufacturing. In
+terms more people might understand, NSLP is analogous to COA.
 
 ### Volume Licensing
 Microsoft's bigger customers that "need" more licenses for more computer can opt