MSFT style fixes

MicrosoftDocs · Jan 22, 2022 · 235eeef · 235eeef
1 parent 484af17
commit 235eeef
Show file tree

Hide file tree

Showing 551 changed files with 653 additions and 653 deletions.
diff --git a/LICENSE b/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

diff --git a/Language/Concepts/Forms/adjust-horizontal-and-vertical-spacing-between-controls.md b/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
 

diff --git a/Language/Concepts/Forms/tips-on-using-text-boxes.md b/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.
 

diff --git a/Language/Concepts/Forms/transparency-in-microsoft-forms.md b/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)**   

diff --git a/Language/Concepts/Getting-Started/avoiding-naming-conflicts.md b/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.
 

diff --git a/Language/Concepts/Getting-Started/calling-sub-and-function-procedures.md b/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" 

diff --git a/Language/Concepts/Getting-Started/declaring-variables.md b/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. 
 

diff --git a/Language/Concepts/Getting-Started/understanding-scope-and-visibility.md b/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.
 

diff --git a/Language/Concepts/Getting-Started/understanding-visual-basic-syntax.md b/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.
 

diff --git a/Language/Glossary/glossary-vba.md b/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

diff --git a/Language/Glossary/vbe-glossary.md b/Language/Glossary/vbe-glossary.md
@@ -669,7 +669,7 @@ Variables declared using the **Public** statement are visible to all procedures
 
 ## referenced project
 
-The project you directly create a link to from the current project you are working on. A project referenced by one of the current project's directly referenced projects is called an indirectly referenced project. Its **Public** variables are not accessible to the current project except through qualification with its project name. Any combination of direct and indirect references between projects is valid as long as they do not result in a complete cycle.
+The project you directly create a link to from the current project you are working on. A project referenced by one of the current project's directly referenced projects is called an indirectly referenced project. Its **Public** variables are not accessible to the current project except through qualification with its project name. Any combination of direct and indirect references between projects is valid as long as they don't result in a complete cycle.
 
 
 ## referencing project

diff --git a/Language/Reference/User-Interface-Help/beforedragover-event.md b/Language/Reference/User-Interface-Help/beforedragover-event.md
@@ -117,7 +117,7 @@ When  _Effect_ is set to **fmDropEffectMove**, the drop source supports a move o
 
 When  _Effect_ is set to **fmDropEffectNone**, the drop source supports a cancel operation.
 
-Most controls do not support drag-and-drop while  _Cancel_ is **False**, which is the default setting. This means that the control rejects attempts to drag or drop anything on the control, and the control does not initiate the BeforeDropOrPaste event. The **[TextBox](textbox-control.md)** and **[ComboBox](combobox-control.md)** controls are exceptions to this; these controls support drag-and-drop operations even when _Cancel_ is **False**.
+Most controls don't support drag-and-drop while  _Cancel_ is **False**, which is the default setting. This means that the control rejects attempts to drag or drop anything on the control, and the control does not initiate the BeforeDropOrPaste event. The **[TextBox](textbox-control.md)** and **[ComboBox](combobox-control.md)** controls are exceptions to this; these controls support drag-and-drop operations even when _Cancel_ is **False**.
 
 ## See also
 

