docs: Update for rc2

src/docs/markdown/caddyfile/matchers.md

@@ -223,13 +223,19 @@ By the method (verb) of the HTTP request. Verbs should be uppercase, like `POST`
 
 ### not
 
+```
+not <any other matcher>
+```
+
+or, to negate multiple matchers which get AND'ed, open a block:
+
 ```
 not {
 	<any other matchers...>
 }
 ```
 
-Encloses other matchers and negates their result.
+The results of the enclosed matchers will be negated.
 
 
 ### path

src/docs/markdown/caddyfile/options.md

@@ -39,6 +39,7 @@ Possible options are:
 		burst    <n>
 	}
 	local_certs
+	key_type ed25519|p256|p384|rsa2048|rsa4096
 }
 ```
 
@@ -56,4 +57,5 @@ Possible options are:
 - **on_demand_tls** configures [On-Demand TLS](/docs/automatic-https#on-demand-tls) where it is enabled, but does not enable it (to enable it, use the [on_demand `tls` subdirective](/docs/caddyfile/directives/tls#syntax)). Highly recommended if using in production environments, to prevent abuse.
 	- **ask** will cause Caddy to make an HTTP request to the given URL with a query string of `?domain=` containing the value of the domain name. If the endpoint returns 200 OK, Caddy will be authorized to obtain a certificate for that name.
 	- **interval** and **burst** allows `<n>` certificate operations within `<duration>` interval.
-- **local_certs** causes all certificates to be issued internally by default, rather than through a (public) ACME CA such as Let's Encrypt. This is useful in development environments.
+- **local_certs** causes all certificates to be issued internally by default, rather than through a (public) ACME CA such as Let's Encrypt. This is useful in development environments.
+- **key_type** specifies the type of key to generate for TLS certificates; only change this if you have a specific need to customize it.