From 845c2124bdf9fb1e3fe2f6bbeba841862ecfb790 Mon Sep 17 00:00:00 2001
From: Andy Helsby <21364480+Absoblogginlutely@users.noreply.github.com>
Date: Fri, 21 Apr 2023 11:37:39 -0400
Subject: [PATCH] Typo fixed

Oddly enough this message was displayed on an en-us windows 2022 server so fixed the typos
---
 Private/Get-XMLGPO.ps1 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Private/Get-XMLGPO.ps1 b/Private/Get-XMLGPO.ps1
index 0833b52..fed4815 100644
--- a/Private/Get-XMLGPO.ps1
+++ b/Private/Get-XMLGPO.ps1
@@ -133,7 +133,7 @@
         # in some cases GPResult seems to return an error - this was first noticed by user when using Dutch based system
         # I am not sure if it's possible to fix this error for users, but once that happens checking if GPO is empty fails using the method below
         # therefore we will use the old method of assuming something is empty or not empty in such case
-        Write-Warning "Get-XMLGPO - Reading GPO content [$DisplayName/$DomainName] returned an error. This may be because of non-english language. Assesing EMPTY using old method which can report false positives. Be careful please."
+        Write-Warning "Get-XMLGPO - Reading GPO content [$DisplayName/$DomainName] returned an error. This may be because of non-english language. Assessing EMPTY using old method which can report false positives. Be careful please."
         $OutputUser = @()
         $OutputComputer = @()
     } else {
@@ -223,7 +223,7 @@
         } elseif ($ADAdministrativeGroups) {
             $OwnerType = 'Unknown'
         } else {
-            $OwnerType = 'Unable to asses (local files?)'
+            $OwnerType = 'Unable to assess (local files?)'
         }
     }
     # Mark GPO as excluded
@@ -398,4 +398,4 @@
             }
         }
     }
-}
\ No newline at end of file
+}