Update content.md

Author: leefine02

docsource/content.md

@@ -103,7 +103,7 @@ more information on defining and configuring certificate stores.
 1. When orchestrating management of external (and potentially local) certificate stores, the `RemoteFile` Orchestrator 
 Extension makes use of `WinRM` to connect to external certificate store servers.  The security context used is the user id 
 entered in the Keyfactor Command certificate store or discovery job screen.  Make sure that `WinRM` is set up on the 
-orchestrated server and that the `WinRM` port (by convention, `5585` for `HTTP` and `5586` for `HTTPS`) is part of the certificate 
+orchestrated server and that the `WinRM` port (by convention, `5985` for `HTTP` and `5986` for `HTTPS`) is part of the certificate 
 store path when setting up your certificate stores/discovery jobs. If running as an agent, managing local certificate stores, 
 local commands are run under the security context of the user account running the Keyfactor Universal Orchestrator Service.  
 Please reference [Certificate Stores and Discovery Jobs](#certificate-stores-and-discovery-jobs) for more information on 
@@ -312,4 +312,4 @@ Steps to create a new supported file-based certificate store type:
    short name in Keyfactor Command. On the `TypeFullName` line for all three sections, make sure the namespace matches
    what you used for your new classes. Note that the namespace for Discovery uses a common class for all supported
    types. Discovery is a common implementation for all supported store types.
-8. Modify the integration-manifest.json file to add the new store type under the store_types element.
+8. Modify the integration-manifest.json file to add the new store type under the store_types element.