[gimp-web/testing] Fixed spelling typo

[Pat David <patdavid src gnome org>]

commit c2da646edd8d8834e6972996553f0ba1724b2cf6
Author: Pat David <patdavid gmail com>
Date:   Wed Mar 23 13:18:55 2016 -0500

    Fixed spelling typo

 ...016-03-17 Corrupt Windows Installer Warnings.md |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/content/news/2016-03-17 Corrupt Windows Installer Warnings.md b/content/news/2016-03-17 Corrupt 
Windows Installer Warnings.md
index b9b25b5..7ca14c1 100644
--- a/content/news/2016-03-17 Corrupt Windows Installer Warnings.md     
+++ b/content/news/2016-03-17 Corrupt Windows Installer Warnings.md     
@@ -7,7 +7,7 @@ Summary: The Windows installer packages for GIMP 2.8.16 are reported as corrupt
 
 For the past few weeks, we have been receiving reports that some users can't download our [installer 
packages](//www.gimp.org/downloads/) for the Microsoft Windows platforms. Microsoft Edge and Internet 
Explorer 11 [mark them as 
corrupt](//social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-authenticode-code-signing-and-timestamping.aspx#Signature_Verification_Failure_Experience)
 and discourage users from running them.
 
-Turns out this is a policy change by Mircosoft, gone into effect on January 1, 2016. The new policy affects 
all kinds of security certificates as of specific deadlines, and this includes code signing certificates. 
Jernej Simončič, who creates the Windows installer packages, signs them to make their authenticity 
verifiable. But the way this signature is done is no longer considered safe by Microsoft, and there are 
justified technical reasons for that.
+Turns out this is a policy change by Microsoft, gone into effect on January 1, 2016. The new policy affects 
all kinds of security certificates as of specific deadlines, and this includes code signing certificates. 
Jernej Simončič, who creates the Windows installer packages, signs them to make their authenticity 
verifiable. But the way this signature is done is no longer considered safe by Microsoft, and there are 
justified technical reasons for that.
 
 Administrators and users of Microsoft Windows systems are well advised to make themselves familiar with the 
implications of this policy; the TechNet article on the subject is available at [Windows Enforcement of 
Authenticode Code Signing and 
Timestamping](//social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-authenticode-code-signing-and-timestamping.aspx).