howto guides remove screenshots

Author: v-krishnag

articles/iot-central/core/how-to-connect-devices-x509.md

@@ -93,7 +93,7 @@ Make a note of the location of these files. You need it later.
 
 1. Open the enrollment group you created and select **Manage Primary**.
 
-1. Select file option to upload the root certificate file called _mytestrootcert_cert.pem_ that you generated previously
+1. Select file option to upload the root certificate file called _mytestrootcert_cert.pem_ that you generated previously.
 
 1. To complete the verification, generate the verification code, copy it, and then use it to create an X.509 verification certificate at the command prompt:
 
@@ -241,7 +241,7 @@ These commands produce the following device certificates:
 
 1. Open the device you created and select **Connect**.
 
-1. Select **Individual Enrollments** as the **Connect Method** and **Certificates (X.509)** as the mechanism
+1. Select **Individual Enrollments** as the **Connect Method** and **Certificates (X.509)** as the mechanism.
 
 1. Select file option under primary and upload the certificate file called _mytestselfcertprimary_cert.pem_ that you generated previously.
 

articles/iot-central/core/howto-manage-devices-in-bulk.md

@@ -41,7 +41,7 @@ The following example shows you how to create and run a job to set the light thr
 
     The cancellation threshold lets you automatically cancel a job if the number of errors exceeds your set limit. The threshold can apply to all the devices in the job, or to individual batches.
 
-1. Select **Next** to move to the **Schedule** page. The **Schedule** page lets you enable a schedule to run the job in the future:
+1. Select **Next** to move to the **Schedule** page. The **Schedule** page lets you enable a schedule to run the job in the future.
 
     Choose a recurrence option for the schedule. You can set up a job to run:
 

articles/iot-central/core/howto-use-properties.md

@@ -220,7 +220,7 @@ For more information on device twins, see [Configure your devices from a back-en
 
 When the operator sets a writable property in the Azure IoT Central application, the application uses a device twin desired property to send the value to the device. The device then responds by using a device twin reported property. When Azure IoT Central receives the reported property value, it updates the property view with a status of **Accepted**.
 
-The following view shows the writable properties. When you enter the value and select **Save**, the initial status is **Pending**. When the device accepts the change, the status changes to **Accepted**.
+When you enter the value and select **Save**, the initial status is **Pending**. When the device accepts the change, the status changes to **Accepted**.
 
 ## Use properties on unassigned devices