SEO fixes for image file names

Author: ecfan

articles/logic-apps/logic-apps-securing-a-logic-app.md

@@ -264,19 +264,19 @@ Many triggers and actions have settings to hide inputs, outputs, or both from a
 
 1. In the [Azure portal](https://portal.azure.com), open your logic app in the Logic App Designer.
 
-   ![Open logic app in Logic App Designer](./media/logic-apps-securing-a-logic-app/sample-logic-app.png)
+   ![Open logic app in Logic App Designer](./media/logic-apps-securing-a-logic-app/open-sample-logic-app-in-designer.png)
 
 1. On the trigger or action where you want to secure data, select the ellipses (**...**) button, and then select **Settings**.
 
-   ![Open trigger or action settings](./media/logic-apps-securing-a-logic-app/open-settings.png)
+   ![Open trigger or action settings](./media/logic-apps-securing-a-logic-app/open-action-trigger-settings.png)
 
 1. Turn on either **Secure Inputs**, **Secure Outputs**, or both. When you're finished, select **Done**.
 
    ![Turn on secure inputs or outputs](./media/logic-apps-securing-a-logic-app/turn-on-secure-inputs-outputs.png)
 
    The action or trigger now shows a lock icon in the title bar.
 
-   ![Action or trigger title bar shows lock icon](./media/logic-apps-securing-a-logic-app/title-bar-lock-icon.png)
+   ![Action or trigger title bar shows lock icon](./media/logic-apps-securing-a-logic-app/lock-icon-action-trigger-title-bar.png)
 
    Tokens that represent secured outputs from previous actions also show lock icons. For example, when you select such an output from the dynamic content list to use in an action, that token shows a lock icon.
 
@@ -347,7 +347,7 @@ Here are some [considerations to review](#obfuscation-considerations) when you u
 
   When you manually turn on **Secure Inputs** in a trigger or action, Logic Apps secures these inputs in the run history. If a downstream action explicitly uses the visible outputs from that trigger or action as inputs, Logic Apps hides this downstream action's inputs in the run history, but *doesn't enable* **Secure Inputs** in this action and doesn't hide this action's outputs.
 
-  ![Secured inputs and downstream impact on most actions](./media/logic-apps-securing-a-logic-app/secure-inputs-flow.png)
+  ![Secured inputs and downstream impact on most actions](./media/logic-apps-securing-a-logic-app/secure-inputs-impact-on-downstream.png)
 
   If the Compose, Parse JSON, and Response actions explicitly use the visible outputs from the trigger or action that has the secured inputs, Logic Apps hides these actions' inputs and outputs, but *doesn't enable* these action's **Secure Inputs** setting. If a downstream action explicitly uses the hidden outputs from the Compose, Parse JSON, or Response actions as inputs, Logic Apps *doesn't hide this downstream action's inputs or outputs*.