Configure XMS: example update

docs/user-guide/api-mediation/using-api-mediation-layer.md

@@ -4,7 +4,7 @@ There are numerous ways you can use the API Mediation Layer. Review this topic a
 For information about the API versioning, see [API Catalog and Versioning](../../extend/extend-apiml/api-mediation-versioning.md).
 
 **Tip:** 
-For testing purposes, it is not necessary to set up certificates when configuring the API Mediation Layer. You can configure Zowe without certificate setup and run Zowe with `verify_certificates: DISABLED`.  
+For testing purposes, it is not necessary to set up certificates when configuring the API Mediation Layer. You can configure Zowe without certificate setup and run Zowe with `zowe.verifyCertificates: DISABLED`.  
 
 For production environments, certificates are required. Ensure that certificates for each of the following services are issued by the Certificate Authority (CA) and that all keyrings contain the public part of the certificate for the relevant CA.  
 
@@ -66,7 +66,7 @@ There are various options for using the API Catalog:
 * [Viewing Service Information abd API Documentation in the API Catalog](../api-mediation-view-service-information-and-api-doc.md)
 * [Changing an expired password via API Catalog](../api-mediation-change-password-via-catalog.md)
 
-### Additional use case when usig API Mediation Layer
+### Additional use case when using API Mediation Layer
 
 * [SMF records](./api-mediation-smf.md)
 

docs/user-guide/configure-xmem-server.md

@@ -123,7 +123,7 @@ For example, the sample JCL below shows `ZWESISTC` where the APF-authorized PDSE
 
 ## SAF configuration
 
-Because the ZIS server makes z/OS security calls it restrits which clients are able to use it services, by requiring them to have `READ` access to a security profile `ZWES.IS` in the `FACILITY` class.  
+Because the ZIS server makes z/OS security calls it restricts which clients are able to use the services, by requiring them to have `READ` access to a security profile `ZWES.IS` in the `FACILITY` class.  
 
 The Zowe launcher started task `ZWESLSTC` needs to be able to access the ZIS server, which requires that the user ID `ZWESVUSR` has access to `ZWES.IS`.  The steps to do this are described in [Configure the cross memory server for SAF](configure-zos-system.md#configure-the-cross-memory-server-for-saf).  
 
@@ -153,7 +153,7 @@ The cross memory server runs as a started task `ZWESISTC` that uses the load mod
 
 In some use cases, the Zowe cross memory server has to spawn child address spaces, which are known as auxiliary (AUX) address spaces.  The auxiliary address spaces run as the started task `ZWESASTC` using the load module `ZWESAUX` and are started, controlled, and stopped by the cross memory server.  
 
-An example of when an auxiliary address space is used is for a system service that requires supervisor state but cannot run in cross-memory mode. The service can be run in an AUX address space which is invoked by the Cross Memory Server acting as a proxy for unauthorized users of the service. 
+An example of when an auxiliary address space is used is for a system service that requires a supervisor state but cannot run in cross-memory mode. The service can be run in an AUX address space which is invoked by the Cross Memory Server acting as a proxy for unauthorized users of the service. 
 
 Do not install the Zowe auxiliary address space unless a Zowe extension product's installation guide explicitly asks for it to be done.  This will occur if the extension product requires services of Zowe that cannot be performed by the cross memory server and an auxiliary address space needs to be started.  
 
@@ -198,16 +198,17 @@ The starting and stopping of the `ZWESLSTC` started task for the main Zowe serve
 ## Troubleshooting
 To diagnose problems that may occur with the Zowe `ZWESLSTC` not being able to attach to the `ZWESISTC` cross memory server, a log file `zssServer-yyyy-mm-dd-hh-mm.log` is created in the log directory each time ZIS is started.  More details on diagnosing errors can be found in [Zowe Application Framework issues](../troubleshoot/app-framework/app-troubleshoot.md#cannot-log-in-to-the-zowe-desktop).
 
-If the `crossMemoryServerName` is changed in `zowe.yaml` and the default name is not applied, manually update the `PROC NAME` in the corresponding `PROCLIB`.
+If the `crossMemoryServerName` is changed in `zowe.yaml` and the default name is not applied, manually update the `NAME` in the corresponding `PROCLIB`.
 
-For example, the ZIS server name is changed from its default of `ZWESIS_STC` to be `ZWESIS_02`. The `PROCLIB` member line 1 is updated from `//ZWESIS01  PROC NAME='ZWESIS_STD',MEM=00,RGN=0M` to `//ZWESIS_01  PROC NAME='ZWESIS_02',MEM=02,RGN=0M`. 
-And the `zowe.yaml` file is updated to use the `02` instance:
+For example, the ZIS server name is changed from its default of `ZWESIS_STD` to be `ZWESIS_02`. The `PROCLIB` member line 1 is updated from `//ZWESIS01  PROC NAME='ZWESIS_STD',MEM=00,RGN=0M` to `//ZWESIS_01  PROC NAME='ZWESIS_02',MEM=00,RGN=0M`. 
+And the `zowe.yaml` file is updated to use the `ZWESIS_02` instance:
 
 ```
-zss:
+components:
+  zss:
     crossMemoryServerName: ZWESIS_02
 ```
 
 ## Next step
 
-After you complete the configuration of the Zowe cross memory server, you may [configure Zowe for High Availability](./zowe-ha-overview), or proceed to [starting Zowe](./start-zowe-zos).
+After you complete the configuration of the Zowe cross memory server, you may [configure Zowe for High Availability](./zowe-ha-overview), or proceed to [starting Zowe](./start-zowe-zos).