From 16d109f9d2ca8a71b9729b1b86e3a34453d05a55 Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen <paulus@paulusschoutsen.nl>
Date: Fri, 13 Oct 2017 23:40:08 -0700
Subject: [PATCH] Update lets_encrypt.markdown

---
 source/_addons/lets_encrypt.markdown | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/source/_addons/lets_encrypt.markdown b/source/_addons/lets_encrypt.markdown
index 98d33c86e03..31fdd13f3b8 100644
--- a/source/_addons/lets_encrypt.markdown
+++ b/source/_addons/lets_encrypt.markdown
@@ -7,13 +7,17 @@ sidebar: true
 comments: false
 sharing: true
 footer: true
-featured: true
+featured: false
 ---
 
+<p class='note'>
+You should not use this if you are also using the [DuckDNS add-on]. The DuckDNS add-on has integrated Let's Encrypt support.
+</p>
+
 Setup and manage a [Let's Encrypt](https://letsencrypt.org/) certificate. This will create a certificate on the first run and will auto-renew if the certificate is within 30 days of expiration.
 
 <p class='note warning'>
-This add-on need port 80/443 to verify the certificate request, please stop all add-ons that also use these ports, or you may not be able to start this add-on.
+This add-on uses ports 80/443 to verify the certificate request. You will need to stop all other add-ons that also use these ports.
 </p>
 
 ```json
@@ -42,3 +46,5 @@ http:
 ```
 
 If you use a other port as `8123` or a SSL proxy, change the port number.
+
+[DuckDNS add-on]: /addons/duckdns/