feedback fixes

Author: chcomley

docs/organizations/settings/work/apply-rules-to-workflow-states.md

@@ -53,29 +53,29 @@ Workflow state rules support the following scenarios:
 ::: moniker range="azure-devops"
 The following list outlines the three groups of workflow rules:
 
-1. Standard actions:
+- Standard actions:
    - Apply when a work item is created, in a selected state, or moved from one state to another.
    - Actions include setting the value of a field, making a field read-only, or making a field required.
    - You can specify one or two conditions and several actions.
 
-2. Restricting state transitions:
+- Restricting state transitions:
    - Specify one condition indicating the state a work item moved from.
    - Define actions to restrict transitions from that state to other states.
 
-3. Restricting state transitions based on user or group membership:
+- Restricting state transitions based on user or group membership:
    - Specify one condition based on user or group membership.
    - Define one action to restrict a transition from one state to another.
 ::: moniker-end
 
 ::: moniker range="<azure-devops"
 The following list outlines the two groups of workflow rules:
 
-1. Standard actions:
+- Standard actions:
    - Apply when a work item is created, in a selected state, or moved from one state to another.
    - Actions include setting the value of a field, making a field read-only, or making a field required.
    - You can specify one or two conditions and several actions.
 
-2. Restricting state transitions:
+- Restricting state transitions:
    - Specify one condition indicating the state a work item moved from.
    - Define one or more actions to restrict transitions from that state to other states.
 ::: moniker-end

docs/reference/add-portfolio-backlogs.md

@@ -45,9 +45,14 @@ By using it, the management team can set priorities and view progress of work be
 
 ![Screenshot of three portfolio backlogs enabled.](media/three-level-portfolio-backlog.png)
 
-You can add up to five levels of portfolio backlogs.
+You can add up to five portfolio backlogs, including the default Feature and Epic backlogs.
+In total, this structure gives you seven levels from the top-level portfolio backlog to task.
 Each team can [select which backlogs appear for them to work on](../organizations/settings/select-backlog-navigation-levels.md).
 
+![Diagram of five levels of portfolio backlog.](media/five-levels-portfolio-backlogs.png)
+
+To add another work item type to your backlogs or boards, see [Add work item types to backlogs and boards](add-wits-to-backlogs-and-boards.md).
+
 <a id="overview"></a>
 
 ## Process overview
@@ -242,24 +247,23 @@ You need to export the following files:
 
 [!INCLUDE [temp](../includes/witadmin-run-tool-example.md)]
 
-1. Enter the `witadmin` command, substituting your data for the arguments that are shown.
-	For example, to import a WIT:
+Enter the `witadmin` command, substituting your data for the arguments that are shown. For example, to import a WIT:
 
-    ```
-    witadmin importwitd /collection:CollectionURL /p:"ProjectName" /f:"DirectoryPath\WITDefinitionFile.xml"
-    ```
+```
+witadmin
+```
 
-    For *CollectionURL*, specify the URL of a project collection. For *ProjectName*, specify the name of a project defined within the collection.
-    You must specify the URL in the following format: `http://ServerName:Port/VirtualDirectoryName/CollectionName`.
+For `CollectionURL`, specify the URL of a project collection. For `ProjectName`, specify the name of a project defined within the collection.
+Specify the URL in the following format: `http://ServerName:Port/VirtualDirectoryName/CollectionName`.
 
-    For *DirectoryPath*, specify the path to the `WorkItem Tracking/TypeDefinitions` folder that holds the process template that you downloaded.
-    The directory path must follow this structure: `Drive:\TemplateFolder\WorkItem Tracking\TypeDefinitions`.
+For `DirectoryPath`, specify the path to the `WorkItem Tracking/TypeDefinitions` folder that holds the process template that you downloaded.
+The directory path must follow this structure: `Drive:\TemplateFolder\WorkItem Tracking\TypeDefinitions`.
 
-    For example, import the ServiceApp WIT:
+For example, import the ServiceApp WIT:
 
-    ```
-    witadmin importwitd /collection:"http://MyServer:8080/tfs/DefaultCollection" /p:MyProject /f:"DirectoryPath/ServiceApp.xml"
-    ```
+```
+witadmin importwitd /collection:"http://MyServer:8080/tfs/DefaultCollection" /p:MyProject /f:"DirectoryPath/ServiceApp.xml"
+```
 
 Use these commands to export and import categories and process configuration: 
 
