diff --git a/docs/licensing/replace-license.mdx b/docs/licensing/replace-license.mdx
index f69a0270e3..bda270d8a7 100644
--- a/docs/licensing/replace-license.mdx
+++ b/docs/licensing/replace-license.mdx
@@ -28,7 +28,7 @@ import ContentFrame from "@site/src/components/ContentFrame";
 * In this article:
     * [Replace your license using a configuration key](../licensing/replace-license.mdx#replace-your-license-using-a-configuration-key)  
     * [Replace your license via Studio](../licensing/replace-license.mdx#replace-your-license-via-studio)  
-    * [Maintain auto-renewal of Let's Encrypt certificates](../licensing/replace-license.mdx#maintain-auto-renewal-of-let-s-encrypt-certificates)  
+    * [Let's Encrypt certificate renewal after a license replacement](../licensing/replace-license.mdx#let-s-encrypt-certificate-renewal-after-a-license-replacement)  
     * [Upgrade a license older than 6.x](../licensing/replace-license.mdx#upgrade-a-license-older-than-6-x)
 
 </Admonition>
@@ -64,10 +64,11 @@ To replace your existing license with a new one, open the **About** view and cli
 
 </Panel>
 
-<Panel heading="Maintain auto-renewal of Let's Encrypt certificates">
+<Panel heading="Let's Encrypt certificate renewal after a license replacement">
 
-* If you installed RavenDB using the [Setup Wizard](../start/installation/setup-wizard/overview.mdx) and applied a Let's Encrypt certificate, contact [customer support](https://ravendb.net/contact) before replacing your license to keep automatic certificate renewal working.  
-* Otherwise, the change in your license ID will cause a mismatch between your new ID and the ID that Let's Encrypt expects during certificate renewal.  
+When you replace your license on a server that was set up using the [Setup Wizard](../start/installation/setup-wizard/overview.mdx) 
+with a Let's Encrypt certificate, RavenDB automatically updates its records to associate your domain with the new license before activating it.  
+Certificate auto-renewal will continue to work without any manual steps.  
 
 </Panel>
 
diff --git a/versioned_docs/version-6.2/start/licensing/replace-license.mdx b/versioned_docs/version-6.2/start/licensing/replace-license.mdx
index 03e01cba9f..e69cc39b2b 100644
--- a/versioned_docs/version-6.2/start/licensing/replace-license.mdx
+++ b/versioned_docs/version-6.2/start/licensing/replace-license.mdx
@@ -26,7 +26,7 @@ import LanguageContent from "@site/src/components/LanguageContent";
 
 * In this page:
     * [Replace license from Studio](../../start/licensing/replace-license.mdx#replace-license-from-studio)  
-    * [Maintain auto-renewal of Let's Encrypt certificates](../../start/licensing/replace-license.mdx#maintain-auto-renewal-of-let)  
+    * [Let's Encrypt certificate renewal after a license replacement](../../start/licensing/replace-license.mdx#lets-encrypt-certificate-renewal-after-a-license-replacement)  
     * [Upgrade a License Key For RavenDB 6.x](../../start/licensing/replace-license.mdx#upgrade-a-license-key-for-ravendb-6x)  
 
 </Admonition>
@@ -46,13 +46,11 @@ Replace the existing license with the new one from the Studio:
 
 
 
-## Maintain auto-renewal of Let's Encrypt certificates 
+## Let's Encrypt certificate renewal after a license replacement
 
-* If you set RavenDB up using the [Setup Wizard](../../start/installation/setup-wizard/overview.mdx) 
-  and used a Let's Encrypt certificate,  contact [customer support](https://ravendb.net/contact) 
-  when changing your license to maintain auto-renewals of certificates.  
-* Otherwise, changing your license ID will cause a mismatch between the new 
-  license ID and the ID that Let's Encrypt expects when renewing the certificate.  
+When you replace your license on a server that was set up using the [Setup Wizard](../../start/installation/setup-wizard/overview.mdx) 
+with a Let's Encrypt certificate, RavenDB automatically updates its records to associate your domain with the new license before activating it.  
+Certificate auto-renewal will continue to work without any manual steps.  
 
 
 
diff --git a/versioned_docs/version-7.0/start/licensing/replace-license.mdx b/versioned_docs/version-7.0/start/licensing/replace-license.mdx
index 03e01cba9f..e69cc39b2b 100644
--- a/versioned_docs/version-7.0/start/licensing/replace-license.mdx
+++ b/versioned_docs/version-7.0/start/licensing/replace-license.mdx
@@ -26,7 +26,7 @@ import LanguageContent from "@site/src/components/LanguageContent";
 
 * In this page:
     * [Replace license from Studio](../../start/licensing/replace-license.mdx#replace-license-from-studio)  
-    * [Maintain auto-renewal of Let's Encrypt certificates](../../start/licensing/replace-license.mdx#maintain-auto-renewal-of-let)  
+    * [Let's Encrypt certificate renewal after a license replacement](../../start/licensing/replace-license.mdx#lets-encrypt-certificate-renewal-after-a-license-replacement)  
     * [Upgrade a License Key For RavenDB 6.x](../../start/licensing/replace-license.mdx#upgrade-a-license-key-for-ravendb-6x)  
 
 </Admonition>
@@ -46,13 +46,11 @@ Replace the existing license with the new one from the Studio:
 
 
 
-## Maintain auto-renewal of Let's Encrypt certificates 
+## Let's Encrypt certificate renewal after a license replacement
 
-* If you set RavenDB up using the [Setup Wizard](../../start/installation/setup-wizard/overview.mdx) 
-  and used a Let's Encrypt certificate,  contact [customer support](https://ravendb.net/contact) 
-  when changing your license to maintain auto-renewals of certificates.  
-* Otherwise, changing your license ID will cause a mismatch between the new 
-  license ID and the ID that Let's Encrypt expects when renewing the certificate.  
+When you replace your license on a server that was set up using the [Setup Wizard](../../start/installation/setup-wizard/overview.mdx) 
+with a Let's Encrypt certificate, RavenDB automatically updates its records to associate your domain with the new license before activating it.  
+Certificate auto-renewal will continue to work without any manual steps.  
 
 
 
diff --git a/versioned_docs/version-7.1/start/licensing/replace-license.mdx b/versioned_docs/version-7.1/start/licensing/replace-license.mdx
index 03e01cba9f..e69cc39b2b 100644
--- a/versioned_docs/version-7.1/start/licensing/replace-license.mdx
+++ b/versioned_docs/version-7.1/start/licensing/replace-license.mdx
@@ -26,7 +26,7 @@ import LanguageContent from "@site/src/components/LanguageContent";
 
 * In this page:
     * [Replace license from Studio](../../start/licensing/replace-license.mdx#replace-license-from-studio)  
-    * [Maintain auto-renewal of Let's Encrypt certificates](../../start/licensing/replace-license.mdx#maintain-auto-renewal-of-let)  
+    * [Let's Encrypt certificate renewal after a license replacement](../../start/licensing/replace-license.mdx#lets-encrypt-certificate-renewal-after-a-license-replacement)  
     * [Upgrade a License Key For RavenDB 6.x](../../start/licensing/replace-license.mdx#upgrade-a-license-key-for-ravendb-6x)  
 
 </Admonition>
@@ -46,13 +46,11 @@ Replace the existing license with the new one from the Studio:
 
 
 
-## Maintain auto-renewal of Let's Encrypt certificates 
+## Let's Encrypt certificate renewal after a license replacement
 
-* If you set RavenDB up using the [Setup Wizard](../../start/installation/setup-wizard/overview.mdx) 
-  and used a Let's Encrypt certificate,  contact [customer support](https://ravendb.net/contact) 
-  when changing your license to maintain auto-renewals of certificates.  
-* Otherwise, changing your license ID will cause a mismatch between the new 
-  license ID and the ID that Let's Encrypt expects when renewing the certificate.  
+When you replace your license on a server that was set up using the [Setup Wizard](../../start/installation/setup-wizard/overview.mdx) 
+with a Let's Encrypt certificate, RavenDB automatically updates its records to associate your domain with the new license before activating it.  
+Certificate auto-renewal will continue to work without any manual steps.