diff --git a/configuration/encryption-and-signing-credentials.html b/configuration/encryption-and-signing-credentials.html
index 1e534a9..207bf55 100644
--- a/configuration/encryption-and-signing-credentials.html
+++ b/configuration/encryption-and-signing-credentials.html
@@ -135,8 +135,8 @@ Unlike ephemeral keys, development certificates are persisted - but not shared a
 </code></pre><div class="WARNING"><h5>Warning</h5><p>This feature is not available on .NET Framework 4.6.1: calling <code>options.AddDevelopmentEncryptionCertificate()</code> or <code>options.AddDevelopmentSigningCertificate()</code>
 will result in a <code>PlatformNotSupportedException</code> being thrown at runtime if no valid development certificate can be found and a new one must be generated.</p>
 </div>
-<div class="CAUTION"><h5>Caution</h5><p><code>options.AddDevelopmentEncryptionCertificate()</code> or <code>options.AddDevelopmentSigningCertificate()</code> cannot be used in applications deployed on IIS or Azure App Services:
-trying to use them on IIS or Azure App Services will result in an exception being thrown at runtime (unless the application pool is configured to load a user profile).
+<div class="CAUTION"><h5>Caution</h5><p><code>options.AddDevelopmentEncryptionCertificate()</code> or <code>options.AddDevelopmentSigningCertificate()</code> cannot be used in applications deployed on IIS or Azure App Service:
+trying to use them on IIS or Azure App Service will result in an exception being thrown at runtime (unless the application pool is configured to load a user profile).
 To avoid that, consider creating self-signed certificates and storing them in the X.509 certificates store of the host machine(s).</p>
 </div>
 <h3 id="registering-a-key">Registering a key</h3>
@@ -179,7 +179,7 @@ File.WriteAllBytes(&quot;signing-certificate.pfx&quot;, certificate.Export(X509C
 </code></pre><p>The best place to store your certificates will depend on your host:</p>
 <ul>
 <li>For IIS applications, <a href="https://www.sonicwall.com/support/knowledge-base/how-can-i-import-certificates-into-the-ms-windows-local-machine-certificate-store/170504615105398/">storing the certificates in the machine store</a> is the recommended option.</li>
-<li>On Azure, certificates can be uploaded and exposed to Azure App Services applications using the special <code>WEBSITE_LOAD_CERTIFICATES</code> flag.
+<li>On Azure, certificates can be uploaded and exposed to Azure App Service applications using the special <code>WEBSITE_LOAD_CERTIFICATES</code> flag.
 For more information, visit <a href="https://docs.microsoft.com/en-us/azure/app-service/configure-ssl-certificate-in-code">Use a TLS/SSL certificate in your code in Azure App Service</a>.</li>
 </ul>
 <h2 id="importing-credentials-in-the-apiresource-validation-options">Importing credentials in the API/resource validation options</h2>
diff --git a/manifest.json b/manifest.json
index 2abb70f..8b1c2a4 100644
--- a/manifest.json
+++ b/manifest.json
@@ -45,7 +45,7 @@
       "output": {
         ".html": {
           "relative_path": "configuration/encryption-and-signing-credentials.html",
-          "hash": "Vv7XgVNlnmcdfoicWhfNlw=="
+          "hash": "zVDvxKXYXBS/95K56YN2MA=="
         }
       },
       "is_incremental": false,