cloud/bmaas: correctly format table
Change-Id: Iafa4967d655c31f107167a82909eabc21bb4e2c5
Reviewed-on: https://review.monogon.dev/c/monogon/+/1792
Tested-by: Jenkins CI
Reviewed-by: Serge Bazanski <serge@monogon.tech>
diff --git a/cloud/bmaas/DEPLOYING.md b/cloud/bmaas/DEPLOYING.md
index 0dacf0b..a1326f6 100644
--- a/cloud/bmaas/DEPLOYING.md
+++ b/cloud/bmaas/DEPLOYING.md
@@ -18,9 +18,10 @@
versions of the components.
3. Repeat from point 1 until the newest wanted CL version is running.
-^ ID ^ Schema range ^ CL range ^ Notes ^
-| 0 | < 1672749980 | >= 0 | Initial production schema. |
-| 1 | >= 1672768890 | >= 1565 | Exponential backoff support. |
+| ID | Schema range | CL range | Notes |
+|----|---------------|----------|------------------------------|
+| 0 | < 1672749980 | >= 0 | Initial production schema. |
+| 1 | >= 1672768890 | >= 1565 | Exponential backoff support. |
For example, if the cluster is at version 1200, it should first be upgraded to
< 1565 (to reach row 0), then to anything higher than 1565 (to reach row 1).