[auto] adding content to backport-55-aa0cdb546d7c9e4ef5c52ad23c656272b7599e23->release-x.55.x (#359)

Co-authored-by: Metabase Docs bot <[email protected]>

Author: github-automation-metabase

_docs/latest/installation-and-operation/activating-the-enterprise-edition.md

@@ -58,7 +58,7 @@ To get all the features available when upgrading to a _self-hosted_ [Pro or Ente
 Assuming you've been using a [production application database](../installation-and-operation/configuring-application-database), you'll want to:
 
 1. [Back up your application database](./backing-up-metabase-application-data).
-2. Download the Enterprise Edition version that corresponds with your current Metabase version. So if you're running the Docker image for {{site.data.latest_version}}, you should switch to the Docker image for {{site.data.latest_enterprise}}. To see a list of available versions for both the Open Source and Enterprise Editions, check out [Metabase releases](https://github.com/metabase/metabase/releases).
+2. Download the Enterprise Edition version that corresponds with your current Metabase version. So if you're running the Docker image for {{site.latest_version}}, you should switch to the Docker image for {{site.latest_enterprise}}. To see a list of available versions for both the Open Source and Enterprise Editions, check out [Metabase releases](https://github.com/metabase/metabase/releases).
 3. Stop your current Metabase Open Source edition.
 4. Swap in the Enterprise Edition Docker image or jar that you downloaded.
 5. Start your Metabase like you normally would using the new Enterprise Edition image or jar. You don't need to do anything with your application database (which you've backed up in step one, right?).

_docs/v0.55/installation-and-operation/activating-the-enterprise-edition.md

@@ -56,7 +56,7 @@ To get all the features available when upgrading to a _self-hosted_ [Pro or Ente
 Assuming you've been using a [production application database](../installation-and-operation/configuring-application-database), you'll want to:
 
 1. [Back up your application database](./backing-up-metabase-application-data).
-2. Download the Enterprise Edition version that corresponds with your current Metabase version. So if you're running the Docker image for {{site.data.latest_version}}, you should switch to the Docker image for {{site.data.latest_enterprise}}. To see a list of available versions for both the Open Source and Enterprise Editions, check out [Metabase releases](https://github.com/metabase/metabase/releases).
+2. Download the Enterprise Edition version that corresponds with your current Metabase version. So if you're running the Docker image for {{site.latest_version}}, you should switch to the Docker image for {{site.latest_enterprise}}. To see a list of available versions for both the Open Source and Enterprise Editions, check out [Metabase releases](https://github.com/metabase/metabase/releases).
 3. Stop your current Metabase Open Source edition.
 4. Swap in the Enterprise Edition Docker image or jar that you downloaded.
 5. Start your Metabase like you normally would using the new Enterprise Edition image or jar. You don't need to do anything with your application database (which you've backed up in step one, right?).

_site/docs/latest/installation-and-operation/activating-the-enterprise-edition.html

@@ -4736,7 +4736,7 @@ <h2 id="upgrading-from-a-self-hosted-metabase-open-source-edition-to-a-pro-or-en
 
 <ol>
   <li><a href="./backing-up-metabase-application-data">Back up your application database</a>.</li>
-  <li>Download the Enterprise Edition version that corresponds with your current Metabase version. So if you’re running the Docker image for , you should switch to the Docker image for . To see a list of available versions for both the Open Source and Enterprise Editions, check out <a href="https://github.com/metabase/metabase/releases">Metabase releases</a>.</li>
+  <li>Download the Enterprise Edition version that corresponds with your current Metabase version. So if you’re running the Docker image for v0.55.2, you should switch to the Docker image for v1.55.2. To see a list of available versions for both the Open Source and Enterprise Editions, check out <a href="https://github.com/metabase/metabase/releases">Metabase releases</a>.</li>
   <li>Stop your current Metabase Open Source edition.</li>
   <li>Swap in the Enterprise Edition Docker image or jar that you downloaded.</li>
   <li>Start your Metabase like you normally would using the new Enterprise Edition image or jar. You don’t need to do anything with your application database (which you’ve backed up in step one, right?).</li>

_site/docs/v0.55/installation-and-operation/activating-the-enterprise-edition.html

@@ -4738,7 +4738,7 @@ <h2 id="upgrading-from-a-self-hosted-metabase-open-source-edition-to-a-pro-or-en
 
 <ol>
   <li><a href="./backing-up-metabase-application-data">Back up your application database</a>.</li>
-  <li>Download the Enterprise Edition version that corresponds with your current Metabase version. So if you’re running the Docker image for , you should switch to the Docker image for . To see a list of available versions for both the Open Source and Enterprise Editions, check out <a href="https://github.com/metabase/metabase/releases">Metabase releases</a>.</li>
+  <li>Download the Enterprise Edition version that corresponds with your current Metabase version. So if you’re running the Docker image for v0.55.2, you should switch to the Docker image for v1.55.2. To see a list of available versions for both the Open Source and Enterprise Editions, check out <a href="https://github.com/metabase/metabase/releases">Metabase releases</a>.</li>
   <li>Stop your current Metabase Open Source edition.</li>
   <li>Swap in the Enterprise Edition Docker image or jar that you downloaded.</li>
   <li>Start your Metabase like you normally would using the new Enterprise Edition image or jar. You don’t need to do anything with your application database (which you’ve backed up in step one, right?).</li>