Fix blocking issues

Author: ecfan

articles/logic-apps/create-single-tenant-workflows-azure-portal.md

@@ -377,7 +377,7 @@ In this example, the workflow runs when the **Request** trigger receives an inbo
 
    When the trigger fires, the example workflow runs and sends an email that appears similar to this example:
 
-   ![Screenshot shows Outlook email as described in the example](./media/create-single-tenant-workflows-azure-portal/workflow-app-result-email.png)
+   ![Screenshot shows Outlook email as described in the example.](./media/create-single-tenant-workflows-azure-portal/workflow-app-result-email.png)
 
 <a name="review-run-history"></a>
 

articles/logic-apps/view-workflow-status-run-history.md

@@ -34,7 +34,7 @@ Each workflow run starts with a trigger, which either fires on a schedule or wai
 
 1. On your logic app menu, select **Overview**. On the **Overview** page, select **Trigger history**.
 
-   :::image type="content" source="media/view-workflow-status-run-history/trigger-history-consumption.png" alt-text="Screenshot shows Azure portal, Consumption workflow, and Overview page with selected tab named Trigger history":::
+   :::image type="content" source="media/view-workflow-status-run-history/trigger-history-consumption.png" alt-text="Screenshot shows Azure portal, Consumption workflow, and Overview page with selected tab named Trigger history.":::
 
    Under **Trigger history**, all trigger attempts appear. Each time the trigger successfully fires, Azure Logic Apps creates an individual workflow instance and runs that instance. By default, each instance runs in parallel so that no workflow has to wait before starting a run. If your workflow triggers for multiple events or items at the same time, a trigger entry appears for each item with the same date and time.