diff --git a/README.md b/README.md
index 0756311..f88a8d7 100644
--- a/README.md
+++ b/README.md
@@ -84,15 +84,14 @@ The Entrust ECS   Gateway AnyCA Gateway REST plugin is supported by Keyfactor fo
 
         * **AuthUsername** - Username for the gateway to authenticate with Entrust 
         * **AuthPassword** - Password for the account used to authenticate with Entrust 
-        * **ClientCertificate** - The client certificate information used to authenticate with Entrust, only if configured to use certificate authentication 
+        * **ClientCertificate** - The client certificate information used to authenticate with Entrust (if configured to use certificate authentication). This can be either a Windows cert store location and thumbprint, or a PFX file and password. 
         * **Name** - The default requester name 
         * **Email** - The default requester email address 
         * **PhoneNumber** - The default requester phone number 
         * **IgnoreExpired** - If set to true, will not sync expired certs from Entrust 
         * **Enabled** - Flag to Enable or Disable gateway functionality. Disabling is primarily used to allow creation of the CA prior to configuration information being available. 
 
-2. Define [Certificate Profiles](https://software.keyfactor.com/Guides/AnyCAGatewayREST/Content/AnyCAGatewayREST/AddCP-Gateway.htm) and [Certificate Templates](https://software.keyfactor.com/Guides/AnyCAGatewayREST/Content/AnyCAGatewayREST/AddCA-Gateway.htm) for the Certificate Authority as required. One Certificate Profile must be defined per Certificate Template. It's recommended that each Certificate Profile be named after the Product ID. The Entrust ECS   Gateway plugin supports the following product IDs:
-
+2. TODO Certificate Template Creation Step is a required section
 
 3. Follow the [official Keyfactor documentation](https://software.keyfactor.com/Guides/AnyCAGatewayREST/Content/AnyCAGatewayREST/AddCA-Keyfactor.htm) to add each defined Certificate Authority to Keyfactor Command and import the newly defined Certificate Templates.
 
@@ -105,8 +104,6 @@ The Entrust ECS   Gateway AnyCA Gateway REST plugin is supported by Keyfactor fo
 
 
 
-
-
 ## License
 
 Apache License 2.0, see [LICENSE](LICENSE).
diff --git a/docsource/configuration.md b/docsource/configuration.md
index a5bd7a2..7f99e1c 100644
--- a/docsource/configuration.md
+++ b/docsource/configuration.md
@@ -10,3 +10,8 @@ The Entrust ECS AnyCA Gateway REST plugin extends the capabilities of Entrust Ce
 ## Gateway Registration
 
 In order to enroll for certificates the Keyfactor Command server must trust the trust chain. Once you know your Root and/or Subordinate CA in your Entrust account, make sure to download and import the certificate chain into the Command Server certificate store
+
+## Certificate Template Creation Step
+
+TODO Certificate Template Creation Step is a required section
+
diff --git a/integration-manifest.json b/integration-manifest.json
index d57f00a..00f2e4c 100644
--- a/integration-manifest.json
+++ b/integration-manifest.json
@@ -23,7 +23,7 @@
                 },
                 {
                     "name": "ClientCertificate",
-                    "description": "The client certificate information used to authenticate with Entrust, only if configured to use certificate authentication"
+                    "description": "The client certificate information used to authenticate with Entrust (if configured to use certificate authentication). This can be either a Windows cert store location and thumbprint, or a PFX file and password."
                 },
                 {
                     "name": "Name",