fix build warnings and error syntax.

Author: KathrynEE

docs/report/powerbi/includes/query-filters-work-items.md

@@ -7,6 +7,6 @@ ms.date: 12/05/2022
 ---
 
 > [!NOTE]   
-> To determine available properties for filter or report purposes, see [Metadata reference for Azure Boards](../analytics/entity-reference-boards).  You can filter your queries or return properties using any of the `Property` values under an `EntityType` or `NavigationPropertyBinding Path` values available with an `EntitySet`. Each `EntitySet` corresponds to an `EntityType`. To learn more about the data type of each value, review the metadata provided for the corresponding `EntityType`.  
+> To determine available properties for filter or report purposes, see [Metadata reference for Azure Boards](../analytics/entity-reference-boards.md).  You can filter your queries or return properties using any of the `Property` values under an `EntityType` or `NavigationPropertyBinding Path` values available with an `EntitySet`. Each `EntitySet` corresponds to an `EntityType`. To learn more about the data type of each value, review the metadata provided for the corresponding `EntityType`.  
 
 

docs/report/powerbi/media/odatapowerbi-bugtrend-report.png

@@ -251,7 +251,7 @@ https://analytics.dev.azure.com/{organization}/{project}/_odata/V3.0-preview/Boa
 
 1. Select the **Modeling** menu, and then select **Manage Relationships**. Ensure there's a relationship between `CFD.ColumnName` and `ColumnOrder.ColumnName`. It's likely that the relationship was autodetected.
 
-	:::image type="content" source="media/reports-boards/cfd-manage-relationships-dialog.png" alt-text="Dialog for Manage Relationships showing a relationship between "CFD.ColumnName" and "ColumnOrder.ColumnName"":::
+	:::image type="content" source="media/reports-boards/cfd-manage-relationships-dialog.png" alt-text="Dialog for Manage Relationships showing a relationship between CFD.ColumnName and ColumnOrder.ColumnName":::
 
 1. In the report created above, in the **Legend**, replace `CFD.ColumnName` with `ColumnOrder.ColumnName` to **Legend**.
 

docs/report/powerbi/sample-boards-cfd.md

@@ -409,41 +409,17 @@ You can the default query label, *Query1* to something more meaningful. To do so
 
 	:::image type="content" source="media/reports-boards/rollup-table-selections.png" alt-text="Screenshot of Power BI Visualizations and Fields selections for Rollup table report. ":::
 
-1. Add the field "**DateValue**" to **X-axis**.
-	- Right-click **DateValue** and select **DateValue**, rather than **Date Hierarchy**.  
-
-1. Add the field Count to **Y-axis**.
-	- Right-click **Count** and ensure **Sum** is selected.
-
-1. Add the State to **Legend**.
-
-The example report displays.  
-
-:::image type="content" source="media/odatapowerbi-bugtrend-report.png" alt-text="Screenshot of Sample Bug trends line chart report.":::
-
-
-
-Power BI shows you the fields you can report on. 
-
-> [!NOTE]   
-> The example below assumes that columns are renamed as indicated in the corresponding images. 
-
-> [!div class="mx-imgBorder"] 
-> ![Feature rollup fields.](media/reports-boards/feature-rollup-fields.png)
-
-For a simple report, do the following steps:
-
 1. Add the following fields to **Columns** in the order indicated: 
-    - **WorkItemId**, choose **Don't summarize** to show ID if needed
-    - **WorkItemType**
-    - **Title**
-    - **State**
-    - **Count of User Stories**
-    - **Total Story Points**. 
-
-The example report displays:
-
-:::image type="content" source="media/reports-boards/feature-rollup-report.png" alt-text="Screenshot of sample Feature rollup matrix report.":::
+    - `WorkItemI`, choose **Don't summarize** to show ID if needed
+    - `WorkItemType`
+    - `Title`
+    - `State`
+    - `Count of User Stories`
+    - `Total Story Points`. 
+ 
+The example report displays.   
+ 
+:::image type="content" source="media/reports-boards/feature-rollup-report.png" alt-text="Screenshot of Sample Feature rollup matrix report.":::
 
 ## Related articles
 

docs/report/powerbi/sample-boards-rollup.md

@@ -382,16 +382,10 @@ https://analytics.dev.azure.com/{organization}/{project}/_odata/v3.0-preview/Wor
 
 ## Create the report
 
-Power BI shows you the fields you can report on. 
-
-> [!NOTE]   
-> The example below assumes that no one renamed any columns. 
-
-> [!div class="mx-imgBorder"] 
-> ![Power BI + OData - expanding an entity column](media/odatapowerbi-sprintburndown-fields.png)
-
-sprint-burndown-visualizations.png
+1. In Power BI, choose the **Line chart** report under **Visualizations** and select the fields as shown in the following image. 
 
+	:::image type="content" source="media/reports-boards/sprint-burndown-visualizations.png" alt-text="Screenshot of Power BI Visualizations and Fields selections for Sprint Burndown report. ":::
+ 
 For a simple report, do the following steps:
 
 1. Select Power BI Visualization **Clustered column chart**. 

docs/report/powerbi/sample-boards-sprintburndown.md

@@ -66,9 +66,6 @@ After closing the Advanced Editor and while remaining in the Power Query Editor,
 	:::image type="content" source="media/transform-data/descendents-expanded-columns.png" alt-text="Screenshot of Power BI expanded Descendants column. ":::
 
 
-links-target-work-item-column-expand.png
-
-
 #### Pivot Descendants.StateCategory column
 
 1. Select the 1Descendants.StateCategory1 column header to select it.
@@ -121,13 +118,12 @@ links-target-work-item-column-expand.png
 > represents its link to Work Item #3.
 
 
-<"id ="transform-data-type" />
+<a id="transform-data-type" />
 
 ## Transform a column data type 
 
-<"id ="leadtimedays-cycletimedays" />
-
-
+<a id="leadtimedays-cycletimedays" />
+ 
 ### Transform the LeadTimeDays and CycleTimeDays columns to whole Numbers
 
 The `LeadTimeDays` and `CycleTimeDays` are decimal fields. For example if **Lead Time** is 10 and 1/2 days, the value is 10.5. Since most Lead/Cycle Time reports assume that it's rounded to the nearest day, we need to convert these fields to an Integer. Making this conversion converts all values less than 1 to 0.