Removes HSTS entry from troubleshooting page (#1371)

removes HSTS entry from troubleshooting page

Author: ZPain8464

content/docs/troubleshooting.mdx

@@ -16,16 +16,6 @@ This article provides troubleshooting information for various tools and features
 
 ## Pomerium Core
 
-### HTTP Strict Transport Security (HSTS)
-
-By default, Pomerium sends the [`Strict-Transport-Security`](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security) response header to the browser, which pins the certificate to our browser for one year. This is common best practice to help prevent man-in-the-middle attacks but can create issues while a new Pomerium configuration is in development.
-
-When you visit an endpoint while Pomerium is using an untrusted certificate (like the self-signed bootstrap certificate or a Let's Encrypt staging certificate), that certificate may be pinned in your browser. Once Pomerium is switched to a trusted production certificate, the untrusted cert must reset in the browser.
-
-While developing your Pomerium environment, consider adjusting the [`SET_RESPONSE_HEADERS`](/docs/reference/set-response-headers) key to remove `Strict-Transport-Security` or reduce the `max-age` value until your production certificates are in place.
-
-See [this article](https://www.ssl2buy.com/wiki/how-to-clear-hsts-settings-on-chrome-firefox-and-ie-browsers) for more information on clearing HSTS for specific endpoints across common browsers.
-
 ### JWT Authentication
 
 When securing the Pomerium Authenticate service with a certificate signed by Let's Encrypt, your upstream applications may reject the certificate when attempting to access the JWT signing key. Here's an example log line from [Grafana](/docs/guides/grafana):