docs: typo

buchdag · pini-gh · web-flow · commit 31bb4dd3a40e · 2024-06-05T15:57:43.000+02:00
Co-authored-by: pini-gh &lt;pini@pini.fr&gt;
diff --git a/docs/Container-configuration.md b/docs/Container-configuration.md
@@ -34,4 +34,4 @@ You can also create test certificates per container (see [Test certificates](./L
 
 * `ACME_POST_HOOK` - The provided command will be run after every certificate issuance. The action is limited to the commands available inside the **acme-companion** container. For example `--env "ACME_POST_HOOK=echo 'end'"`. For more information see [Pre- and Post-Hook](./Hooks.md)
 
-* `ACME_HTTP_CHALLENGE_LOCATION` - Previously **acme-companion** automatically added the ACME HTTP challenge location to the nginx configuration through files generated in `/etc/nginx/vhost.d`. Recent versions of **nginx-proxy** (>= `1.6`) already include the required location configuration, which remove the need for **acme-companion** to attempt to dynamically add them. If you're running and older version of **nginx-proxy** (or **docker-gen** with an older version of the `nginx.tmpl` file), you can re-enable this behaviour by setting `ACME_HTTP_CHALLENGE_LOCATION` to `true`.
+* `ACME_HTTP_CHALLENGE_LOCATION` - Previously **acme-companion** automatically added the ACME HTTP challenge location to the nginx configuration through files generated in `/etc/nginx/vhost.d`. Recent versions of **nginx-proxy** (>= `1.6`) already include the required location configuration, which remove the need for **acme-companion** to attempt to dynamically add them. If you're running an older version of **nginx-proxy** (or **docker-gen** with an older version of the `nginx.tmpl` file), you can re-enable this behaviour by setting `ACME_HTTP_CHALLENGE_LOCATION` to `true`.

Original file line number	Diff line number	Diff line change
`@@ -34,4 +34,4 @@ You can also create test certificates per container (see [Test certificates](./L`
`34`	`34`
`35`	`35`	* `ACME_POST_HOOK` - The provided command will be run after every certificate issuance. The action is limited to the commands available inside the acme-companion container. For example `--env "ACME_POST_HOOK=echo 'end'"`. For more information see [Pre- and Post-Hook](./Hooks.md)
`36`	`36`
`37`		-* `ACME_HTTP_CHALLENGE_LOCATION` - Previously acme-companion automatically added the ACME HTTP challenge location to the nginx configuration through files generated in `/etc/nginx/vhost.d`. Recent versions of nginx-proxy (>= `1.6`) already include the required location configuration, which remove the need for acme-companion to attempt to dynamically add them. If you're running and older version of nginx-proxy (or docker-gen with an older version of the `nginx.tmpl` file), you can re-enable this behaviour by setting `ACME_HTTP_CHALLENGE_LOCATION` to `true`.
	`37`	+* `ACME_HTTP_CHALLENGE_LOCATION` - Previously acme-companion automatically added the ACME HTTP challenge location to the nginx configuration through files generated in `/etc/nginx/vhost.d`. Recent versions of nginx-proxy (>= `1.6`) already include the required location configuration, which remove the need for acme-companion to attempt to dynamically add them. If you're running an older version of nginx-proxy (or docker-gen with an older version of the `nginx.tmpl` file), you can re-enable this behaviour by setting `ACME_HTTP_CHALLENGE_LOCATION` to `true`.