Merge pull request #112320 from tanmaygore/patch-7

Updated customer suggestion that certs don't contain private keys

Author: PRMerger16

articles/cloud-services/cloud-services-certs-create.md

@@ -15,7 +15,7 @@ Certificates are used in Azure for cloud services ([service certificates](#what-
 
 Certificates used in Azure are x.509 v3 certificates and can be signed by another trusted certificate or they can be self-signed. A self-signed certificate is signed by its own creator, therefore it is not trusted by default. Most browsers can ignore this problem. You should only use self-signed certificates when developing and testing your cloud services. 
 
-Certificates used by Azure can contain a private or a public key. Certificates have a thumbprint that provides a means to identify them in an unambiguous way. This thumbprint is used in the Azure [configuration file](cloud-services-configure-ssl-certificate-portal.md) to identify which certificate a cloud service should use. 
+Certificates used by Azure can contains a public key. Certificates have a thumbprint that provides a means to identify them in an unambiguous way. This thumbprint is used in the Azure [configuration file](cloud-services-configure-ssl-certificate-portal.md) to identify which certificate a cloud service should use. 
 
 >[!Note]
 >Azure Cloud Services does not accept AES256-SHA256 encrypted certificate.
@@ -46,7 +46,7 @@ There is a limit of 100 management certificates per subscription. There is also
 You can use any tool available to create a self-signed certificate as long as they adhere to these settings:
 
 * An X.509 certificate.
-* Contains a private key.
+* Contains a public key.
 * Created for key exchange (.pfx file).
 * Subject name must match the domain used to access the cloud service.