From 92cb56746d3fc04b1e274da08f31aea42bcf6523 Mon Sep 17 00:00:00 2001
From: Tim Usner <40451181+timuthy@users.noreply.github.com>
Date: Tue, 17 Jul 2018 13:02:27 +0200
Subject: [PATCH] Add *.example.com to SAN

*.example.com is set as Common Name and thus part of SANs.
---
 docs/tutorials/acme/dns-validation.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/tutorials/acme/dns-validation.rst b/docs/tutorials/acme/dns-validation.rst
index f2a8f8e0f..416d974be 100644
--- a/docs/tutorials/acme/dns-validation.rst
+++ b/docs/tutorials/acme/dns-validation.rst
@@ -123,7 +123,7 @@ If the certificate is obtained successfully, the resulting key pair will be
 stored in a secret called ``example-com-tls`` in the same namespace as the Certificate.
 
 The certificate will have a common name of ``*.example.com`` and the
-`Subject Alternative Names `_ (SANs) will be ``example.com`` and ``foo.com``.
+`Subject Alternative Names `_ (SANs) will be ``*.example.com``, ``example.com`` and ``foo.com``.
 
 In our Certificate we have referenced the ``letsencrypt-staging`` Issuer above.
 The Issuer must be in the same namespace as the Certificate.