Merge pull request #10530 from damabe/vdamabe-policheck1

Policheck updates | 1 (Bulk update)

Author: prmerger-automator[bot]

docs/debugger/configure-firewall-for-remote-debugging-dialog-box.md

@@ -27,10 +27,10 @@ ms.workload:
 # Configure Firewall for Remote Debugging Dialog Box
 
  [!INCLUDE [Visual Studio](~/includes/applies-to-version/vs-windows-only.md)]
-This dialog box appears when the Windows Firewall blocks the debugger from receiving information over the network. To continue remote debugging, you must open a hole in the firewall so the debugger can receive information.
+This dialog box appears when the Windows Firewall blocks the debugger from receiving information over the network. To continue remote debugging, you must open a port in the firewall so the debugger can receive information.
 
 > [!CAUTION]
-> Opening a hole in the Firewall may expose your machine to security threats that the Firewall is designed to block. Opening a hole for remote debugging unblocks ports 4020 and 4021 in Visual Studio 2015. In other versions of Visual Studio, other port numbers are used. For more information, see [Remote Debugger Port Assignments](../debugger/remote-debugger-port-assignments.md). In addition, it allows the debugger to open additional ports. For more information, see [Configure the Windows Firewall for Remote Debugging](../debugger/configure-the-windows-firewall-for-remote-debugging.md).
+> Opening a port in the Firewall may expose your machine to security threats that the Firewall is designed to block. Opening a port for remote debugging unblocks ports 4020 and 4021 in Visual Studio 2015. In other versions of Visual Studio, other port numbers are used. For more information, see [Remote Debugger Port Assignments](../debugger/remote-debugger-port-assignments.md). In addition, it allows the debugger to open additional ports. For more information, see [Configure the Windows Firewall for Remote Debugging](../debugger/configure-the-windows-firewall-for-remote-debugging.md).
 
 ## UIElement List
  **Cancel remote debugging**

docs/debugger/debug-live-azure-applications.md

@@ -109,7 +109,7 @@ If it's difficult to recreate a particular state in your app, consider using a c
 
 #### To create a conditional snappoint
 
-1. Right-click a snappoint icon (the hollow ball) and choose **Settings**.
+1. Right-click a snappoint icon (the hollow sphere) and choose **Settings**.
 
    ![Choose Settings](../debugger/media/snapshot-snappoint-settings.png)
 

docs/debugger/debug-live-azure-kubernetes.md

@@ -108,7 +108,7 @@ If it's difficult to recreate a particular state in your app, consider using a c
 
 #### To create a conditional snappoint
 
-1. Right-click a snappoint icon (the hollow ball) and choose **Settings**.
+1. Right-click a snappoint icon (the hollow sphere) and choose **Settings**.
 
    ![Choose Settings](../debugger/media/snapshot-snappoint-settings.png)
 

docs/debugger/debug-live-azure-virtual-machines-time-travel-debugging.md

@@ -74,7 +74,7 @@ In this tutorial, you:
 
    ![Screenshot that shows setting a snappoint in the code editor.](../debugger/media/time-travel-debugging-set-snappoint-settings.png)
 
-1. Right-click the snappoint hollow ball icon and choose **Actions** to show the **Snapshot Settings** window.
+1. Right-click the snappoint hollow sphere icon and choose **Actions** to show the **Snapshot Settings** window.
 
    ![Screenshot that shows the Snapshot Settings window.](../debugger/media/time-travel-debugging-set-snappoint-new.png)
 

docs/debugger/debug-live-azure-virtual-machines.md

@@ -114,7 +114,7 @@ If it's difficult to recreate a particular state in your app, consider using a c
 
 #### To create a conditional snappoint
 
-1. Right-click a snappoint icon (the hollow ball) and choose **Settings**.
+1. Right-click a snappoint icon (the hollow sphere) and choose **Settings**.
 
    ![Choose Settings](../debugger/media/snapshot-snappoint-settings.png)
 

docs/debugger/debugger-tips-and-tricks.md

@@ -50,7 +50,7 @@ If it is difficult or time-consuming to recreate a particular state in your app,
 
 #### To create a conditional breakpoint
 
-1. Right-click a breakpoint icon (the red ball) and choose **Conditions**.
+1. Right-click a breakpoint icon (the red sphere) and choose **Conditions**.
 
 2. In the **Breakpoint Settings** window, type an expression.
 

docs/workflow-designer/flowchart-activity-designer.md

@@ -30,7 +30,7 @@ The <xref:System.Activities.Statements.Flowchart> specifies a unique <xref:Syste
 
 The **Flowchart** activity designer can be found in the **Flowchart** category of the **Toolbox**, which is accessed by clicking the **Toolbox** tab on the Workflow Designer. Alternatively, select **Toolbox** from the **View** menu, or press **Ctrl**+**Alt**+**X**.
 
-The **Flowchart** activity designer can be dragged from the **Toolbox** and dropped on to the Workflow Designer surface wherever activity designers are normally placed, either as a root activity or as the child of another control flow activity. If the **Flowchart** activity designer is dropped onto a blank Workflow Designer surface, it creates a <xref:System.Activities.Statements.Flowchart> activity, which by default presents itself in an expanded view in which the start node that initiates execution is represented as a green ball. If the **Flowchart** activity designer is dropped into another control flow activity, it presents itself in a minimized view that can be expanded by double-clicking the **Flowchart** activity designer. Any activity in the **Toolbox** can be dragged directly onto the **Flowchart** activity designer, including other control flow activities.
+The **Flowchart** activity designer can be dragged from the **Toolbox** and dropped on to the Workflow Designer surface wherever activity designers are normally placed, either as a root activity or as the child of another control flow activity. If the **Flowchart** activity designer is dropped onto a blank Workflow Designer surface, it creates a <xref:System.Activities.Statements.Flowchart> activity, which by default presents itself in an expanded view in which the start node that initiates execution is represented as a green sphere. If the **Flowchart** activity designer is dropped into another control flow activity, it presents itself in a minimized view that can be expanded by double-clicking the **Flowchart** activity designer. Any activity in the **Toolbox** can be dragged directly onto the **Flowchart** activity designer, including other control flow activities.
 
 After dragging various activity designers onto the Workflow Designer canvas, the <xref:System.Activities.Activity> objects they represent can be linked together to specify the order of execution. To create a link between a source activity and a destination activity, mouse over the designer of the source activity and square handles appear on each side of it. Click one of the square handles and drag it by holding down the mouse button to one of the handles that appears in a similar manner around the destination activity when hovering over it with the mouse. Release the mouse button and a link is created between these two activities that is represented as an arrow from the source designer to the destination designer.