diff --git a/doc/developer-guide/plugins/example-plugins/tls_bridge.en.rst b/doc/developer-guide/plugins/example-plugins/tls_bridge.en.rst
index d2bcbc350ad..adebd924a24 100644
--- a/doc/developer-guide/plugins/example-plugins/tls_bridge.en.rst
+++ b/doc/developer-guide/plugins/example-plugins/tls_bridge.en.rst
@@ -101,7 +101,7 @@ useful case.
    If this is unsuitable then an identity remap rule can be added for the peer |TS|. If the peer
    |TS| was named "peer.ats" and it listens on port 4443, then the remap rule would be ::
 
-      remap https://peer.ats:4443 https://peer.ats:4443
+      map https://peer.ats:4443 https://peer.ats:4443
 
    Remapping will be disabled for the user agent connection and so it will not need a rule.
 
diff --git a/plugins/experimental/tls_bridge/tls_bridge.cc b/plugins/experimental/tls_bridge/tls_bridge.cc
index 413b4aa6dec..435af57b81f 100644
--- a/plugins/experimental/tls_bridge/tls_bridge.cc
+++ b/plugins/experimental/tls_bridge/tls_bridge.cc
@@ -29,7 +29,7 @@ constexpr char const PLUGIN_NAME[] = "TLS Bridge";
 constexpr char const PLUGIN_TAG[]  = "tls_bridge";
 
 // Base format string for making the internal CONNECT.
-char const CONNECT_FORMAT[] = "CONNECT https:%.*s HTTP/1.1\r\n\r\n";
+char const CONNECT_FORMAT[] = "CONNECT https://%.*s HTTP/1.1\r\n\r\n";
 
 // TextView of the 'CONNECT' method string.
 const TextView METHOD_CONNECT{TS_HTTP_METHOD_CONNECT, TS_HTTP_LEN_CONNECT};