Update events-not-forwarded-by-windows-server-collector.md

There was a missing letter 's' in protocol list. Probably a copying typo

Author: bad-samaritan

support/windows-server/admin-development/events-not-forwarded-by-windows-server-collector.md

@@ -37,7 +37,7 @@ The forwarder is having a problem communicating with subscription manager at add
 This behavior is caused by the permissions that are configured for the following URLs:
 
 - `http://+:5985/wsman/`
-- `http://+:5986/wsman/`
+- `https://+:5986/wsman/`
 
 On the event collector computer, both the Windows Event Collector service (WecSvc) and the Windows Remote Management service (WinRM) use these URLs. However, the default access control lists (ACLs) for these URLs allow access for only the svchost process that runs WinRM.
 In the default configuration of Windows Server 2016, a single svchost process runs both WinRM and WecSvc. Because the process has access, both services function correctly. However, if you change the configuration so that the services run on separate host processes, WecSvc no longer has access and event forwarding no longer functions.