Update suse-public-cloud-connectivity-registration-issues.md

Author: przlplx

support/azure/virtual-machines/linux/suse-public-cloud-connectivity-registration-issues.md

@@ -144,7 +144,7 @@ The output doesn't show the server certificate or SSL session.
 
 This scenario usually occurs when the command crosses a Network Virtual Appliance (NVA) that performs SSL packet inspection. This inspection causes the NVA to inject its own SSL certificate into the encrypted session.
 
-Because SUSE uses certificate pinning, another injected SSL certificate can break the pinning operation. If the pinning is broken, the SUSE repository will deny the connection.
+Because SUSE uses certificate pinning, another injected SSL certificate can break the pinning operation. If the pinning is broken, the SUSE repository denies the connection.
 
 ### Resolution
 
@@ -200,17 +200,17 @@ sudo tail /var/log/cloudregister
 2025-01-29 20:20:06,917 ERROR:No response from: [('23.101.171.119', '2603:1030:603::2e9'), ('23.101.164.199', '2603:1030:603::625'), ('23.96.231.74', '2603:1030:603::2e6')]
 ```
 
-The output indicates that a connectivity error exists. However, this isn't true. This indication occurs because the error handling process in the registration scripts doesn't show the certificate errors from the old libraries.
+The output indicates that a connectivity error exists. However, this indication isn't true. It occurs because the error handling process in the registration scripts doesn't show the certificate errors from the old libraries.
 
-The script output might also mistakenly indicate that a certificate for one of the SMT IPs that's displayed in the `sudo tail /var/log/cloudregister` command output can't be found. This is also a library issue, not an issue that affects the CA list on the VM.
+The script output might also mistakenly indicate that a certificate for one of the SMT IPs that's displayed in the `sudo tail /var/log/cloudregister` command output can't be found. This issue is also a library issue, not one that affects the CA list on the VM.
 
 ### Cause
 
 If instances aren't regularly updated, they can become incompatible with our update infrastructure API. This situation causes failure of the repositories that are required to update an instance.
 
 ### Resolution
 
-1. Create a PAYG instance by using the same OS as the that has broken repos.
+1. Create a PAYG instance by using the same OS as the one that has the broken repos.
 2. Create a temporary directory:
 
     ```bash
@@ -313,7 +313,7 @@ Error: Activating SLES_SAP 12.5 x86_64 ... Error: Registration server returned '
 
 ### Cause
 
-The VMs can't to connect to SUSE repositories because of outdated SUSE Public Cloud packages.
+The VMs can't connect to SUSE repositories because of outdated SUSE Public Cloud packages.
 
 ### Resolution