diff --git a/Fido.ps1 b/Fido.ps1
index a2a68ba..13d9e0a 100644
--- a/Fido.ps1
+++ b/Fido.ps1
@@ -1,5 +1,5 @@
 #
-# Fido v1.07 - Retail Windows ISO Downloader
+# Fido v1.08 - Retail Windows ISO Downloader
 # Copyright © 2019 Pete Batard <pete@akeo.ie>
 # ConvertTo-ImageSource: Copyright © 2016 Chris Carter
 #
@@ -517,7 +517,6 @@ $Continue.add_click({
 			$array = @()
 			foreach ($Version in $WindowsVersions[$WindowsVersion.SelectedValue.Index]) {
 				if (($i -ne 0) -and ($Version -is [array])) {
-					Write-Host $Version[0]
 					$array += @(New-Object PsObject -Property @{ Release = $ltrm + $Version[0].Replace(")", ")" + $ltrm); Index = $i })
 				}
 				$i++
diff --git a/README.md b/README.md
index 4918164..c593b46 100644
--- a/README.md
+++ b/README.md
@@ -19,7 +19,7 @@ As to the reason one might want to download Windows __retail__ ISOs, as opposed
 Microsoft's own Media Creation Tool (MCT), this is because it is only with an official retail ISO that one can assert
 with complete certainty whether its content has been altered in any way or not. Indeed, retail Microsoft's ISOs are the
 only ones you will be able to obtain an official SHA-1 for (from sites [such as this one](https://msdn.rg-adguard.net/public.php))
-for instance) allowing you to be 100% certain that the image you are using is non corrupted and safe to use.
+allowing you to be 100% certain that the image you are using is non corrupted and safe to use.
 
 This, in turn, offers assurance that the content __YOU__ are using to install your OS, and which it is indeed critical
 to validate beforehand if you care about security, does matches bit for bit the one that Microsoft officially released.