diff --git a/src/docs/markdown/caddyfile/directives/reverse_proxy.md b/src/docs/markdown/caddyfile/directives/reverse_proxy.md
index a23d89e..0eb0609 100644
--- a/src/docs/markdown/caddyfile/directives/reverse_proxy.md
+++ b/src/docs/markdown/caddyfile/directives/reverse_proxy.md
@@ -60,7 +60,8 @@ Upstream addresses can take the form of a conventional [Caddy network address](/
 - `https://example.com`
 - `example.com`
 - `unix//var/php.sock`
-- `srv+http://internal:5099`
+- `srv+http://internal.service.consul`
+- `srv+https://internal.service.consul`
 
 Note: Schemes cannot be mixed, since they modify the common transport configuration (a TLS-enabled transport cannot carry both HTTPS and plaintext HTTP). Specifying ports 80 and 443 are the same as specifying the HTTP and HTTPS schemes, respectively. Any explicit transport configuration will not be overwritten, and omitting schemes or using other ports will not assume a particular transport. Additionally, schemes cannot contain paths or query strings, as that would imply simultaneous rewriting the request while proxying, which behavior is not defined or supported. If the address is not a URL (i.e. does not have a scheme), then placeholders can be used, but this makes the upstream dynamic.
 
@@ -204,4 +205,4 @@ route /prefix/* {
 	uri strip_prefix /prefix
 	reverse_proxy localhost:9000
 }
-```
\ No newline at end of file
+```