MSFT style fixes

Author: lindalu-MSFT

Language/Concepts/Forms/creating-forms-and-dialog-boxes-with-right-to-left-extensions.md

@@ -12,7 +12,7 @@ ms.localizationpriority: medium
 
 # Creating forms and dialog boxes with right-to-left extensions
 
-You can use the Visual Basic Editor and Microsoft Forms version 2.0 in all Microsoft Office 2000 applications to create forms and dialog boxes. Bidirectional extensions to the editor and Microsoft Forms 2.0 are provided in Office 2000 for right-to-left, left-to-right, and mixed-text usage. For a general overview of the standard tools, see the "Forms" topic in Help for the application that you are working in.
+Use the Visual Basic Editor and Microsoft Forms version 2.0 in all Microsoft Office 2000 applications to create forms and dialog boxes. Bidirectional extensions to the editor and Microsoft Forms 2.0 are provided in Office 2000 for right-to-left, left-to-right, and mixed-text usage. For a general overview of the standard tools, see the "Forms" topic in Help for the application that you are working in.
 
 Three Microsoft Forms 2.0 properties are generally used to add bidirectional characteristics to forms and dialog boxes. These properties are listed and described in the following table.
 

Language/Concepts/Forms/passwordchar-property.md

@@ -29,7 +29,7 @@ The **PasswordChar** property syntax has these parts:
 
 ## Remarks
 
-You can use the **PasswordChar** property to protect sensitive information, such as passwords or security codes. The value of **PasswordChar** is the character that appears in a control instead of the actual characters that the user types. If you don't specify a character, the control displays the characters that the user types.
+Use the **PasswordChar** property to protect sensitive information, such as passwords or security codes. The value of **PasswordChar** is the character that appears in a control instead of the actual characters that the user types. If you don't specify a character, the control displays the characters that the user types.
 
 ## See also
 

Language/Concepts/Forms/ways-to-change-the-appearance-of-a-control.md

@@ -23,7 +23,7 @@ Microsoft Forms includes several properties that let you define the appearance o
 
 **BackColor** and **BackStyle** apply to the control's background. The background is the area within the control's boundaries, such as the area surrounding the text in a control, but not the control's border. **BackColor** determines the [background color](../../Glossary/glossary-vba.md#background-color). **BackStyle** determines whether the background is [transparent](../../Glossary/glossary-vba.md#transparent). A transparent control background is useful if your application design includes a picture as the main background and you want to see that picture through the control.
 
