[OSDOCS-10274]: Add note to etcd docs

Author: lahinson

modules/restore-replace-stopped-etcd-member.adoc

@@ -190,9 +190,9 @@ $ oc delete secret -n openshift-etcd etcd-serving-ip-10-0-131-183.ec2.internal
 $ oc delete secret -n openshift-etcd etcd-serving-metrics-ip-10-0-131-183.ec2.internal
 ----
 
-. Delete and re-create the control plane machine. After this machine is re-created, a new revision is forced and etcd scales up automatically. See "Replacing an unhealthy etcd member whose machine is not running or whose node is not ready" for more information.
+. Delete and re-create the control plane machine. After this machine is re-created, a new revision is forced and etcd scales up automatically. For more information, see "Replacing an unhealthy etcd member whose machine is not running or whose node is not ready".
 +
-If you are running installer-provisioned infrastructure, or you used the Machine API to create your machines, follow these steps. Otherwise, you must create the new master using the same method that was used to originally create it.
+If you are running installer-provisioned infrastructure, or you used the Machine API to create your machines, follow these steps. Otherwise, you must create the new master by using the same method that was used to originally create it.
 
 .. Obtain the machine for the unhealthy member.
 +
@@ -247,6 +247,11 @@ clustername-8qw5l-worker-us-east-1c-pkg26   Running        m4.large    us-east-1
 <1> The new machine, `clustername-8qw5l-master-3` is being created and is ready once the phase changes from `Provisioning` to `Running`.
 +
 It might take a few minutes for the new machine to be created. The etcd cluster Operator will automatically sync when the machine or node returns to a healthy state.
++
+[NOTE]
+====
+Verify the subnet IDs that you are using for your machine sets to ensure that they end up in the correct availability zone.
+====
 
 . Turn the quorum guard back on by entering the following command:
 +