diff --git a/src/docs/markdown/caddyfile/directives/tls.md b/src/docs/markdown/caddyfile/directives/tls.md
index c1c122d8..cf3318dc 100644
--- a/src/docs/markdown/caddyfile/directives/tls.md
+++ b/src/docs/markdown/caddyfile/directives/tls.md
@@ -359,22 +359,31 @@ Obtains certificates using the ACME protocol. Note that `acme` is a default issu
- **any_common_name** is a list of one or more common names; Caddy will choose the first chain that has an issuer that matches with at least one of the specified common names.
+
#### zerossl
-Obtains certificates using the ACME protocol, specifically with ZeroSSL. Note that `zerossl` is a default issuer, so configuring it explicitly is usually unnecessary.
+Obtains certificates using the [ZeroSSL API](https://zerossl.com/documentation/api/).
```caddy-d
-... zerossl [] {
- ...
+... zerossl {
+ validity_days
+ alt_http_port
+ dns []
+ propagation_delay
+ propagation_timeout
+ resolvers
+ dns_ttl
}
```
-The syntax for `zerossl` is exactly the same as for [`acme`](#acme), except that its name is `zerossl` and it can optionally take your ZeroSSL API key.
-
-Its functionality is also the same, except that it will use ZeroSSL's directory by default and it can automatically negotiate EAB credentials (whereas with the `acme` issuer, you have to manually provide EAB credentials and set the directory endpoint).
-
-When explicitly configuring `zerossl`, configuring an `email` is required so that your certificates can appear in your ZeroSSL dashboard.
+Fields for the `zerossl` issuer module share the syntax of those in common with the [`acme` issuer module](#acme).
#### internal