manage-secrets changes

Author: asergaz

articles/iot-operations/secure-iot-ops/howto-manage-secrets.md

@@ -35,27 +35,29 @@ Secrets are used in asset endpoints and data flow endpoints for authentication.
 
 1. Go to the **Asset endpoints** page in the [operations experience](https://iotoperations.azure.com) web UI.
 
-1. To view the secrets list, select **Manage certificates and secrets** and then **Secrets**.
-<!-- ****TODO: Confirm this Add new secret button****** -->
-1. To add a new secret, select **Add new secret**:
+1. To add a new secret reference, select **Add reference** when creating a new asset endpoint:
 
     :::image type="content" source="media/howto-manage-secrets/use-secrets.png" alt-text="Screenshot that shows the Add from Azure Key Vault and Create new options when selecting a secret in operations experience.":::
 
     - **Create a new secret**: creates a secret reference in the Azure Key Vault and also automatically synchronizes the secret down to the edge using Secret Store extension. Use this option if you didn't create the secret you require for this scenario in the key vault beforehand. 
 
     - **Add from Azure Key Vault**: synchronizes an existing secret in key vault down to the edge if it wasn't synchronized before. Selecting this option shows you the list of secret references in the selected key vault. Use this option if you created the secret in the key vault beforehand. *Only the latest version of the secret is synced to the edge*.
 
-When you add the username and password references to the asset endpoints or data flow endpoints, you then need to give the synchronized secret a name. The secret references will be saved in the edge with this given name as one resource. In the example from the screenshot below, the username and password references are saved to the edge as *edp1secrets*.
-
-:::image type="content" source="media/howto-manage-secrets/synced-secret-name.png" alt-text="Screenshot that shows the synced secret name field when username password is selected for authentication mode in operations experience.":::
+1. When you add the username and password references to the asset endpoints or data flow endpoints, you then need to give the synchronized secret a name. The secret references will be saved in the edge with this given name as one resource. In the example from the screenshot below, the username and password references are saved to the edge as *edp1secrets*.
 
+    :::image type="content" source="media/howto-manage-secrets/synced-secret-name.png" alt-text="Screenshot that shows the synced secret name field when username password is selected for authentication mode in operations experience.":::
+    
 ## Manage synced secrets
 
-In the [operations experience](https://iotoperations.azure.com) web UI, go to the **Asset endpoints** or **Data flows** page, select **Manage certificates and secrets**, and then **Secrets**.
+In this section, we use asset endpoints as an example, the same can be applied to data flow endpoints:
+
+1. Go to the **Asset endpoints** page in the [operations experience](https://iotoperations.azure.com) web UI.
+
+1. To view the secrets list, select **Manage certificates and secrets** and then **Secrets**.
 
-*****TODO: Add screenshots for the secrets page.****
+:::image type="content" source="media/howto-manage-secrets/synced-secret-list.png" alt-text="Screenshot that shows the synced secrets list in the operations experience secrets page.":::
 
-You can use the **Secrets** page to manage synchronized secrets in your asset endpoints and data flow endpoints. Secrets page shows the list of all current synchronized secrets at the edge for the resource you are viewing. A synced secret represents one or multiple secret references, depending on the resource using it. Any operation applied to a synced secret will be applied to all secret references contained within the synced secret. 
+You can use the **Secrets** page to view synchronized secrets in your asset endpoints and data flow endpoints. Secrets page shows the list of all current synchronized secrets at the edge for the resource you are viewing. A synced secret represents one or multiple secret references, depending on the resource using it. Any operation applied to a synced secret will be applied to all secret references contained within the synced secret. 
 
 You can delete synced secrets as well in the **Secrets** page. When you delete a synced secret, it only deletes the synced secret from the edge, and doesn't delete the contained secret reference from Azure Key Vault. You must delete the certificate secret manually from the key vault.