diff --git a/TLS.md b/TLS.md
index eec2b1e..93f709c 100644
--- a/TLS.md
+++ b/TLS.md
@@ -26,13 +26,10 @@ mkcert localhost 127.0.0.1 ::1
 
 This should create a file called `localhost+2.pem` and another file called `localhost+2-key.pem`.
 
-
 **Continue with [TLS Using a Caddy Container](#tls-using-caddy-container).**
 
 ## TLS Using a Caddy Container
 
-Originally we suggested hitch for TLS proxy, but because hitch is protocol agnostic, It does not know about HTTP. In other words it did not set X-Forwarded-Proto or X-Forwarded-For on requests seen by the backend server and thus NetBox deployments using hitch would respond to API requests with http  references instead of https.
-
 [Caddy](https://caddyserver.com/) is a powerful, extensible platform to serve your sites, services, and apps, written in Go.  It is able to handle HTTP redirection, ensures the API responses reference https, and even auto create/renew your HTTPS Certificate using Let's Encrypt.
 
 First, you need to create a Cadyfile with the required reverse proxy & tls settings you require.  
@@ -95,3 +92,4 @@ services:
       - 443:443
 ```
 
+## About _hitch_