diff --git a/docs/user-guide/certificate-configuration-scenarios.md b/docs/user-guide/certificate-configuration-scenarios.md
index 979808aa82..fb01752fe0 100644
--- a/docs/user-guide/certificate-configuration-scenarios.md
+++ b/docs/user-guide/certificate-configuration-scenarios.md
@@ -56,7 +56,7 @@ Ensure that all alias values for all scenarios use only lower-case.
 
 ## Scenario 1: Use a file-based (PKCS12) keystore with Zowe generated certificates
 
-Use the following procedure to configure your yaml file to enable Zowe to use generated PKCS12 certificates to be used with a keystore directory to store your certificates.
+Use the following procedure to configure the `zowe.setup` section in your yaml file to enable Zowe to use generated PKCS12 certificates to be used with a keystore directory to store your certificates.
 
 1. Set the `type` of the certificate storage to `PKCS12`.
 
@@ -133,7 +133,7 @@ Check out the [video tutorials](https://www.youtube.com/playlist?list=PL8REpLGaY
 
 ## Scenario 2: Use a file-based (PKCS12) keystore and import a certificate generated by another CA
 
-Use the following procedure to configure your yaml file to enable Zowe to use a file-based PKCS12 keystore to import a certificate generted by another CA. 
+Use the following procedure to configure the `zowe.setup` section in your yaml file to enable Zowe to use a file-based PKCS12 keystore to import a certificate generted by another CA. 
 
 1. Set the `type` of the certificate storage to `PKCS12`.
 
@@ -191,7 +191,7 @@ PEM format certificate authorities can be imported and trusted.
    ```
 Your yaml file is now configured to enable Zowe to use a file-based PKCS12 keystore to import a certificate generted by another CA.
 ##  Scenario 3: Use a z/OS keyring-based keystore with Zowe generated certificates
-Use the following procedure to configure your yaml file to enable Zowe to use a z/OS keyring-based keystore with Zowe generated certificates.
+Use the following procedure to configure the `zowe.setup` section in your yaml file to enable Zowe to use a z/OS keyring-based keystore with Zowe generated certificates.
 
 1. Set the `type` of the certificate storage to one of the following keyring types:
 
@@ -269,7 +269,7 @@ Due to the limitation of the `RACDCERT` command, this field should contain exact
 Your yaml file is now configured to enable Zowe to use a z/OS keyring-based keystore with Zowe generated certificates.
 ## Scenario 4: Use a z/OS keyring-based keystore and connect to an existing certificate
 
-Use the following procedure to configure your yaml file to use a z/OS keyring-based keystore and connect to an existing certificate.
+Use the following procedure to configure the `zowe.setup` section in your yaml file to use a z/OS keyring-based keystore and connect to an existing certificate.
 
 1. Set the `type` of the certificate storage to one of the following keyring types:
 
@@ -329,7 +329,7 @@ If you would like to use this example in your Zowe configuration YAML file, repl
 Your yaml file is now configured to use a z/OS keyring-based keystore and connect to an existing certificate.
 ## Scenario 5: Use a z/OS keyring-based keystore and import a certificate stored in a data set
 
-Use the following procedure to configure your yaml file to use a z/OS keyring-based keystore and import a certificate stored in a data set.
+Use the following procedure to configure the `zowe.setup` section in your yaml file to use a z/OS keyring-based keystore and import a certificate stored in a data set.
 
 1. Set the `type` of the certificate storage to one of the following keyring types: