Update configure-certificates.md

Signed-off-by: Wen Ting Su (Sam) <[email protected]>
zowe · Jul 26, 2023 · 74ebd94 · 74ebd94
1 parent b669cfc
commit 74ebd94
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/user-guide/configure-certificates.md b/docs/user-guide/configure-certificates.md
@@ -75,7 +75,7 @@ Some Zowe components act as a server, some as a client, and some as both - clien
 
 
 ### Hostname validity
-The host communicating with a certificate should have its hostname match one of the values of the certificate's Common Name or Subject Alternate Name (SAN). If this condition is not true for at least one of the certificates that are seen by Zowe, then you can wish to set [NONSTRICT verification](#nonstrict-verification) within Zowe's configuration.
+The host communicating with a certificate should have its hostname match one of the values of the certificate's Common Name or Subject Alternate Name (SAN). If this condition is not true for at least one of the certificates that are seen by Zowe, then you may wish to set [NONSTRICT verification](#nonstrict-verification) within Zowe's configuration.
 
 ### z/OSMF access
 The z/OSMF certificate is verified according to Zowe's [Certificate verification setting](#certificate-verification), as is the case with any certificate that is seen by Zowe. However, Zowe will also set up a trust relationship with z/OSMF within Zowe's truststore during certificate setup automation if the certificate setting is set to any value other than [DISABLED](#disabled-verification).