From bbdee361f1d391f96f0c12a59ac22d8b7fac2ae1 Mon Sep 17 00:00:00 2001
From: HPPinata <83947761+HPPinata@users.noreply.github.com>
Date: Thu, 4 Nov 2021 21:45:10 +0100
Subject: [PATCH] Clarify grammar in DH-GROUP section

Since the second option got removed, the "either" makes no sense any more and may lead to confusion about non existent alternatives
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 1605fc9..d387b73 100644
--- a/README.md
+++ b/README.md
@@ -257,7 +257,7 @@ If you are running the container in a virtualized environment (Hyper-V, VirtualB
 
 To use custom `dhparam.pem` files per-virtual-host, the files should be named after the virtual host with a `dhparam` suffix and `.pem` extension. For example, a container with `VIRTUAL_HOST=foo.bar.com` should have a `foo.bar.com.dhparam.pem` file in the `/etc/nginx/certs` directory.
 
-> COMPATIBILITY WARNING: The default generated `dhparam.pem` key is 4096 bits for A+ security. Some older clients (like Java 6 and 7) do not support DH keys with over 1024 bits. In order to support these clients, you must either provide your own `dhparam.pem`.
+> COMPATIBILITY WARNING: The default generated `dhparam.pem` key is 4096 bits for A+ security. Some older clients (like Java 6 and 7) do not support DH keys with over 1024 bits. In order to support these clients, you must provide your own `dhparam.pem`.
 
 In the separate container setup, no pre-generated key will be available and neither the [jwilder/docker-gen](https://hub.docker.com/r/jwilder/docker-gen) image, nor the offical [nginx](https://registry.hub.docker.com/_/nginx/) image will provide one. If you still want A+ security in a separate container setup, you should mount an RFC7919 DH key file to the nginx container at `/etc/nginx/dhparam/dhparam.pem`.