MSFT style fixes

Author: lindalu-MSFT

LICENSE

@@ -19,7 +19,7 @@ conditions that creators and other rights holders may use to share
 original works of authorship and other material subject to copyright
 and certain other rights specified in the public license below. The
 following considerations are for informational purposes only, are not
-exhaustive, and do not form part of our licenses.
+exhaustive, and don't form part of our licenses.
 
      Considerations for licensors: Our public licenses are
      intended for use by those authorized to give the public
@@ -146,7 +146,7 @@ Section 2 -- Scope.
 
        2. Exceptions and Limitations. For the avoidance of doubt, where
           Exceptions and Limitations apply to Your use, this Public
-          License does not apply, and You do not need to comply with
+          License does not apply, and You don't need to comply with
           its terms and conditions.
 
        3. Term. The term of this Public License is specified in Section

Language/Concepts/Forms/adjust-horizontal-and-vertical-spacing-between-controls.md

@@ -24,7 +24,7 @@ ms.localizationpriority: medium
 
    - **Decrease**, to decrease the space between controls by one grid block.
 
-   - **Remove**, to remove the space between controls. The controls do not overlap, but are immediately adjacent to each other.
+   - **Remove**, to remove the space between controls. The controls don't overlap, but are immediately adjacent to each other.
 
 ## See also
 

Language/Concepts/Forms/tips-on-using-text-boxes.md

@@ -20,7 +20,7 @@ The **[TextBox](../../reference/user-interface-help/textbox-control.md)** is a f
 
 - **[WordWrap](../../reference/user-interface-help/wordwrap-property.md)** allows the **TextBox** to wrap lines of text that are longer than the width of the **TextBox** into shorter lines that fit.
 
-If you do not use **WordWrap**, the **TextBox** starts a new line of text when it encounters a newline character in the text. If **WordWrap** is turned off, you can have text lines that do not fit completely in the **TextBox**. The **TextBox** displays the portions of text that fit inside its width and truncates the portions of text that do not fit. **WordWrap** is not applicable unless **MultiLine** is **True**.
+If you don't use **WordWrap**, the **TextBox** starts a new line of text when it encounters a newline character in the text. If **WordWrap** is turned off, you can have text lines that don't fit completely in the **TextBox**. The **TextBox** displays the portions of text that fit inside its width and truncates the portions of text that don't fit. **WordWrap** is not applicable unless **MultiLine** is **True**.
 
 - **[AutoSize](../../reference/user-interface-help/autosize-property.md)** controls whether the **TextBox** adjusts to display all of the text. When using **AutoSize** with a **TextBox**, the width of the **TextBox** shrinks or expands according to the amount of text in the **TextBox** and the font size used to display the text.
 

Language/Concepts/Forms/transparency-in-microsoft-forms.md

@@ -26,9 +26,9 @@ In Microsoft Forms, bitmaps are always transparent on the following controls:
 - **[OptionButton](../../reference/user-interface-help/optionbutton-control.md)**   
 - **[ToggleButton](../../reference/user-interface-help/togglebutton-control.md)**
 
-Transparent pictures sometimes have a hazy appearance. If you do not like this appearance, display the picture on a control that supports opaque images.
+Transparent pictures sometimes have a hazy appearance. If you don't like this appearance, display the picture on a control that supports opaque images.
 
-If you use a transparent bitmap on a control that does not support transparent bitmaps, the bitmap will display correctly, but you won't be able to see what's behind it. In Microsoft Forms, the following controls do not support transparent bitmaps:
+If you use a transparent bitmap on a control that does not support transparent bitmaps, the bitmap will display correctly, but you won't be able to see what's behind it. In Microsoft Forms, the following controls don't support transparent bitmaps:
 
 - The form window (**[UserForm](../../reference/user-interface-help/userform-window.md)**)   
 - **[Frame](../../reference/user-interface-help/frame-control.md)**   

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

@@ -12,7 +12,7 @@ ms.localizationpriority: medium
 
 # Avoiding naming conflicts
 
