From 4d50836aea2df8d0e2ba24573f03319d8ff0ccd6 Mon Sep 17 00:00:00 2001 From: Matthew Mols Date: Thu, 11 Dec 2025 11:54:11 -0600 Subject: [PATCH] docs: fix indent on warning in upgrade doc --- docs/using/upgrade-db.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/using/upgrade-db.md b/docs/using/upgrade-db.md index 70a89ab3..3d01e0a4 100644 --- a/docs/using/upgrade-db.md +++ b/docs/using/upgrade-db.md @@ -164,7 +164,7 @@ As an alternative to using the zero downtime add node approach, you can also [cr !!! warning -You should thoroughly test major version upgrade scenarios in a non-production environment before upgrading your production database. Additionally, we recommend you review the [Backup and Restore](./backup-restore.md) documentation, and take a fresh backup of your database before upgrading to ensure that you are prepared to restore in the event you run into problems. + You should thoroughly test major version upgrade scenarios in a non-production environment before upgrading your production database. Additionally, we recommend you review the [Backup and Restore](./backup-restore.md) documentation, and take a fresh backup of your database before upgrading to ensure that you are prepared to restore in the event you run into problems.