Incorp, round 2

Author: KennedyDMSFT

articles/iot-hub/iot-hub-x509-certificate-concepts.md

@@ -117,7 +117,7 @@ Digital signing can be used to determine whether the data has been modified in t
 
 ## Next steps
 
-To learn more about the fields that make up an X.509 certificate, see [Tutorial: Understand X.509 public key certificates](tutorial-x509-certificates.md).
+To learn more about the fields that make up an X.509 certificate, see [Understand X.509 public key certificates](tutorial-x509-certificates.md).
 
 If you're already familiar with X.509 certificates, and you want to generate test versions that you can use to authenticate to your IoT hub, see the following articles:
 

articles/iot-hub/tutorial-x509-certificates.md

@@ -1,6 +1,6 @@
 ---
-title: Tutorial - Understand X.509 public key certificates for Azure IoT Hub| Microsoft Docs
-description: Tutorial - Understand X.509 public key certificates for Azure IoT Hub
+title: Understand X.509 public key certificates for Azure IoT Hub| Microsoft Docs
+description: Understand X.509 public key certificates for Azure IoT Hub
 author: kgremban
 
 ms.service: iot-hub
@@ -12,7 +12,7 @@ ms.custom: [mvc, 'Role: Cloud Development', 'Role: Data Analytics']
 #Customer intent: As a developer, I want to be able to use X.509 certificates to authenticate devices to an IoT hub. This step of the tutorial needs to introduce me to X.509 Public Key certificates.
 ---
 
-# Tutorial: Understand X.509 public key certificates
+# Understand X.509 public key certificates
 
 X.509 certificates are digital documents that represent a user, computer, service, or device. They're issued by a certification authority (CA), subordinate CA, or registration authority and contain the public key of the certificate subject. They don't contain the subject's private key, which must be stored securely. Public key certificates are documented by [RFC 5280](https://tools.ietf.org/html/rfc5280). They're digitally signed and, in general, contain the following information:
 

articles/iot-hub/tutorial-x509-introduction.md

@@ -33,7 +33,7 @@ Before starting any of the articles in this tutorial, you should be familiar wit
 
 - For an introduction to concepts that underlie the use of X.509 certificates, see [Understand public key cryptography and X.509 public key infrastructure](iot-hub-x509-certificate-concepts.md).
 
-- For a quick review of the fields that can be present in an X.509 certificate, see the [Certificate fields](tutorial-x509-certificates.md#certificate-fields) section of [Tutorial: Understand X.509 public key certificates](tutorial-x509-certificates.md).
+- For a quick review of the fields that can be present in an X.509 certificate, see the [Certificate fields](tutorial-x509-certificates.md#certificate-fields) section of [Understand X.509 public key certificates](tutorial-x509-certificates.md).
 
 ## X.509 certificate scenario paths
 
@@ -49,7 +49,7 @@ Using a CA-signed certificate chain backed by a PKI to authenticate a device pro
 
 ## Next steps
 
-To learn more about the fields that make up an X.509 certificate, see [Tutorial: Understand X.509 public key certificates](tutorial-x509-certificates.md).
+To learn more about the fields that make up an X.509 certificate, see [Understand X.509 public key certificates](tutorial-x509-certificates.md).
 
 If you're already familiar with X.509 certificates, and you want to generate test versions that you can use to authenticate to your IoT hub, see the following articles:
 

articles/iot-hub/tutorial-x509-prove-possession.md

@@ -27,7 +27,7 @@ When you upload your root certificate authority (CA) certificate or subordinate
 
 1. To automatically verify the certificate, check the box next to **Set certificate status to verified on upload**.
 
-  :::image type="content" source="media/tutorial-x509-prove-possession/skip-pop.png" alt-text="Screenshot showing how to automatically verify the certificate status on upload.":::
+   :::image type="content" source="media/tutorial-x509-prove-possession/skip-pop.png" alt-text="Screenshot showing how to automatically verify the certificate status on upload.":::
 
 1. Select **Save**.  
 
@@ -41,7 +41,7 @@ If you didn't choose to automatically verify your certificate during upload, you
 
 1. Select **Generate Verification Code** in the dialog.
 
-  :::image type="content" source="media/tutorial-x509-prove-possession/certificate-details.png" alt-text="Screenshot showing the certificate details dialog.":::
+   :::image type="content" source="media/tutorial-x509-prove-possession/certificate-details.png" alt-text="Screenshot showing the certificate details dialog.":::
 
 1. Copy the verification code to the clipboard. You must use this verification code as the certificate subject in subsequent steps. For example, if the verification code is 75B86466DA34D2B04C0C4C9557A119687ADAE7D4732BDDB3, add that as the subject of your certificate as shown in the next step.