Merge pull request #85926 from lahinson/ocpbugs-12781-etcd-backup

[OCPBUGS-45851]: Correcting etcd backup docs

Author: lahinson

backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc

@@ -10,7 +10,7 @@ etcd is the key-value store for {product-title}, which persists the state of all
 
 Back up your cluster's etcd data regularly and store in a secure location ideally outside the {product-title} environment. Do not take an etcd backup before the first certificate rotation completes, which occurs 24 hours after installation, otherwise the backup will contain expired certificates. It is also recommended to take etcd backups during non-peak usage hours because the etcd snapshot has a high I/O cost.
 
-Be sure to take an etcd backup after you update your cluster. This is important because when you restore your cluster, you must use an etcd backup that was taken from the same z-stream release. For example, an {product-title} 4.y.z cluster must use an etcd backup that was taken from 4.y.z.
+Be sure to take an etcd backup before you update your cluster. Taking a backup before you update is important because when you restore your cluster, you must use an etcd backup that was taken from the same z-stream release. For example, an {product-title} 4.17.5 cluster must use an etcd backup that was taken from 4.17.5.
 
 [IMPORTANT]
 ====
@@ -30,4 +30,4 @@ include::modules/backup-etcd.adoc[leveloffset=+1]
 // Creating automated etcd backups
 include::modules/etcd-creating-automated-backups.adoc[leveloffset=+1]
 include::modules/creating-single-etcd-backup.adoc[leveloffset=+2]
-include::modules/creating-recurring-etcd-backups.adoc[leveloffset=+2]
+include::modules/creating-recurring-etcd-backups.adoc[leveloffset=+2]