copyedited and added PR content to 5.2

Author: rachel-netq

content/cumulus-netq-51/NVLink-Management/Register-Services.md

@@ -5,7 +5,7 @@ weight: 325
 toc: 3
 ---
 
-NetQ must register with the NMX-T and NMX-C services to begin receiving network telemetry and control data. Communication between these services is secured using certificate-based mTLS encryption. These certificates are automatically created during the installation process, but you must configure them on the switch trays hosting NMX-C and NMX-T.
+NetQ must register with the NMX-T (telemetry) and NMX-C (controller) services to begin receiving network telemetry and control data. Communication between these services is secured using certificate-based mTLS encryption. These certificates are automatically created during the installation process, but you must configure them on the switch trays hosting NMX-C and NMX-T.
 
 {{<notice tip>}}
 You can also perform the steps outlined on this page using the <code>/v1/switch-profiles</code> endpoint. Refer to {{<link url="NVLink-Bringup" text="NVLink Bringup">}} for more information.
@@ -35,11 +35,13 @@ Files created:
 Done.
 ```
 
-3. Copy the `example-ca.crt` and `example-tls.p12` files to the switch tray. Replace the filenames with the actual names of the files. Use the {{<exlink url="https://docs.nvidia.com/networking/display/nvidianvosusermanualfornvlinkswitchesv25022225/cluster+manager+commands" text="NVOS cluster manager commands">}} to apply the certificates to both NMX-C and NMX-T. Applying the certificates is not enough, be sure to enable the manager using `nv action update cluster apps <app-name> manager` to get the port open for both apps. 
+3. Copy the `example-ca.crt` and `example-tls.p12` files to the switch tray. Replace the filenames with the actual names of the files. Use the {{<exlink url="https://docs.nvidia.com/networking/display/nvidianvosusermanualfornvlinkswitchesv25022225/cluster+manager+commands" text="NVOS cluster manager commands">}} to apply the certificates to both NMX-C and NMX-T. 
+
+4. After the certificates are applied, enable the manager with the `nv action update cluster apps <app-name> manager` command.   
 
 ## Register Services
 
-Register the services by making a POST request to the `v1/services` endpoint. NMX-c aka the controller is listening on port 9370 while NMX-t aka TELEMETRY is listening on port 9351.
+Register the services by making a POST request to the `v1/services` endpoint. NMX-C listens on port 9370 and NMX-T listens on port 9351.
 
 {{<tabs "TabID42" >}}
 

content/cumulus-netq-52/NVLink-Management/Register-Services.md

@@ -35,11 +35,13 @@ Files created:
 Done.
 ```
 
-3. Copy the `example-ca.crt` and `example-tls.p12` files to the switch tray. Replace the filenames with the actual names of the files. Use the {{<exlink url="https://docs.nvidia.com/networking/display/nvidianvosusermanualfornvlinkswitchesv25022225/cluster+manager+commands" text="NVOS cluster manager commands">}} to apply the certificates to both NMX-C and NMX-T.
+3. Copy the `example-ca.crt` and `example-tls.p12` files to the switch tray. Replace the filenames with the actual names of the files. Use the {{<exlink url="https://docs.nvidia.com/networking/display/nvidianvosusermanualfornvlinkswitchesv25022225/cluster+manager+commands" text="NVOS cluster manager commands">}} to apply the certificates to both NMX-C and NMX-T. 
+
+4. After the certificates are applied, enable the manager with the `nv action update cluster apps <app-name> manager` command.   
 
 ## Register Services
 
-Register the services by making a POST request to the `/v1/services` endpoint.
+Register the services by making a POST request to the `v1/services` endpoint. NMX-C listens on port 9370 and NMX-T listens on port 9351.
 
 {{<tabs "TabID42" >}}