-**BorderColor**, **BorderStyle**, and **SpecialEffect** apply to the control's border. You can use **BorderStyle** or **SpecialEffect** to choose a type of border. Only one of these two properties can be used at a time. When you assign a value to one of these properties, the system sets the other property to **None**. 
+**BorderColor**, **BorderStyle**, and **SpecialEffect** apply to the control's border. Use **BorderStyle** or **SpecialEffect** to choose a type of border. Only one of these two properties can be used at a time. When you assign a value to one of these properties, the system sets the other property to **None**. 
 
 - **SpecialEffect** lets you choose one of several border styles, but only lets you use [system colors](../../Glossary/glossary-vba.md#system-colors) for the border. 
 

Language/Concepts/Forms/ways-to-create-an-option-group.md

@@ -23,7 +23,7 @@ If you want more than one option group on the form, there are two ways to create
 The first method is recommended over the second because it reduces the number of controls required in the application. This reduces the disk space required for your application and can improve the performance of your application as well.
 
 > [!NOTE] 
-> A **[TabStrip](../../reference/user-interface-help/tabstrip-control.md)** is not a container. Option buttons in the **TabStrip** are included in the form's option group. You can use **GroupName** to create an option group from buttons in a **TabStrip**.
+> A **[TabStrip](../../reference/user-interface-help/tabstrip-control.md)** is not a container. Option buttons in the **TabStrip** are included in the form's option group. Use **GroupName** to create an option group from buttons in a **TabStrip**.
 
 ## See also
 

Language/Concepts/Forms/ways-to-protect-sensitive-information.md

@@ -20,7 +20,7 @@ Many applications use data that should be available only to certain users. Here
 
 - Disable the control when unauthorized users run the application. The **[Enabled](../../reference/user-interface-help/enabled-property-microsoft-forms.md)** property determines when a control is disabled. 
 
-- Require a password for access to the application or a specific control. You can use [placeholders](../../Glossary/glossary-vba.md#placeholder) as the user types each character. The **[PasswordChar]((passwordchar-property.md)** property defines placeholder characters. 
+- Require a password for access to the application or a specific control. Use [placeholders](../../Glossary/glossary-vba.md#placeholder) as the user types each character. The **[PasswordChar]((passwordchar-property.md)** property defines placeholder characters. 
 
 > [!NOTE] 
 > Using passwords or any other techniques listed can improve the security of your application, but does not guarantee the prevention of unauthorized access to your data.

Language/Concepts/Getting-Started/avoiding-naming-conflicts.md

@@ -29,7 +29,7 @@ Most naming conflicts can be resolved by preceding each identifier with a qualif
 YourProject.YourModule.YourSub MyProject.MyModule.MyVar
 ```
 
-The preceding code calls the **Sub** procedure `YourSub` and passes `MyVar` as an argument. You can use any combination of qualifiers to differentiate identical identifiers.
+The preceding code calls the **Sub** procedure `YourSub` and passes `MyVar` as an argument. Use any combination of qualifiers to differentiate identical identifiers.
 
 Visual Basic matches each reference to an identifier with the "closest" declaration of a matching identifier. For example, if  `MyID` is declared **Public** in two modules in a project (`Mod1` and `Mod2`), you can specify the `MyID` declared in `Mod2` without qualification from within `Mod2`, but you must qualify it as `Mod2.MyID` to specify it in `Mod1`. 
 

Language/Concepts/Getting-Started/calling-procedures-with-the-same-name.md

@@ -35,7 +35,7 @@ End Sub
 
 
 > [!TIP] 
-> - If you rename a module or project, be sure to change the module or project name wherever it appears in calling [statements](../../Glossary/vbe-glossary.md#statement); otherwise, Visual Basic will not be able to find the called procedure. You can use the **Replace** command on the **[Edit](../../reference/user-interface-help/edit-menu.md)** menu to find and replace text in a module.
+> - If you rename a module or project, be sure to change the module or project name wherever it appears in calling [statements](../../Glossary/vbe-glossary.md#statement); otherwise, Visual Basic will not be able to find the called procedure. Use the **Replace** command on the **[Edit](../../reference/user-interface-help/edit-menu.md)** menu to find and replace text in a module.
 > - To avoid naming conflicts among referenced projects, give your procedures unique names so you can call a procedure without specifying a project or module.
     
 ## See also

Language/Concepts/Getting-Started/calling-sub-and-function-procedures.md

@@ -14,7 +14,7 @@ ms.localizationpriority: high
 
 To call a **[Sub](../../reference/user-interface-help/sub-statement.md)** procedure from another [procedure](../../Glossary/vbe-glossary.md#procedure), type the name of the procedure and include values for any required [arguments](../../Glossary/vbe-glossary.md#argument). The **[Call](../../reference/user-interface-help/call-statement.md)** statement is not required, but if you use it, you must enclose any arguments in parentheses.
 
-You can use a **Sub** procedure to organize other procedures so they are easier to understand and debug. In the following example, the **Sub** procedure `Main` calls the **Sub** procedure `MultiBeep`, passing the value 56 for its argument. 
+Use a **Sub** procedure to organize other procedures so they are easier to understand and debug. In the following example, the **Sub** procedure `Main` calls the **Sub** procedure `MultiBeep`, passing the value 56 for its argument. 
 
 After `MultiBeep` runs, control returns to `Main`, and `Main` calls the **Sub** procedure `Message`. `Message` displays a message box; when the user clicks **OK**, control returns to `Main`, and `Main` finishes.
 

Language/Concepts/Getting-Started/declaring-arrays.md

@@ -65,9 +65,9 @@ Dim sngArray() As Single
 ```
 
 > [!NOTE] 
-> You can use the **[ReDim](../../reference/user-interface-help/redim-statement.md)** statement to declare an array implicitly within a procedure. Be careful not to misspell the name of the array when you use the **ReDim** statement. Even if the **[Option Explicit](../../reference/user-interface-help/option-explicit-statement.md)** statement is included in the module, a second array will be created.
+> Use the **[ReDim](../../reference/user-interface-help/redim-statement.md)** statement to declare an array implicitly within a procedure. Be careful not to misspell the name of the array when you use the **ReDim** statement. Even if the **[Option Explicit](../../reference/user-interface-help/option-explicit-statement.md)** statement is included in the module, a second array will be created.
 
-In a procedure within the array's [scope](../../Glossary/vbe-glossary.md#scope), use the **ReDim** statement to change the number of dimensions, to define the number of elements, and to define the upper and lower bounds for each dimension. You can use the **ReDim** statement to change the dynamic array as often as necessary. However, each time you do this, the existing values in the array are lost. Use **ReDim Preserve** to expand an array while preserving existing values in the array. 
+In a procedure within the array's [scope](../../Glossary/vbe-glossary.md#scope), use the **ReDim** statement to change the number of dimensions, to define the number of elements, and to define the upper and lower bounds for each dimension. Use the **ReDim** statement to change the dynamic array as often as necessary. However, each time you do this, the existing values in the array are lost. Use **ReDim Preserve** to expand an array while preserving existing values in the array. 
 
 For example, the following statement enlarges the array by 10 elements without losing the current values of the original elements.
 

Language/Concepts/Getting-Started/declaring-variables.md

@@ -58,7 +58,7 @@ The shorthand for the types is: % -integer; & -long; @ -currency; # -double; ! -
 
 ## Public statement
 
-You can use the **Public** statement to declare public module-level variables.
+Use the **Public** statement to declare public module-level variables.
 
 ```vb
 Public strName As String 
@@ -69,7 +69,7 @@ Public variables can be used in any procedures in the project. If a public varia
 
 ## Private statement
 
-You can use the **[Private](../../reference/user-interface-help/private-statement.md)** statement to declare private module-level variables.
+Use the **[Private](../../reference/user-interface-help/private-statement.md)** statement to declare private module-level variables.
 
 ```vb
 Private MyName As String