diff --git a/Language/Reference/User-Interface-Help/combobox-control.md b/Language/Reference/User-Interface-Help/combobox-control.md
@@ -18,7 +18,7 @@ Combines the features of a **[ListBox](listbox-control.md)** and a **[TextBox](t
 
 If a **ComboBox** is [bound](../../Glossary/glossary-vba.md#bound) to a [data source](../../Glossary/glossary-vba.md#data-source), the **ComboBox** inserts the value the user enters or selects into that data source. If a multi-column combo box is bound, the **BoundColumn** property determines which value is stored in the bound data source.
 
-The list in a **ComboBox** consists of rows of data. Each row can have one or more columns, which can appear with or without headings. Some applications do not support column headings, others provide only limited support.
+The list in a **ComboBox** consists of rows of data. Each row can have one or more columns, which can appear with or without headings. Some applications don't support column headings, others provide only limited support.
 
 The default property of a **ComboBox** is the **Value** property. The default event of a **ComboBox** is the Change event.
 

diff --git a/...uage/Reference/User-Interface-Help/compile-error-in-hidden-modulemodule-name.md b/...uage/Reference/User-Interface-Help/compile-error-in-hidden-modulemodule-name.md
@@ -26,7 +26,7 @@ Possible solutions:
 
 - If you have access to the VBA code in the document or project, unprotect the module, and then run the code again to view the specific error.
 
-- If you do not have access to the VBA code in the document, then contact the document author to have the code in the hidden module updated.
+- If you don't have access to the VBA code in the document, then contact the document author to have the code in the hidden module updated.
 
 [!include[Add-ins note](~/includes/addinsnote.md)]
 

diff --git a/Language/Reference/User-Interface-Help/debug-menu.md b/Language/Reference/User-Interface-Help/debug-menu.md
@@ -21,7 +21,7 @@ ms.localizationpriority: medium
 |**Run to Cursor** | When your application is in design mode, use **Run To Cursor** to select a statement further down in your code where you want execution to stop. Your application will run from the current statement to the selected statement, and the current line of execution margin indicator (![Run to cursor](../../../images/wcurline_ZA01201810.gif)) appears on the **Margin Indicator** bar.<br/><br/>Use this command, for example, to avoid stepping through large loops. | | CTRL+F8|
 |**Set Next Statement** | Sets the execution point to the line of code you choose. You can set a different line of code to execute after the currently selected statement by selecting the line of code you want to execute and choosing the **Set Next Statement** command, or by dragging the **Current Execution Line** margin indicator to the line of code that you want to execute.<br/><br/>Using **Set Next Statement**, you can choose a line of code located before or after the currently selected statement. When you run the code, any intervening code isn't executed. Use this command when you want to rerun a statement within the current procedure or to skip over statements you don't want to execute. You can't use **Set Next Statement** for statements in different procedures. | ![Set Next Statement toolbar button](../../../images/tbr_snst_ZA01201746.gif) | CTRL+F9 |
 |**Show Next Statement** | Highlights the next statement to be executed. Use the **Show Next Statement** command to place the cursor on the line that will execute next. Available only in break mode.|![Show Next Statement toolbar button](../../../images/tbr_shns_ZA01201743.gif) | |
-|**Step Into** | Executes code one statement at a time.<br/><br/>When not in design mode, **Step Into** enters break mode at the current line of execution. If the statement is a call to a procedure, the next statement displayed is the first statement in the procedure.<br/><br/>At [design time](../../Glossary/vbe-glossary.md#design-time), this menu item begins execution and enters break mode before the first line of code is executed. If there is no current execution point, the **Step Into** command may appear to do nothing until you do something that triggers code, for example click on a document.|![Step Into toolbar button](../../../images/tbr_stpi_ZA01201749.gif) | F8 |
+|**Step Into** | Executes code one statement at a time.<br/><br/>When not in design mode, **Step Into** enters break mode at the current line of execution. If the statement is a call to a procedure, the next statement displayed is the first statement in the procedure.<br/><br/>At [design time](../../Glossary/vbe-glossary.md#design-time), this menu item begins execution and enters break mode before the first line of code is executed. If there is no current execution point, the **Step Into** command may appear to don'thing until you do something that triggers code, for example click on a document.|![Step Into toolbar button](../../../images/tbr_stpi_ZA01201749.gif) | F8 |
 |**Step Over** | Similar to **Step Into**. The difference in use occurs when the current statement contains a call to a procedure. **Step Over** executes the procedure as a unit, and then steps to the next statement in the current procedure. Therefore, the next statement displayed is the next statement in the current procedure regardless of whether the current statement is a call to another procedure. Available in break mode only.| ![Step Over toolbar button](../../../images/tbr_stpo_ZA01201750.gif) | SHIFT+F8 |
 |**Step Out** |Executes the remaining lines of a function in which the current execution point lies. The next statement displayed is the statement following the procedure call. All of the code is executed between the current and the final execution points. Available in break mode only.|![Step Out toolbar button](../../../images/tbr_stot_ZA01201748.gif) |CTRL+SHIFT+F8|
 |**Toggle Breakpoint** |Sets or removes a breakpoint at the current line. You can't set a breakpoint on lines containing nonexecutable code such as comments, declaration statements, or blank lines.<br/><br/>A line of code in which a breakpoint is set appears in the colors specified on the **[Editor Format](editor-format-tab-options-dialog-box.md)** tab of the **Options** dialog box.| ![Toggle Breakpoint toolbar button](../../../images/tbr_bkpt_ZA01201681.gif) | F9 |

diff --git a/...ge/Reference/User-Interface-Help/delete-method-visual-basic-for-applications.md b/...ge/Reference/User-Interface-Help/delete-method-visual-basic-for-applications.md
@@ -33,7 +33,7 @@ An error occurs if the specified file or folder does not exist.
 
 The results of the **Delete** method on a **File** or **Folder** are identical to operations performed by using **FileSystemObject.DeleteFile** or **FileSystemObject.DeleteFolder**.
 
-The **Delete** method does not distinguish between folders that have contents and those that do not. The specified folder is deleted regardless of whether or not it has contents.
+The **Delete** method does not distinguish between folders that have contents and those that don't. The specified folder is deleted regardless of whether or not it has contents.
 
 ## See also
 

diff --git a/Language/Reference/User-Interface-Help/deletefolder-method.md b/Language/Reference/User-Interface-Help/deletefolder-method.md
@@ -32,7 +32,7 @@ The **DeleteFolder** method syntax has these parts:
 
 ## Remarks
 
-The **DeleteFolder** method does not distinguish between folders that have contents and those that do not. The specified folder is deleted regardless of whether or not it has contents.
+The **DeleteFolder** method does not distinguish between folders that have contents and those that don't. The specified folder is deleted regardless of whether or not it has contents.
 
 An error occurs if no matching folders are found. The **DeleteFolder** method stops on the first error it encounters. No attempt is made to roll back or undo any changes that were made before an error occurred.
-Original file line number
+Diff line change
@@ Expand Up @@
     ```
-    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"
@@ Expand Down @@