replaced disallowed HTML tags, <li> and <code>

Author: chcomley

docs/boards/queries/query-by-date-or-current-iteration.md

@@ -198,7 +198,7 @@ Not all fields are valid for all work item types. Jump to [date fields](#date_fi
 ---
 :::row:::
    :::column span="1":::
-      Items closed during the current sprint (the <code><xref href="CurrentIteration" data-throw-if-not-resolved="False" data-raw-source="@CurrentIteration"></xref></code> macro references the sprint defined for the current team context)
+      Items closed during the current sprint (the `<xref href="CurrentIteration" data-throw-if-not-resolved="False" data-raw-source="@CurrentIteration"></xref>` macro references the sprint defined for the current team context)
    :::column-end::: 
    :::column span="2":::
       :::image type="content" source="media/q-by-done-current-iteration.png" alt-text="Screenshot of query editor, Clause for items closed during the current sprint.":::  

docs/boards/queries/query-field-value.md

@@ -49,7 +49,7 @@ You can use the comparison field operators&mdash;`=[Field], <>[Field], >[Field],
    :::column span="1":::
 
    `Created By <>[Field] Closed By`  
-   State = Closed</code>  
+   State = Closed`  
    :::column-end:::
 :::row-end:::
 :::row:::
@@ -69,7 +69,7 @@ You can use the comparison field operators&mdash;`=[Field], <>[Field], >[Field],
    :::column span="1":::
 
    `Target Date <=[Field] Closed Date`  
-   State = Closed</code>  
+   State = Closed`  
    :::column-end:::
 :::row-end:::
 

docs/boards/queries/query-operators-variables.md

@@ -577,7 +577,7 @@ You can use the macros described in the following table to filter your queries b
       **[Any]** 
    :::column-end:::
    :::column span="3":::
-      Use with the **Work Item Type** or **State** fields to search across all work item types or across all states. For example, <code>Work Item Type=[Any]</code> won't place any filters based on the work item type.
+      Use with the **Work Item Type** or **State** fields to search across all work item types or across all states. For example, `Work Item Type=[Any]` won't place any filters based on the work item type.
    :::column-end:::
 :::row-end:::
 ---
@@ -616,7 +616,7 @@ You can use the macros described in the following table to filter your queries b
       **@Me** 
    :::column-end:::
    :::column span="3":::
-      Use with an identity or user account field to automatically search for items associated with your user or account name. For example, you can find work items that you opened with the clause <code>Created By=@Me</code>. For more examples, see [Query by assignment, workflow, or Kanban board changes](query-by-workflow-changes.md).
+      Use with an identity or user account field to automatically search for items associated with your user or account name. For example, you can find work items that you opened with the clause `Created By=@Me`. For more examples, see [Query by assignment, workflow, or Kanban board changes](query-by-workflow-changes.md).
    :::column-end:::
 :::row-end:::
 ---
@@ -634,7 +634,7 @@ You can use the macros described in the following table to filter your queries b
       **@Project** 
    :::column-end:::
    :::column span="3":::
-      Use with the **Team Project** field to filter for work items in other projects. For example, you can find all the work items in the currently selected project with the clause <code>Team Project=@Project</code>. The system automatically defaults to filtering based on the current project. For more information, see [Define a query, Query across projects](using-queries.md#across-projects). 
+      Use with the **Team Project** field to filter for work items in other projects. For example, you can find all the work items in the currently selected project with the clause `Team Project=@Project`. The system automatically defaults to filtering based on the current project. For more information, see [Define a query, Query across projects](using-queries.md#across-projects). 
    :::column-end:::
 :::row-end:::
 ---
@@ -661,7 +661,7 @@ You can use the macros described in the following table to filter your queries b
       **@StartOfDay** <sup>2</sup> 
    :::column-end:::
    :::column span="3":::
-      Use with a <code>DateTime</code> field to filter for work items that relate to the current date or with a plus/minus offset. For example, you can find all items closed in the last week with the clause <code>Closed Date&gt;=@StartOfDay-7</code>. For more examples, see [Query by date or current iteration](query-by-date-or-current-iteration.md).
+      Use with a `DateTime` field to filter for work items that relate to the current date or with a plus/minus offset. For example, you can find all items closed in the last week with the clause `Closed Date&gt;=@StartOfDay-7`. For more examples, see [Query by date or current iteration](query-by-date-or-current-iteration.md).
    :::column-end:::
 :::row-end:::
 ---
@@ -670,7 +670,7 @@ You can use the macros described in the following table to filter your queries b
       **@StartOfMonth** <sup>2</sup> 
    :::column-end:::
    :::column span="3":::
-      Use with a <code>DateTime</code> field to filter for work items that relate to the current month or with a plus/minus offset. For example, you can find all items created in the last three months with the clause <code>Created Date&gt;=@StartOfMonth-3</code>. For more examples, see [Query by date or current iteration](query-by-date-or-current-iteration.md).
+      Use with a `DateTime` field to filter for work items that relate to the current month or with a plus/minus offset. For example, you can find all items created in the last three months with the clause `Created Date&gt;=@StartOfMonth-3`. For more examples, see [Query by date or current iteration](query-by-date-or-current-iteration.md).
    :::column-end:::
 :::row-end:::
 ---
@@ -679,7 +679,7 @@ You can use the macros described in the following table to filter your queries b
       **@StartOfWeek** <sup>2</sup> 
    :::column-end:::
    :::column span="3":::
-      Use with a <code>DateTime</code> field to filter for work items that relate to the current week or with a plus/minus offset. For example, you can find all items changed in the last two weeks with the clause <code>Changed Date&gt;=@StartOfWeek-2</code>. For more examples, see [Query by date or current iteration](query-by-date-or-current-iteration.md).
+      Use with a `DateTime` field to filter for work items that relate to the current week or with a plus/minus offset. For example, you can find all items changed in the last two weeks with the clause `Changed Date&gt;=@StartOfWeek-2`. For more examples, see [Query by date or current iteration](query-by-date-or-current-iteration.md).
    :::column-end:::
 :::row-end:::
 ---
@@ -688,7 +688,7 @@ You can use the macros described in the following table to filter your queries b
       **@StartOfYear** <sup>2</sup> 
    :::column-end:::
    :::column span="3":::
-      Use with a <code>DateTime</code> field to filter for work items that relate to the current year or with a plus/minus offset. For example, you can find all features that have a Target Date scheduled within the current year with the clause <code>Target Date&gt;=@StartOfYear</code>. For more examples, see [Query by date or current iteration](query-by-date-or-current-iteration.md).
+      Use with a `DateTime` field to filter for work items that relate to the current year or with a plus/minus offset. For example, you can find all features that have a Target Date scheduled within the current year with the clause `Target Date&gt;=@StartOfYear`. For more examples, see [Query by date or current iteration](query-by-date-or-current-iteration.md).
    :::column-end:::
 :::row-end:::
 ---
@@ -697,7 +697,7 @@ You can use the macros described in the following table to filter your queries b
       **@TeamAreas**  
    :::column-end:::
    :::column span="3":::
-      Only use with the **Area Path** field to filter for work items whose area path corresponds to one assigned to a specific team. Requires you use the **=** operator. For example, you can find all items assigned to the area paths assigned to the Web team with the clause <code>Area Path=@TeamAreas [Fabrikam Fiber]\Web</code>. For more examples, see [Query by area or iteration path](query-by-area-iteration-path.md).  
+      Only use with the **Area Path** field to filter for work items whose area path corresponds to one assigned to a specific team. Requires you use the **=** operator. For example, you can find all items assigned to the area paths assigned to the Web team with the clause `Area Path=@TeamAreas [Fabrikam Fiber]\Web`. For more examples, see [Query by area or iteration path](query-by-area-iteration-path.md).  
       The **@TeamAreas** macro is supported for Azure DevOps Server 2019 and later versions, and only when run from the web portal.
    :::column-end:::
 :::row-end:::
@@ -707,7 +707,7 @@ You can use the macros described in the following table to filter your queries b
       **@Today**
    :::column-end:::
    :::column span="3":::
-      Use with a <code>DateTime</code> field to filter for work items that relate to the current date or to an earlier date. You can also modify the **@Today** macro by subtracting days. For example, you can find all items created in the last week with the clause <code>Created Date&gt;=@Today-7</code>. For more examples, see [Query by date or current iteration](query-by-date-or-current-iteration.md).
+      Use with a `DateTime` field to filter for work items that relate to the current date or to an earlier date. You can also modify the **@Today** macro by subtracting days. For example, you can find all items created in the last week with the clause `Created Date&gt;=@Today-7`. For more examples, see [Query by date or current iteration](query-by-date-or-current-iteration.md).
    :::column-end:::
 :::row-end:::
 ---

docs/boards/work-items/set-work-item-experience-vs.md

@@ -22,7 +22,7 @@ Each view supports the following tasks:
 
 | **Default experience**|**Legacy experience**|
 |-----------------------|---------------------| 
-|- [View and add work items](./view-add-work-items.md)|- [Add work items](../backlogs/add-work-items.md)<br/>- [Use the query editor to list and manage queries](../queries/using-queries.md)<br/>- [Organize query folders and set query permissions](../queries/set-query-permissions.md)<br/>- [Open query in Excel](../backlogs/office/bulk-add-modify-work-items-excel.md)<br/>- [Send email of query results list using Outlook](../work-items/email-work-items.md)<br/>- [Create reports from query in Excel](/previous-versions/azure/devops/report/admin/create-status-and-trend-excel-reports)<br/>(on-premises Azure DevOps Server only)</li></ul>|
+|- [View and add work items](./view-add-work-items.md)|- [Add work items](../backlogs/add-work-items.md)<br/>- [Use the query editor to list and manage queries](../queries/using-queries.md)<br/>- [Organize query folders and set query permissions](../queries/set-query-permissions.md)<br/>- [Open query in Excel](../backlogs/office/bulk-add-modify-work-items-excel.md)<br/>- [Send email of query results list using Outlook](../work-items/email-work-items.md)<br/>- [Create reports from query in Excel](/previous-versions/azure/devops/report/admin/create-status-and-trend-excel-reports)<br/>(on-premises Azure DevOps Server only)</br></ul>|
 
 > [!NOTE]
 > If you want to quickly access a list of work items based on their assignment to you, following, mentioned, or recent updates; then use the new default experience. However, if you rely on accessing queries from Team Explorer, then we recommend that you set your Landing page to the legacy option. 

docs/extend/develop/add-dashboard-widget.md

@@ -111,9 +111,9 @@ Add the below HTML in `hello-world.html`. We add the mandatory reference to `VSS
 
 ### Step 3: Your JavaScript
 
-We use JavaScript to render content in the widget. In this article, we wrap all of our JavaScript code inside a <code>&lt;script&gt;</code> element in the HTML file. You can choose to have this code in a separate JavaScript file and refer it in the HTML file.
+We use JavaScript to render content in the widget. In this article, we wrap all of our JavaScript code inside a `&lt;script&gt;` element in the HTML file. You can choose to have this code in a separate JavaScript file and refer it in the HTML file.
 The code renders the content. This JavaScript code also initializes the VSS SDK, maps the code for your widget to your widget name, and notifies the extension framework of widget successes or failures.
-In our case, below is the code that would print &quot;Hello World&quot; in the widget. Add this <code>script</code> element in the <code>head</code> of the HTML.
+In our case, below is the code that would print &quot;Hello World&quot; in the widget. Add this `script` element in the `head` of the HTML.
 
 ```html    
     <script type="text/javascript">
@@ -167,7 +167,7 @@ The `vss-extension.json` should always be at the root of the folder (in this gui
 
 <a id="image" />
 
-### Step 4: Your extension&#39;s logo: <code>logo.png</code>
+### Step 4: Your extension&#39;s logo: `logo.png`
 
 Your logo is displayed in the Marketplace, and in the widget catalog once a user installs your extension.
 
@@ -177,7 +177,7 @@ To support TFS 2015 Update 3, you need an additional image that is 330 px x 160
 
 You can name these images however you want as long as the extension manifest in the next step is updated with the names you use.
 
-### Step 5: Your extension&#39;s manifest: <code>vss-extension.json</code>
+### Step 5: Your extension&#39;s manifest: `vss-extension.json`
 
 * ***Every*** extension must have an extension manifest file
 * Read the [extension manifest reference](./manifest.md)
@@ -381,8 +381,8 @@ Copy the file `hello-world.html` from the previous example, and rename the copy
 ```
 
 <br>
-Add a new <code>div</code> element right below the <code>h2</code> to hold the query information.
-Update the name of the widget from <code>HelloWorldWidget</code> to <code>HelloWorldWidget2</code> in the line where you call <code>VSS.register</code>.
+Add a new `div` element right below the `h2` to hold the query information.
+Update the name of the widget from `HelloWorldWidget` to `HelloWorldWidget2` in the line where you call `VSS.register`.
 This allows the framework to uniquely identify the widget within the extension.
 
 ```html
@@ -502,9 +502,9 @@ Replace the `// Do something with the query` comment with the below:
 ```JavaScript
     // Create a list with query details                                
     var $list = $('<ul>');                                
-    $list.append($('<li>').text("Query Id: " + query.id));
-    $list.append($('<li>').text("Query Name: " + query.name));
-    $list.append($('<li>').text("Created By: " + ( query.createdBy? query.createdBy.displayName: "<unknown>" ) ) );                                                            
+    $list.append($('- ').text("Query Id: " + query.id));
+    $list.append($('- ').text("Query Name: " + query.name));
+    $list.append($('- ').text("Created By: " + ( query.createdBy? query.createdBy.displayName: "<unknown>" ) ) );                                                            
 
     // Append the list to the query-info-container
     var $container = $('#query-info-container');
@@ -537,9 +537,9 @@ Your final `hello-world2.html` is as follows:
                             .then(function (query) {
                                 // Create a list with query details                                
                                 var $list = $('<ul>');
-                                $list.append($('<li>').text("Query ID: " + query.id));
-                                $list.append($('<li>').text("Query Name: " + query.name));
-                                $list.append($('<li>').text("Created By: " + (query.createdBy ? query.createdBy.displayName: "<unknown>") ));
+                                $list.append($('- ').text("Query ID: " + query.id));
+                                $list.append($('- ').text("Query Name: " + query.name));
+                                $list.append($('- ').text("Created By: " + (query.createdBy ? query.createdBy.displayName: "<unknown>") ));
 
                                 // Append the list to the query-info-container
                                 var $container = $('#query-info-container');
@@ -679,7 +679,7 @@ Your folder now looks like the following example:
 ```
 
 <br>
-Add the below HTML in <code>configuration.html</code>. We basically add the mandatory reference to the <code>VSS.SDK.min.js</code> file and a <code>select</code> element for the dropdown to select a query from a preset list.
+Add the below HTML in `configuration.html`. We basically add the mandatory reference to the `VSS.SDK.min.js` file and a `select` element for the dropdown to select a query from a preset list.
 
 ```html
     <!DOCTYPE html>
@@ -876,8 +876,8 @@ return {
 ```
 
 <br>
-The hard-coded query path in <code>getQueryInfo</code> should be replaced with the configured query path, which can be extracted from the parameter <code>widgetSettings</code> that is passed to the method.
-Add the below in the very beginning of the <code>getQueryInfo</code> method and replace the hard-coded querypath with <code>settings.queryPath</code>.
+The hard-coded query path in `getQueryInfo` should be replaced with the configured query path, which can be extracted from the parameter `widgetSettings` that is passed to the method.
+Add the below in the very beginning of the `getQueryInfo` method and replace the hard-coded querypath with `settings.queryPath`.
 
 ```JavaScript
 var settings = JSON.parse(widgetSettings.customSettings.data);