Clean up links from other docs

Author: ecfan

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

@@ -388,25 +388,19 @@ In this example, the workflow runs when the **Request** trigger receives an inbo
 
 ## Review workflow run history
 
-After a stateful workflow finishes running, you can view the workflow's run history, including the status for the overall run, for the trigger, and for each action along with their inputs and outputs. In the Azure portal, workflow run history and trigger history appear at the workflow level, not at the logic app resource level. For more information, see [Review workflow run history](monitor-logic-apps.md?tabs=standard#review-runs-history) and [Review trigger history](monitor-logic-apps.md?tabs=standard#review-trigger-history).
-
-For this example workflow, the workflow run history looks similar to the following sample:
-
-![Screenshot shows run details view with the status for each step in the workflow.](./media/create-single-tenant-workflows-azure-portal/review-run-details.png)
-
-![Screenshot shows inputs and outputs in the selected action named Send an email.](./media/create-single-tenant-workflows-azure-portal/review-step-inputs-outputs.png)
+After a stateful workflow finishes running, you can view the workflow's run history, including the status for the overall run, for the trigger, and for each action along with their inputs and outputs. In the Azure portal, workflow run history and trigger history appear at the workflow level, not at the logic app resource level. For more information, see [Review workflow run history](view-workflow-status-run-history.md?tabs=standard#review-run-history) and [Review trigger history](view-workflow-status-run-history.md?tabs=standard#review-trigger-history).
 
 <a name="review-trigger-history"></a>
 
 ## Review trigger history
 
-For a stateful workflow, you can review the trigger history for each run, including the trigger status along with inputs and outputs, separately from the [workflow run history](#review-run-history). In the Azure portal, trigger history and run history appear at the workflow level, not the logic app level. For more information, see [Review trigger history](monitor-logic-apps.md?tabs=standard#review-trigger-history).
+For a stateful workflow, you can review the trigger history for each run, including the trigger status along with inputs and outputs, separately from the [workflow run history](#review-run-history). In the Azure portal, trigger history and run history appear at the workflow level, not the logic app level. For more information, see [Review trigger history](view-workflow-status-run-history.md?tabs=standard#review-trigger-history).
 
 <a name="resubmit-workflow-run"></a>
 
 ## Resubmit workflow run with same inputs
 
-For an existing stateful workflow run, you can rerun the entire workflow with the same inputs that were previously used for that run. For more information, see [Rerun a workflow with same inputs](monitor-logic-apps.md?tabs=standard#resubmit-workflow-run).
+For a stateful workflow run, you can rerun the entire workflow with the same inputs that were previously used for that run. For more information, see [Rerun a workflow with same inputs](view-workflow-status-run-history.md?tabs=standard#resubmit-workflow-run).
 
 <a name="set-up-managed-identity-storage"></a>
 

articles/logic-apps/media/create-single-tenant-workflows-azure-portal/review-run-details.png

@@ -14,18 +14,12 @@ ms.date: 02/06/2025
 
 After you run a logic app workflow, you can check that workflow's run status, trigger history, workflow run history, and performance.
 
-This guide shows how to perform the following tasks:
+This guide shows you how to perform the following tasks:
 
 - [Review trigger history](#review-trigger-history).
 - [Review workflow run history](#review-run-history).
 - [Set up alerts](#add-azure-alerts) to get notifications about failures or other possible problems. For example, you can create an alert that detects "when more than five runs fail in an hour".
 
-To monitor and review the workflow run status for Standard workflows, see the following sections in [Create an example Standard logic app workflow in single-tenant Azure Logic Apps](create-single-tenant-workflows-azure-portal.md):
-
-- [Review trigger history](create-single-tenant-workflows-azure-portal.md#review-trigger-history)
-- [Review workflow run history](create-single-tenant-workflows-azure-portal.md#review-run-history).
-- [Enable or open Application Insights after deployment](create-single-tenant-workflows-azure-portal.md#enable-open-application-insights).
-
 For real-time event monitoring and richer debugging, you can set up diagnostics logging for your logic app workflow by using [Azure Monitor logs](/azure/azure-monitor/overview). This Azure service helps you monitor your cloud and on-premises environments so that you can more easily maintain their availability and performance. You can then find and view events, such as trigger events, run events, and action events. By storing this information in [Azure Monitor logs](/azure/azure-monitor/logs/data-platform-logs), you can create [log queries](/azure/azure-monitor/logs/log-query-overview) that help you find and analyze this information. You can also use this diagnostic data with other Azure services, such as Azure Storage and Azure Event Hubs. For more information, see [Monitor logic apps by using Azure Monitor](monitor-workflows-collect-diagnostic-data.md).
 
 <a name="review-trigger-history"></a>