@@ -277,45 +281,33 @@ witadmin exportprocessconfig /collection:"CollectionURL" /p:"ProjectName" /f:"Di
 witadmin importprocessconfig /collection:"CollectionURL" /p:"ProjectName" /f:"DirectoryPath/ProcessConfiguration.xml"
 ```
 
+## FAQs
 
-## Related content
-
-You can add up to five portfolio backlogs, including the default Feature and Epic backlogs.
-In total, this structure gives you seven levels from the top-level portfolio backlog to task.
-
-![Diagram of five levels of portfolio backlog.](media/five-levels-portfolio-backlogs.png)
-
-To add another work item type to your backlogs or boards, see [Add work item types to backlogs and boards](add-wits-to-backlogs-and-boards.md).
-
-- [All WITD XML elements reference](/previous-versions/azure/devops/reference/xml/all-witd-xml-elements-reference)
-- [Process configuration XML element reference](xml/process-configuration-xml-element.md)
-- [Import, export, and manage work item types](witadmin/witadmin-import-export-manage-wits.md)
-- [Import and export categories](/previous-versions/azure/devops/reference/witadmin/witadmin-import-export-categories)
-- [Import and export process configuration](witadmin/witadmin-import-export-process-configuration.md)
-- [Customize your work tracking experience](customize-work.md)
-
-### Portfolio backlog hierarchy
+### Q: What controls the hierarchy among portfolio backlogs?
 
-What controls the hierarchy among portfolio backlogs?
-
-The process configuration determines the hierarchy through the assignment of parent categories to portfolio backlog categories.
+A: The process configuration determines the hierarchy through the assignment of parent categories to portfolio backlog categories.
 Only parent-child relationships are supported.
 The uppermost category within the hierarchy doesn't contain a parent assignment.
 
-### Portfolio backlogs and WIT categories
-
-Can I define more than one WIT in a category that I use for a portfolio backlog?
+### Q: Can I define more than one WIT in a category that I use for a portfolio backlog?
 
-Yes.
+A: Yes.
 For example, you can add Goal and Initiative WITs to a portfolio backlog category.
 The main restriction is to not add the same WIT to two different categories that you assign to one of the following sections for process configuration: a ```PortfolioBacklog```, ```RequirementBacklog```, or ```TaskBacklog```.
 
-### Nesting of backlog items
+### Q: Can you nest backlog items in addition to using portfolio backlogs?
 
-**Can you nest backlog items in addition to using portfolio backlogs?**
-
-While you can nest backlog items, nesting isn't recommended.
+A: While you can nest backlog items, nesting isn't recommended.
 Drag-and-drop linking of nested backlog items isn't supported.
 Instead, use [mapping of backlog items to portfolio items](../boards/backlogs/organize-backlog.md).
 
 For examples of how hierarchically linked items that belong to the Requirements Category appear on the backlogs and boards, see [How backlogs and boards display hierarchical (nested) items](../boards/backlogs/resolve-backlog-reorder-issues.md).
+
+## Related content
+
+- [All WITD XML elements reference](/previous-versions/azure/devops/reference/xml/all-witd-xml-elements-reference)
+- [Process configuration XML element reference](xml/process-configuration-xml-element.md)
+- [Import, export, and manage work item types](witadmin/witadmin-import-export-manage-wits.md)
+- [Import and export categories](/previous-versions/azure/devops/reference/witadmin/witadmin-import-export-categories)
+- [Import and export process configuration](witadmin/witadmin-import-export-process-configuration.md)
+- [Customize your work tracking experience](customize-work.md)

docs/reference/customize-wit-form.md

@@ -61,7 +61,7 @@ To make the indicated customizations, see the following topics:
 
 ## Import and export definition files (On-premises XML process)
 
-1. If you don't have administration permissions for your project, [get them](../organizations/security/change-organization-collection-level-permissions.md).  
+If you don't have administration permissions for your project, [get them](../organizations/security/change-organization-collection-level-permissions.md).  
   
 1. Open a Command Prompt window by following the instructions in [witAdmin: Customize and manage objects for tracking work](witadmin/witadmin-customize-and-manage-objects-for-tracking-work.md#run-witadmin-tool). 
 
@@ -71,23 +71,23 @@ To make the indicated customizations, see the following topics:
    %programfiles(x86)%\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer 
    ```  
 
-1. Export the WIT definition file where you want to modify or add a field. Specify the name of the WIT and a name for the file.  
+2. Export the WIT definition file where you want to modify or add a field. Specify the name of the WIT and a name for the file.  
 
     ```
     witadmin exportwitd /collection:CollectionURL /p:ProjectName /n:TypeName /f:"DirectoryPath/FileName.xml"  
     ```
 
    An example of a <em>CollectionURL</em> for an organization is https:\//dev.azure.com/*OrganizationName*.
 
-1. Edit the file. For details, see [WebLayout XML elements](/previous-versions/azure/devops/reference/xml/weblayout-xml-elements).  
+3. Edit the file. For details, see [WebLayout XML elements](/previous-versions/azure/devops/reference/xml/weblayout-xml-elements).  
 
-1. Import the WIT definition file.  
+4. Import the WIT definition file.  
 
     ```
     witadmin importwitd /collection:CollectionURL /p:ProjectName /f:"DirectoryPath/FileName.xml"  
     ```
 
-1. Open either the web portal to view the changes. If the client is already open, refresh the page. 
+5. Open either the web portal to view the changes. If the client is already open, refresh the page. 
 
    The latest updates are downloaded from the server, including the changes that you just imported. Wait several seconds until the refresh completes.