AU: 1 updated - nssm

[skip ci] https://gist.github.com/a14b1e5bfaf70839b338eb1ab7f8226f/5e5c29d75bd74e135ecdf8ae0fe16475f8685919

automatic/nssm/nssm.nuspec

@@ -2,15 +2,15 @@
 <package xmlns="http://schemas.microsoft.com/packaging/2011/08/nuspec.xsd">
   <metadata>
     <id>nssm</id>
-    <version>2.24.101-g897c7ad</version>
+    <version>2.24.101</version>
     <title>NSSM - the Non-Sucking Service Manager</title>
     <authors>Iain Patterson</authors>
     <owners>chocolatey, dtgm</owners>
     <licenseUrl>https://git.nssm.cc/?p=nssm.git;a=blob;f=README.txt;h=12db7e88a4cd83edb7023b2b92e7d3d5eabf1175;hb=HEAD#l882</licenseUrl>
     <projectUrl>http://nssm.cc/</projectUrl>
     <iconUrl>https://cdn.rawgit.com/chocolatey/chocolatey-coreteampackages/e5fb8d88f655ec82c1b56702686d9627cfc3ac2e/icons/nssm.png</iconUrl>
     <requireLicenseAcceptance>false</requireLicenseAcceptance>
-    <description>nssm is a service helper which doesn't suck. srvany and other service helper programs suck because they don't handle failure of the application running as a service. If you use such a program you may see a service listed as started when in fact the application has died. nssm monitors the running service and will restart it if it dies. With nssm you know that if a service says it's running, it really is. Alternatively, if your application is well-behaved you can configure nssm to absolve all responsibility for restarting it and let Windows take care of recovery actions.
+    <description><![CDATA[nssm is a service helper which doesn't suck. srvany and other service helper programs suck because they don't handle failure of the application running as a service. If you use such a program you may see a service listed as started when in fact the application has died. nssm monitors the running service and will restart it if it dies. With nssm you know that if a service says it's running, it really is. Alternatively, if your application is well-behaved you can configure nssm to absolve all responsibility for restarting it and let Windows take care of recovery actions.
 
 nssm logs its progress to the system Event Log so you can get some idea of why an application isn't behaving as it should.
 
@@ -24,7 +24,8 @@ nssm logs its progress to the system Event Log so you can get some idea of why a
 * UAC aware
 * Unicode support
 * Works under Windows 2000 or later. Specifically, Windows 7, Windows 8 and Windows 10 are supported, x32 and x64 bit versions.
-</description>
+
+]]></description>
     <summary>Service helper program similar to srvany and cygrunsrv</summary>
     <releaseNotes>http://nssm.cc/changelog</releaseNotes>
     <copyright>© Iain Patterson</copyright>