Fix wording.

zammad · Feb 26, 2024 · 9ff6dcc · 9ff6dcc
1 parent 11e5dbc
commit 9ff6dcc
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/zammad/README.md b/zammad/README.md
@@ -166,11 +166,11 @@ redis:
 #### Storage Requirements Changed
 
 - Zammad no longer requires a volume for `var/`
-- If you use the default `DB` or the new `S3` storage back end for file storage, you don't need to do anything.
-- If you use the `File` storage back end instead, Zammad now requires a `ReadWriteMany` volume for `storage/` that is shared in the cluster.
+- If you use the default `DB` or the new `S3` storage backend for file storage, you don't need to do anything.
+- If you use the `File` storage backend instead, Zammad now requires a `ReadWriteMany` volume for `storage/` that is shared in the cluster.
   - If you already had one via `persistence.existingClaim` before, you need to ensure it has `ReadWriteMany` access to be mountable across nodes.
   - If you used the default `PersistentVolumeClaim` of the `StatefulSet`, you need to take manual action:
-    - You can either migrate to `S3` storage before upgrading to the new major version as described above in [Configuration](#how-to-migrate-from-file-to-s3-storage).
+    - You can either migrate to `S3` storage **before upgrading** to the new major version as described above in [Configuration](#how-to-migrate-from-file-to-s3-storage).
     - Or you can provide an `existingClaim` with `ReadWriteMany` permission and migrate your existing data to it from the old `StatefulSet`.
 
 ### From Chart Version 9.x to 10.0.0