Incorporating peer review comments

Author: Dhruv-Soni11

modules/gitops-release-notes-1-16-0.adoc

@@ -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