-A naming conflict occurs when you try to create or use an [identifier](../../Glossary/vbe-glossary.md#identifier) that was previously defined. In some cases, naming conflicts generate errors such as **Ambiguous name detected** or **Duplicate declaration in current scope**. Naming conflicts that go undetected can result in bugs in your code that produce erroneous results, especially if you do not explicitly declare all [variables](../../Glossary/vbe-glossary.md#variable) before first use.
+A naming conflict occurs when you try to create or use an [identifier](../../Glossary/vbe-glossary.md#identifier) that was previously defined. In some cases, naming conflicts generate errors such as **Ambiguous name detected** or **Duplicate declaration in current scope**. Naming conflicts that go undetected can result in bugs in your code that produce erroneous results, especially if you don't explicitly declare all [variables](../../Glossary/vbe-glossary.md#variable) before first use.
 
 You can avoid most naming conflicts by understanding the [scoping](../../Glossary/vbe-glossary.md#scope), private [module-level](../../Glossary/vbe-glossary.md#module-level), and public module-level.
 

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

@@ -66,7 +66,7 @@ Answer3 = MsgBox("Are you happy with your salary?", 4, "Question 3")
 
 ```
 
-If you are not interested in the return value of a function, you can call a function the same way you call a **Sub** procedure. Omit the parentheses, list the arguments, and do not assign the function to a variable, as shown in the following example.
+If you are not interested in the return value of a function, you can call a function the same way you call a **Sub** procedure. Omit the parentheses, list the arguments, and don't assign the function to a variable, as shown in the following example.
 
 ```vb
 MsgBox "Task Completed!", 0, "Task Box" 

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

@@ -30,7 +30,7 @@ Public strName As String
 
 For information about naming your variables, see [Visual Basic naming rules](visual-basic-naming-rules.md).
 
-Variables can be declared as one of the following [data types](../../reference/user-interface-help/data-type-summary.md): **Boolean**, **Byte**, **Integer**, **Long**, **Currency**, **Single**, **Double**, **Date**, **String** (for variable-length strings), **String * _length_** (for fixed-length strings), **Object**, or **Variant**. If you do not specify a data type, the **Variant** data type is assigned by default. You can also create a [user-defined type](../../Glossary/vbe-glossary.md#user-defined-type) by using the **[Type](../../reference/user-interface-help/type-statement.md)** statement. 
+Variables can be declared as one of the following [data types](../../reference/user-interface-help/data-type-summary.md): **Boolean**, **Byte**, **Integer**, **Long**, **Currency**, **Single**, **Double**, **Date**, **String** (for variable-length strings), **String * _length_** (for fixed-length strings), **Object**, or **Variant**. If you don't specify a data type, the **Variant** data type is assigned by default. You can also create a [user-defined type](../../Glossary/vbe-glossary.md#user-defined-type) by using the **[Type](../../reference/user-interface-help/type-statement.md)** statement. 
 
 You can declare several variables in one statement. To specify a data type, you must include the data type for each variable. 
 

Language/Concepts/Getting-Started/understanding-scope-and-visibility.md

@@ -67,7 +67,7 @@ Public strMsg As String
 
 ```
 
-All procedures are public by default, except for event procedures. When Visual Basic creates an event procedure, the **Private** [keyword](../../Glossary/vbe-glossary.md#keyword) is automatically inserted before the procedure declaration. For all other procedures, you must explicitly declare the procedure with the **Private** keyword if you do not want it to be public.
+All procedures are public by default, except for event procedures. When Visual Basic creates an event procedure, the **Private** [keyword](../../Glossary/vbe-glossary.md#keyword) is automatically inserted before the procedure declaration. For all other procedures, you must explicitly declare the procedure with the **Private** keyword if you don't want it to be public.
 
 Use public procedures, variables, and constants defined in standard modules or class modules from referencing projects. However, you must first set a reference to the project in which they are defined.
 

Language/Concepts/Getting-Started/understanding-visual-basic-syntax.md

@@ -46,7 +46,7 @@ MsgBox Title:="Answer Box", Prompt:="Your answer is correct!"
 
 ```
 
-The syntax for functions and some methods shows the arguments enclosed in parentheses. These functions and methods return values, so you must enclose the arguments in parentheses to assign the value to a variable. If you ignore the return value or if you don't pass arguments at all, don't include the parentheses. Methods that don't return values do not need their arguments enclosed in parentheses. These guidelines apply whether you are using positional arguments or named arguments.
+The syntax for functions and some methods shows the arguments enclosed in parentheses. These functions and methods return values, so you must enclose the arguments in parentheses to assign the value to a variable. If you ignore the return value or if you don't pass arguments at all, don't include the parentheses. Methods that don't return values don't need their arguments enclosed in parentheses. These guidelines apply whether you are using positional arguments or named arguments.
 
 In the following example, the return value from the **MsgBox** function is a number indicating the selected button that is stored in the variable `myVar`. Because the return value is used, parentheses are required. Another message box then displays the value of the variable.
 

Language/Glossary/glossary-vba.md

@@ -43,7 +43,7 @@ A unique number or string that corresponds to a specific object in an applicatio
 
 ## control group
 
-A set of controls that are conceptually or logically related. Controls that are conceptually related are usually viewed together but do not necessarily affect each other. Controls that are logically related affect each other. For example, setting one button in a group of option buttons sets the value of all other buttons in the group to **False**.
+A set of controls that are conceptually or logically related. Controls that are conceptually related are usually viewed together but don't necessarily affect each other. Controls that are logically related affect each other. For example, setting one button in a group of option buttons sets the value of all other buttons in the group to **False**.
 
 
 ## control tip