Incorporating peer review comments

Author: Dhruv-Soni11

Diff for: modules/gitops-release-notes-1-16-0.adoc

@@ -60,8 +60,8 @@ When the {gitops-title} Operator is deployed on an {OCP} cluster configured for
 
 * Before this update, the on-deployed trigger in the Argo CD notification-controller could incorrectly send a success notification while the application was still in the `progressing` state. This issue arose from the way Argo CD handled application status updates. With this update, a new timestamp field, `status.health.lastTransitionTime`, has been introduced in the application status to address this issue. This field prevents false-positive alerts by capturing the last health status change and enabling the on-deployed trigger to send notifications only after a stable transition. link:https://issues.redhat.com/browse/GITOPS-3699[GITOPS-3699]
 
-* Before this update, during an upgrade, the `argocd-redis-ha-configmap`, `argocd-redis-ha-health-configmap`, and the Redis HA `StatefulSet` resources were not correctly updated. This led to Redis HA pods encountering an `AUTH` error.
-With this update, the {gitops-shortname} Operator correctly updates the Redis HA config maps and `StatefulSet` during an upgrade process. As a result, Redis HA pods are prevented from entering an `AUTH` error state post-upgrade. link:https://issues.redhat.com/browse/GITOPS-5975[GITOPS-5975]
+* Before this update, during an upgrade, the `argocd-redis-ha-configmap`, `argocd-redis-ha-health-configmap`, and the Redis HA ``StatefulSet'` resources were not correctly updated. This led to Redis HA pods encountering an `AUTH` error.
+With this update, the {gitops-shortname} Operator correctly updates the Redis HA config maps and ``StatefulSet'` during an upgrade process. As a result, Redis HA pods are prevented from entering an `AUTH` error state post-upgrade. link:https://issues.redhat.com/browse/GITOPS-5975[GITOPS-5975]
 
 * Before this update, any changes to the `serviceAccountName` and `serviceAccount` fields in the Redis deployment were not reconciled by the {gitops-title} Operator. With this update, this issue is fixed by ensuring that any unintended changes to these fields are reset to their expected value, `<argocd-instance-name>-argocd-redis`. link:https://issues.redhat.com/browse/GITOPS-6032[GITOPS-6032]
 
@@ -96,9 +96,9 @@ With this update, this issue is fixed. This update resolves the issue by integra
 [id="known-issues-1-16-0_{context}"]
 == Known Issues
 
-* There is currently a known issue that assigns a lower `SecurityContextConstraints` (SCC) to Redis service account in {gitops-shortname} v1.16 after upgrading from {gitops-shortname} v1.15 to v1.16. The {gitops-shortname} Operator does not update the `securityContext` of the `redis-ha-server` StatefulSet, which causes the container's user to be statically set instead of being randomly assigned as required by the `restricted-v2` SCC. The `redis-ha-server` StatefulSet pods retain the old configurations and are not updated with the new settings. As a result, the new configuration of the StatefulSet is not applied correctly.
+* There is currently a known issue that assigns a lower `SecurityContextConstraints` (SCC) to Redis service account in {gitops-shortname} v1.16 after upgrading from {gitops-shortname} v1.15 to v1.16. The {gitops-shortname} Operator does not update the `securityContext` of the `redis-ha-server` `StatefulSet`, which causes the container's user to be statically set instead of being randomly assigned as required by the `restricted-v2` SCC. The `redis-ha-server` `StatefulSet' pods retain the old configurations and are not updated with the new settings. As a result, the new configuration of the `StatefulSet' is not applied correctly.
 +
-Workaround: Manually delete the `redis-ha-server` StatefulSet to trigger the re-creation of the pods with the updated settings. link:https://issues.redhat.com/browse/GITOPS-6670[GITOPS-6670]
+Workaround: Manually delete the `redis-ha-server` `StatefulSet' to trigger the re-creation of the pods with the updated settings. link:https://issues.redhat.com/browse/GITOPS-6670[GITOPS-6670]
 
 [id="deprecated-features-1-16-0_{context}"]
 == Deprecated and removed features