Merge pull request #186 from seqeralabs/24.1.3-fix

Fix version typo and admonition format in Enterprise release notes
seqeralabs · Aug 23, 2024 · 627bfe7 · 627bfe7
2 parents dac5bc0 + 45f2622
commit 627bfe7
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/...form_versioned_docs/version-24.1/enterprise/release_notes/enterprise_latest.mdx b/...form_versioned_docs/version-24.1/enterprise/release_notes/enterprise_latest.mdx
@@ -78,18 +78,20 @@ Enterprise deployments that have customized this value previously will need to a
 
 1. This version includes an update to the Platform Enterprise H8 cache. **Do not start the upgrade while any pipelines are in a `running` state as active run data may be lost.**
 1. This version requires a database schema update. Make a backup of your Platform database prior to upgrade.
-1. If you are upgrading from a version older than 23.4.1, update your installation to version [23.4.4](./23.4.mdx) first, before updating to 24.1.2 with the steps below.
+1. If you are upgrading from a version older than 23.4.1, update your installation to version [23.4.4](./23.4.mdx) first, before updating to 24.1 with the steps below.
 1. For recommended Platform memory settings, add the following environment variable to your Platform configuration values (`tower.env`, `configmap.yml`, etc. ):
     ```console 
     JAVA_OPTS: -Xms1000M -Xmx2000M -XX:MaxDirectMemorySize=800m -Dio.netty.maxDirectMemory=0 -Djdk.nio.maxCachedBufferSize=262144
     ```
 1. See [Upgrade installation](../upgrade.mdx) for database backup and installation upgrade guidance.
 
+:::info
 Docker Compose deployments require downtime while upgrading services. Restarting the application may take several minutes. See [Docker compose deployment](../docker-compose.mdx) for more information.
 
 For Kubernetes deployments, apply the 24.1 `tower-cron.yml` to your cron pod and wait for the cron pod to be running before applying the `tower-svc.yml` to your backend pod and restarting the service. If the cron pod update is interrupted, you may need to restore the instance from your DB backup and start again. See [Kubernetes deployment](../kubernetes.mdx) for more information. 
 
-For custom deployments with third-party services such as ArgoCD, [contact support](https://support.seqera.io) for assistance during upgrade.  
+For custom deployments with third-party services such as ArgoCD, [contact support](https://support.seqera.io) for assistance during upgrade. 
+::: 
 
 ## Changelog