From 99f07f61e33c42f399281f41c75840dced8fa53a Mon Sep 17 00:00:00 2001 From: Przemyslaw Klys Date: Sun, 24 Jan 2021 10:28:29 +0100 Subject: [PATCH] Text improvement --- Private/Invoke.GPOZaurrBrokenLink.ps1 | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Private/Invoke.GPOZaurrBrokenLink.ps1 b/Private/Invoke.GPOZaurrBrokenLink.ps1 index c86e4d5..3d717e2 100644 --- a/Private/Invoke.GPOZaurrBrokenLink.ps1 +++ b/Private/Invoke.GPOZaurrBrokenLink.ps1 @@ -39,11 +39,11 @@ $GPOZaurrBrokenLink = [ordered] @{ } Summary = { New-HTMLText -FontSize 10pt -TextBlock { - "When GPO is deleted in a proper way it usually is removed from AD, SYSVOL and any link to it is also discarded. " - "Unfortunetly this is true only if the GPO is created and linked within same domain. " - "If GPO is linked in another domain, this leaves a broken link hanging on wherever it was linked before. " - "Additionally Remove-GPO cmdlet doesn't handle site link deletions, which causes dead links to be stuck on sites until those are manually deleted. " - "This means that any GPOs deleted using PowerShell may leave trail. " + "When GPO is deleted correctly, it usually is removed from AD, SYSVOL, and any link to it is also discarded. " + "Unfortunately, this is true only if the GPO is created and linked within the same domain. " + "If GPO is linked in another domain, this leaves a broken link hanging on before it was linked. " + "Additionally, the Remove-GPO cmdlet doesn't handle site link deletions, which causes dead links to be stuck on sites until those are manually deleted. " + "This means that any GPOs deleted using PowerShell may leave a trail." } New-HTMLText -Text @( 'As it stands currently there are ',