Merge Linda toc 925 to master (MicrosoftDocs#209)

* removed en-us from links

* Added space before [

Strings: a, an, and, the, or, either, not, comma, is, has, at, closing parens, .md)or, in, its,
with, see

Author: Linda Caputo

Language/Concepts/Forms/add-a-watch-expression.md

@@ -20,9 +20,9 @@ A watch expression is an expression you define to be monitored in the  **Watch**
 
 1. On the  **Debug** menu, click **Add Watch**. The **Add Watch** dialog box is displayed.
 
-2. If an [expression](../../Glossary/vbe-glossary.md#expression) is already selected in the **Code** window, it is automatically displayed in the **Expression** box. If no expression is displayed, enter the expression you want to evaluate. The expression can be a[variable](../../Glossary/vbe-glossary.md#variable), a [property](../../Glossary/vbe-glossary.md#property), a function call, or any other valid expression.
+2. If an [expression](../../Glossary/vbe-glossary.md#expression) is already selected in the **Code** window, it is automatically displayed in the **Expression** box. If no expression is displayed, enter the expression you want to evaluate. The expression can be a [variable](../../Glossary/vbe-glossary.md#variable), a [property](../../Glossary/vbe-glossary.md#property), a function call, or any other valid expression.
 
-3. Select a [module](../../Glossary/vbe-glossary.md#module) or[procedure](../../Glossary/vbe-glossary.md#procedure) context in the **Context** group to select the range for which the expression will be evaluated.
+3. Select a [module](../../Glossary/vbe-glossary.md#module) or [procedure](../../Glossary/vbe-glossary.md#procedure) context in the **Context** group to select the range for which the expression will be evaluated.
 
      **Note**  Select the narrowest [scope](../../Glossary/vbe-glossary.md#scope) that fits your needs. Selecting all procedures or all modules can slow down module execution considerably, since the expression is evaluated after execution of each statement. If you select a specific procedure for a context, execution is affected only while the procedure is in the list of active procedure calls. Choose **Call Stack** from the **View** menu to display the list of active procedures.
 4. Select an option in the  **Watch Type** group to define how the system responds to the watch expression.

Language/Concepts/Forms/assign-a-control-tip-to-a-page-or-tab.md

@@ -20,7 +20,7 @@ ms.date: 06/08/2017
 
 3. From the shortcut menu, choose  **Rename**.
 
-4. In the  **ControlTipText** field, type the string you want to use as the[control tip](../../Glossary/glossary-vba.md#control-tip).
+4. In the  **ControlTipText** field, type the string you want to use as the [control tip](../../Glossary/glossary-vba.md#control-tip).
 
 5. Click OK.
 

Language/Concepts/Forms/should-i-use-a-multipage-or-a-tabstrip.md

@@ -13,5 +13,5 @@ ms.date: 06/08/2017
 
 If you use a single layout for data, use a  **TabStrip** and map each set of data to its own **Tab**. If you need several layouts for data, use a **MultiPage** and assign each layout to its own **Page**.
 
-Unlike a  **Page** of a **MultiPage**, the[client region](../../Glossary/glossary-vba.md#client-region) of a **TabStrip** is not a separate form, but a portion of the form that contains the **TabStrip**. The border of a **TabStrip** defines a region of the form that you can associate with the tabs. When you place a control in the client region of a **TabStrip**, you are adding a control to the form that contains the **TabStrip**.
+Unlike a  **Page** of a **MultiPage**, the [client region](../../Glossary/glossary-vba.md#client-region) of a **TabStrip** is not a separate form, but a portion of the form that contains the **TabStrip**. The border of a **TabStrip** defines a region of the form that you can associate with the tabs. When you place a control in the client region of a **TabStrip**, you are adding a control to the form that contains the **TabStrip**.
 

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

@@ -13,7 +13,7 @@ ms.date: 06/08/2017
 
 Microsoft Forms supports transparency in two areas: the background of certain controls, and in bitmaps used on certain controls.
 
-The  **BackStyle** property determines whether a control is[transparent](../../Glossary/glossary-vba.md#transparent). A transparent control lets you see what is behind it on the form. This is useful if you have a decorative background on the form and you want to minimize the amount of that background that is hidden behind the controls. For more information on making a control transparent, see [Create a transparent control](create-a-transparent-control.md).
+The  **BackStyle** property determines whether a control is [transparent](../../Glossary/glossary-vba.md#transparent). A transparent control lets you see what is behind it on the form. This is useful if you have a decorative background on the form and you want to minimize the amount of that background that is hidden behind the controls. For more information on making a control transparent, see [Create a transparent control](create-a-transparent-control.md).
 
 You can display a bitmap on many controls in Microsoft Forms. Certain controls support transparent bitmaps, that is, bitmaps in which one or more [background color](../../Glossary/glossary-vba.md#background-color) is transparent. Bitmap transparency is not controlled by any control property; it is controlled by the color of the lower-left pixel in the image. Microsoft Forms does not provide a way to edit a bitmap and make it transparent; you must use a picture editor for this purpose.
 

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

@@ -24,7 +24,7 @@ Microsoft Forms includes several properties that let you define the appearance o
 -  **SpecialEffect**
 
 
- **ForeColor** determines the[foreground color](../../Glossary/glossary-vba.md#foreground-color). The foreground color applies to any text associated with the control, such as the caption or the control's contents.
- **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.
+ **ForeColor** determines the [foreground color](../../Glossary/glossary-vba.md#foreground-color). The foreground color applies to any text associated with the control, such as the caption or the control's contents.
+ **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**. **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. **BorderStyle** supports only one border style, but lets you choose any color that is a valid setting for **BorderColor**. **BorderColor** specifies the color of the control's border, and is only valid when you use **BorderStyle** to create the border.
 

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

@@ -11,7 +11,7 @@ ms.date: 06/08/2017
 
 # Ways to create an option group
 
-By default, all  **OptionButton** controls on a[container](../../Glossary/vbe-glossary.md#container) (such as a form, a **MultiPage**, or a **Frame**) are part of a single option group. This means that selecting one of the buttons automatically sets all other option buttons on the form to **False**.
+By default, all  **OptionButton** controls on a [container](../../Glossary/vbe-glossary.md#container) (such as a form, a **MultiPage**, or a **Frame**) are part of a single option group. This means that selecting one of the buttons automatically sets all other option buttons on the form to **False**.
 
 If you want more than one option group on the form, there are two ways to create additional groups:
 

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

@@ -15,13 +15,13 @@ Many applications use data that should be available only to certain users. Here
 
 
 
-- Write code that makes a control (and its data) invisible to unauthorized users. The  **Visible** property makes a control visible or invisible. For more information about **Visible**, see[Visible Property](../../reference/User-Interface-Help/visible-property-microsoft-forms.md).
+- Write code that makes a control (and its data) invisible to unauthorized users. The  **Visible** property makes a control visible or invisible. For more information about **Visible**, see [Visible Property](../../reference/User-Interface-Help/visible-property-microsoft-forms.md).
 
-- Write code that sets the control's foreground and background to the same color when unauthorized users run the application. This hides the information from unauthorized users. The  **ForeColor** and **BackColor** properties determine the[foreground color](../../Glossary/glossary-vba.md#foreground-color) and the[background color](../../Glossary/glossary-vba.md#background-color). For information about  **ForeColor**, see[ForeColor Property](../../reference/User-Interface-Help/forecolor-property-microsoft-forms.md). For information about  **BackColor**, see[BackColor Property](../../reference/User-Interface-Help/backcolor-property-microsoft-forms.md).
+- Write code that sets the control's foreground and background to the same color when unauthorized users run the application. This hides the information from unauthorized users. The  **ForeColor** and **BackColor** properties determine the [foreground color](../../Glossary/glossary-vba.md#foreground-color) and the [background color](../../Glossary/glossary-vba.md#background-color). For information about  **ForeColor**, see [ForeColor Property](../../reference/User-Interface-Help/forecolor-property-microsoft-forms.md). For information about  **BackColor**, see [BackColor Property](../../reference/User-Interface-Help/backcolor-property-microsoft-forms.md).
 
-- Disable the control when unauthorized users run the application. The  **Enabled** property determines when a control is disabled. For information about **Enabled**, see[Enabled Property](../../reference/User-Interface-Help/enabled-property-microsoft-forms.md).
+- Disable the control when unauthorized users run the application. The  **Enabled** property determines when a control is disabled. For information about **Enabled**, see [Enabled Property](../../reference/User-Interface-Help/enabled-property-microsoft-forms.md).
 
-- 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** property defines placeholder characters. For information about **PasswordChar**, see[PasswordChar Property](passwordchar-property.md).
+- 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** property defines placeholder characters. For information about **PasswordChar**, see [PasswordChar Property](passwordchar-property.md).
 
 
 

Language/Concepts/Forms/what-is-a-multipage.md

@@ -11,7 +11,7 @@ ms.date: 06/08/2017
 
 # What is a MultiPage?
 
-A  **MultiPage** is a control that contains a[collection](../../Glossary/vbe-glossary.md#collection) of one or more pages.
+A  **MultiPage** is a control that contains a [collection](../../Glossary/vbe-glossary.md#collection) of one or more pages.
 
 Each  **Page** of a **MultiPage** is a form that contains its own controls, and as such, can have a unique layout. Typically, the pages in a **MultiPage** have tabs so the user can select the individual pages.
 

Language/Concepts/Forms/what-is-a-shortcut-menu.md

@@ -32,6 +32,6 @@ A shortcut menu is a menu that appears when you right-click an object. In Micros
 
 The commands on a shortcut menu vary depending on the object you select. For example, if you select multiple controls that aren't in a group, the shortcut menu will include the  **Group** command; the shortcut menu for the Toolbox will not.
 To display the shortcut menu for a control or container, right-click the object.
-For more information on displaying the shortcut menu for a  **MultiPage** or a **Page**, see[Display the shortcut menu for a MultiPage or Page](display-the-shortcut-menu-for-a-multipage-or-page.md).
-For more information on displaying the shortcut menu for a  **TabStrip** or a **Tab**, see[Display the shortcut menu for a TabStrip or Tab](display-the-shortcut-menu-for-a-tabstrip-or-tab.md).
+For more information on displaying the shortcut menu for a  **MultiPage** or a **Page**, see [Display the shortcut menu for a MultiPage or Page](display-the-shortcut-menu-for-a-multipage-or-page.md).
+For more information on displaying the shortcut menu for a  **TabStrip** or a **Tab**, see [Display the shortcut menu for a TabStrip or Tab](display-the-shortcut-menu-for-a-tabstrip-or-tab.md).
 

Language/Concepts/Forms/what-is-a-tabstrip.md

@@ -11,7 +11,7 @@ ms.date: 06/08/2017
 
 # What is a TabStrip?
 
-A  **TabStrip** is a control that contains a[collection](../../Glossary/vbe-glossary.md#collection) of one or more tabs.
+A  **TabStrip** is a control that contains a [collection](../../Glossary/vbe-glossary.md#collection) of one or more tabs.
 
 Each  **Tab** of a **TabStrip** is a separate object that users can select. Visually, a **TabStrip** also includes a client area that all the tabs in the **TabStrip** share.
 

Language/Concepts/Getting-Started/64-bit-visual-basic-for-applications-overview.md

@@ -32,7 +32,7 @@ To address this problem and enable VBA code to work correctly in both 32-bit and
 
 All [Declare Statements](../../reference/User-Interface-Help/../../reference/User-Interface-Help/declare-statement.md) must now include the **PtrSafe** keyword when running in 64-bit versions of Office. It is important to understand that simply adding the **PtrSafe** keyword to a **Declare** statement only signifies the **Declare** statement explicitly targets 64-bits, all data types within the statement that need to store 64-bits (including return values and parameters) must still be modified to hold 64-bit quantities.
 
- **Note**   **Declare** statements with the[PtrSafe](../../reference/User-Interface-Help/../../reference/User-Interface-Help/ptrsafe-keyword.md) keyword is the recommended syntax. **Declare** statements that include **PtrSafe** work correctly in the VBA7 development environment on both 32-bit and 64-bit platforms. To ensure backwards compatibility in VBA7 and earlier use the following construct:
+ **Note**   **Declare** statements with the [PtrSafe](../../reference/User-Interface-Help/../../reference/User-Interface-Help/ptrsafe-keyword.md) keyword is the recommended syntax. **Declare** statements that include **PtrSafe** work correctly in the VBA7 development environment on both 32-bit and 64-bit platforms. To ensure backwards compatibility in VBA7 and earlier use the following construct:
 
 
 

Language/Concepts/Getting-Started/compiler-constants.md

@@ -11,7 +11,7 @@ ms.date: 06/08/2017
 
 # Compiler Constants
 
-Visual Basic for Applications defines [constants](../../Glossary/vbe-glossary.md#constant) for exclusive use with the **#If...Then...#Else** directive. These constants are functionally equivalent to constants defined with the **#If...Then...#Else** directive except that they are global in[scope](../../Glossary/vbe-glossary.md#scope); that is, they apply everywhere in a [project](../../Glossary/vbe-glossary.md#project).
+Visual Basic for Applications defines [constants](../../Glossary/vbe-glossary.md#constant) for exclusive use with the **#If...Then...#Else** directive. These constants are functionally equivalent to constants defined with the **#If...Then...#Else** directive except that they are global in [scope](../../Glossary/vbe-glossary.md#scope); that is, they apply everywhere in a [project](../../Glossary/vbe-glossary.md#project).
 
 
  **Note**  Because  **Win32** returns true in both 32-bit and 64-bit development platforms it is important that the order within the **#If...Then...#Else** directive returns the desired results in your code. For example, because **Win32** returns True in 64-bit (**Win32** is compatible in **Win64** environments) checking for **Win32** before **Win64** results in the **Win64** condition never running because **Win32** returns True. The following order returns predictable results:

Language/Concepts/Getting-Started/deftype-statements.md

@@ -58,7 +58,7 @@ The statement name determines the data type:
 |**DefVar**|[Variant](../../Glossary/vbe-glossary.md#variant-data-type)|
 
 For example, in the following program fragment, is a string variable:
-A  **Def**_type_ statement affects only the[module](../../Glossary/vbe-glossary.md#module) where it is used. For example, a **DefInt** statement in one module affects only the default data type of variables, arguments passed to procedures, and the return type for **Function** and **Property** **Get** procedures declared in that module; the default data type of variables, arguments, and return types in other modules is unaffected. If not explicitly declared with a **Def**_type_ statement, the default data type for all variables, all arguments, all **Function** procedures, and all **Property** **Get** procedures is **Variant**.
+A  **Def**_type_ statement affects only the [module](../../Glossary/vbe-glossary.md#module) where it is used. For example, a **DefInt** statement in one module affects only the default data type of variables, arguments passed to procedures, and the return type for **Function** and **Property** **Get** procedures declared in that module; the default data type of variables, arguments, and return types in other modules is unaffected. If not explicitly declared with a **Def**_type_ statement, the default data type for all variables, all arguments, all **Function** procedures, and all **Property** **Get** procedures is **Variant**.
 When you specify a letter range, it usually defines the data type for variables that begin with letters in the first 128 characters of the character set. However, when you specify the letter range A-Z, you set the default to the specified data type for all variables, including variables that begin with international characters from the extended part of the character set (128-255).
 Once the range A-Z has been specified, you can't further redefine any subranges of variables using  **Def**_type_ statements. Once a range has been specified, if you include a previously defined letter in another **Def**_type_ statement, an error occurs. However, you can explicitly specify the data type of any variable, defined or not, using a **Dim** statement with an **As**_type_ clause. For example, you can use the following code at module level to define a variable as a **Double** even though the default data type is **Integer**:
  **Def**_type_ statements don't affect elements of[user-defined types](../../Glossary/vbe-glossary.md#user-defined-type) because the elements must be explicitly declared.