small changes

articles/automation-analytics-with-fabric-introduction.md

@@ -38,7 +38,7 @@ The Link to Microsoft Fabric feature built into Power Platform makes all your Dy
 
 ## Get started
 
-This guide explains how to use Dataverse shortcuts within Microsoft Fabric to create powerful data analytics solutions. By the end of this guide, you have the skills to understand automation-centric data models, build sophisticated data queries in order to generate insightful reports.
+This guide explains how to use Dataverse shortcuts within Microsoft Fabric to create powerful data analytics solutions. By the end of this guide, you have the skills to understand automation-centric data models, and build sophisticated data queries to generate insightful reports.
 
 > [!NOTE]
 >
@@ -51,10 +51,14 @@ Before you continue, ensure you meet the following prerequisites:
 1. Understand data modeling, Power Automate, Dataverse, and the Fabric ecosystem.
 1. Have access to a Dataverse environment (in the same region as your Fabric capacity) with a Power Automate premium license, (ideally) existing cloud, and desktop flow runs, and System Administrator role in this environment.
 1. Ensure that you meet the [**prerequisites**](/power-apps/maker/data-platform/azure-synapse-link-view-in-fabric#prerequisites) before linking your Dataverse environment with Fabric.
-1. Follow [**these steps**](/power-apps/maker/data-platform/azure-synapse-link-view-in-fabric#link-to-microsoft-fabric) to link your Dataverse environment with Microsoft Fabric. After linking the environment, you see a Lakehouse, a semantic model, and an SQL analytics endpoint. These items are prefixed with "Dataverse," followed by your environment name and a unique environment suffix, such as `dataverse_contosousap_cds2_workspace_unq111111111111111111111111`.
+1. Follow [**these steps**](/power-apps/maker/data-platform/azure-synapse-link-view-in-fabric#link-to-microsoft-fabric) to link your Dataverse environment with Microsoft Fabric. After linking the environment, you see a Lakehouse, a semantic model, and a SQL analytics endpoint. These items are prefixed with "Dataverse," followed by your environment name and a unique environment suffix, such as `dataverse_contosousap_cds2_workspace_unq111111111111111111111111`.
+
     :::image type="content" source="media/advanced-automation-related-data-analytics-fabric/fabric-workspace-with-lakehouse.png" alt-text="Screenshot of Fabric workspace showing a Dataverse-related lakehouse and other artifacts." lightbox="media/advanced-automation-related-data-analytics-fabric/fabric-workspace-with-lakehouse.png":::
-1. (Optional) Select Lakehouse settings and rename your Lakehouse to a more meaningful name, such as "contoso_westus_accounts_payable," and provide a brief description. This change helps others quickly identify the specific automations and data being processed in the Lakehouse.
+
+1. (Optional) Select Lakehouse settings and rename your Lakehouse to a meaningful name, such as "contoso_westus_accounts_payable," and provide a brief description. This change helps others quickly identify the specific automations and data processed in the Lakehouse.
+
     :::image type="content" source="media/advanced-automation-related-data-analytics-fabric/lakehouse-renaming.png" alt-text="Screenshot of the Fabric interface with details such as name, description, location, and ownership of a lakehouse." lightbox="media/advanced-automation-related-data-analytics-fabric/lakehouse-renaming.png":::
+
 1. (Optional) Link other Dataverse environments within the same geographical region to Fabric to create cross-environment analytics solutions.
 1. (Optional) If you plan to follow the advanced section for [Desktop flow action log-level analytics](automation-analytics-with-fabric-queries.md#governance-related-query-examples-for-v2-action-logs), ensure that [**Desktop Flow Logs V2**](/power-automate/desktop-flows/configure-desktop-flow-logs#configure-desktop-flow-action-log-version) is enabled in that environment and you have existing desktop flow runs.
 

articles/automation-analytics-with-fabric-queries.md

@@ -1,5 +1,5 @@
 ---
-title: Crafting automation-related queries with Fabric
+title: Create automation-related queries with Fabric
 description: Learn how to query automation-related Dataverse data in Microsoft Fabric
 ms.topic: conceptual
 ms.date: 12/19/2024
@@ -15,27 +15,27 @@ search.audienceType:
   - enduser
 ---
 
-# Crafting automation-related queries with Fabric
+# Create automation-related queries with Fabric
 
 > [!NOTE]
 >
-> **Disclaimer:** The scenarios, query examples, and data used in this tutorial are fictional, may include errors, inefficiencies and are intended solely for demonstration purposes.
+> **Disclaimer:** The scenarios, query examples, and data used in this tutorial are fictional, may include errors, inefficiencies, and are intended solely for demonstration purposes.
 
 ## List of automation-related tables
 
 The following table lists automation-related tables frequently used for reporting and observability.
 
 | Display name | Object name       |   Purpose                                             |
 |--------------------|------------------|-------------------------------------------------------|
-| [Process](/power-apps/developer/data-platform/reference/entities/workflow) | workflow         | Contains desktop flows and solution-based cloud flows (along with other workflow types). |
-| [Flow Session](/power-apps/developer/data-platform/reference/entities/flowsession) | flowsession | Contains desktop flow run-related data such as start, durations, status, machine, robot account, parent flow context etc.     |
-| [Flow Run](/power-apps/developer/data-platform/reference/entities/flowrun) | flowrun  | Contains cloud flow run-related data such start, end, duration, parent flow context etc. |
 | [Flow Log](/power-apps/developer/data-platform/reference/entities/flowlog) | flowlog  | Contains a wide variety of logs, such as custom logs, [desktop flow action logs V2](/power-automate/desktop-flows/configure-desktop-flow-logs#configure-desktop-flow-action-log-version), [machine run queue logs](/power-automate/desktop-flows/monitor-run-details#view-queue-events), unattended self-heal requests/responses, and work queue processing logs etc. The data is stored in a [Dataverse elastic table](/power-apps/maker/data-platform/create-edit-elastic-tables), and depending on the log type, can be configured with its own [time-to-live (TTL)](/power-apps/developer/data-platform/elastic-tables#expire-data-by-using-time-to-live) setting in the [Organization table](/power-apps/developer/data-platform/reference/entities/organization#writable-columnsattributes) ([FlowLogsTtlInMinutes](/power-apps/developer/data-platform/reference/entities/organization#BKMK_FlowLogsTtlInMinutes) and [DesktopFlowQueueLogsTtlInMinutes](/power-apps/developer/data-platform/reference/entities/organization#BKMK_DesktopFlowQueueLogsTtlInMinutes)), which defines when records should be automatically deleted from the table. |
 | [Flow Machine](/power-apps/developer/data-platform/reference/entities/flowmachine) | flowmachine  | Contains machine and hosted machine-related info. |
 | [Flow Machine Group](/power-apps/developer/data-platform/reference/entities/flowmachinegroup) | flowmachinegroup | Contains machine group and hosted machine group-related info.  |
+| [Flow Run](/power-apps/developer/data-platform/reference/entities/flowrun) | flowrun  | Contains cloud flow run-related data such start, end, duration, parent flow context etc. |
+| [Flow Session](/power-apps/developer/data-platform/reference/entities/flowsession) | flowsession | Contains desktop flow run-related data such as start, durations, status, machine, robot account, parent flow context etc.     |
+| [Process](/power-apps/developer/data-platform/reference/entities/workflow) | workflow         | Contains desktop flows and solution-based cloud flows (along with other workflow types). |
+| [User](/power-apps/developer/data-platform/reference/entities/systemuser)   | systemuser | Represents the Dataverse user. |
 | [Work Queue](/power-apps/developer/data-platform/reference/entities/workqueue) | workqueue  | Represents an instance of a workflow execution.  |
 | [Work Queue Item](/power-apps/developer/data-platform/reference/entities/workqueueitem)  | workqueueitem  | Contains information about each run of a workflow.|
-| [User](/power-apps/developer/data-platform/reference/entities/systemuser)   | systemuser | Represents the Dataverse user. |
 
 ### Simplified table relationship diagram
 
@@ -94,10 +94,14 @@ Follow these steps to create a sample SQL query on the SQL Analytical Endpoint i
       | Ignored   | 12    |
 
 1. Review the query results to ensure they meet your needs.
+
     :::image type="content" source="media/advanced-automation-related-data-analytics-fabric/basic-sql-flowsession-query.png" alt-text="Screenshot of a SQL query being executed in a database management tool." lightbox="media/advanced-automation-related-data-analytics-fabric/basic-sql-flowsession-query.png":::
+
 1. (Optional) Open a Live-query with results in Excel by highlighting the SQL query and selecting **Open in Excel** in the query output section. This generates and downloads an Excel file with a Live-query to the SQL Analytics endpoint for further analysis.
+
     :::image type="content" source="media/advanced-automation-related-data-analytics-fabric/open-query-in-excel.png" alt-text="Screenshot of a SQL query being executed in a database query panel in Fabric." lightbox="media/advanced-automation-related-data-analytics-fabric/open-query-in-excel.png":::
-1. (Optional) To store the SQL query for future use, select the **Save Query**.  
+
+1. (Optional) To store the SQL query for future use, select **Save Query**.  
   
 ### Basic flow queries