MSFT style fixes

Author: lindalu-MSFT

Language/Reference/User-Interface-Help/page-object.md

@@ -20,7 +20,7 @@ One page of a **[MultiPage](multipage-control.md)** and a single member of a **[
 
 Each **Page** object contains its own set of controls and does not necessarily rely on other pages in the [collection](../../Glossary/vbe-glossary.md#collection) for information. A **Page** inherits some properties from its [container](../../Glossary/vbe-glossary.md#container); the value of each [inherited property](../../Glossary/glossary-vba.md#inherited-property) is set by the container.
 
-A **Page** has a unique name and index value within a **Pages** collection. You can reference a **Page** by either its name or its index value. The index of the first **Page** in a collection is 0; the index of the second **Page** is 1; and so on. When two **Page** objects have the same name, you must reference each **Page** by its index value. References to the name in code will access only the first **Page** that uses the name.
+A **Page** has a unique name and index value within a **Pages** collection. Reference a **Page** by either its name or its index value. The index of the first **Page** in a collection is 0; the index of the second **Page** is 1; and so on. When two **Page** objects have the same name, you must reference each **Page** by its index value. References to the name in code will access only the first **Page** that uses the name.
 
 The default name for the first **Page** is Page1; the default name for the second **Page** is Page2.
 

Language/Reference/User-Interface-Help/pages-collection-microsoft-forms.md

@@ -20,7 +20,7 @@ A **Pages** collection includes all the pages of a **[MultiPage](multipage-contr
 
 Each **Pages** collection provides the features to manage the number of pages in the [collection](../../Glossary/vbe-glossary.md#collection) and to identify the page that is currently in use.
 
-A **Page** object has a unique name and index value within a **Pages** collection. You can reference a **Page** either by its name or its index value. The index of the first **Page** in a collection is 0; the index of the second **Page** is 1; and so on. The default name for the first page is Page1; the default name for the second page is Page2.
+A **Page** object has a unique name and index value within a **Pages** collection. Reference a **Page** either by its name or its index value. The index of the first **Page** in a collection is 0; the index of the second **Page** is 1; and so on. The default name for the first page is Page1; the default name for the second page is Page2.
 
 The default value of a **Pages** collection identifies the current **Page** of a collection.
 

Language/Reference/User-Interface-Help/tab-object.md

@@ -24,7 +24,7 @@ In contrast to a **Page**, a **Tab** does not contain any controls. Controls tha
 
 Each **Tab** has its own set of properties, but has no methods or events. You must use events from the appropriate **TabStrip** to initiate processing of an individual **Tab**.
 
-Each **Tab** has a unique name and index value within the [collection](../../Glossary/vbe-glossary.md#collection). You can reference a **Tab** by either its name or its index value. The index of the first **Tab** is 0; the index of the second **Tab** is 1; and so on. When two **Tab** objects have the same name, you must reference each **Tab** by its index value. References to the name in code will access only the first **Tab** that uses the name.
+Each **Tab** has a unique name and index value within the [collection](../../Glossary/vbe-glossary.md#collection). Reference a **Tab** by either its name or its index value. The index of the first **Tab** is 0; the index of the second **Tab** is 1; and so on. When two **Tab** objects have the same name, you must reference each **Tab** by its index value. References to the name in code will access only the first **Tab** that uses the name.
 
 ## See also
 

Language/Reference/User-Interface-Help/tabs-collection-microsoft-forms.md

@@ -22,7 +22,7 @@ Each **Tabs** collection provides the features to manage the number of tabs in t
 
 The default value of the **Tabs** collection identifies the current **Tab** of a collection.
 
-A **Tab** object has a unique name and index value within a **Tabs** collection. You can reference a **Tab** either by its name or its index value. The index value reflects the ordinal position of the **Tab** within the collection. The index of the first **Tab** in a collection is 0; the index of the second **Tab** is 1; and so on.
+A **Tab** object has a unique name and index value within a **Tabs** collection. Reference a **Tab** either by its name or its index value. The index value reflects the ordinal position of the **Tab** within the collection. The index of the first **Tab** in a collection is 0; the index of the second **Tab** is 1; and so on.
 
 ## See also
 

access/Concepts/Controls/refer-to-tab-control-objects-in-vba.md

@@ -97,7 +97,7 @@ The **PageIndex** property is more typically set at design time in a page's prop
 
 ## Refer to controls on a tab control page
 
-The controls you place on a tab control page are part of the same collection as all controls on the form. For this reason, each control on a tab control page must have a name that is unique with respect to all other controls on the same form. You can refer to controls on a tab control page by using the same syntax for controls on a form without a tab control. 
+The controls you place on a tab control page are part of the same collection as all controls on the form. For this reason, each control on a tab control page must have a name that is unique with respect to all other controls on the same form. Refer to controls on a tab control page by using the same syntax for controls on a form without a tab control. 
 
 ```vb
 Forms!Employees!HomePhone 

access/Concepts/Error-Codes/program-with-class-modules.md

@@ -75,6 +75,6 @@ When the procedure that creates this instance has finished executing, the instan
 
 Any properties that you set will affect this instance of the form's class, but won't be saved with the form. Also, a new instance of the form's class can't be created if the form is open in Design view.
 
-A nondefault instance of a form's class can't be referred to by name in the **[Forms](../../../api/Access.Forms.md)** collection. You can refer to it by index number only. Since you can create multiple nondefault instances of a form, and each instance has the same name, you can have more than one form with the same name in the **Forms** collection, without any means of distinguishing them other than by index number.
+A nondefault instance of a form's class can't be referred to by name in the **[Forms](../../../api/Access.Forms.md)** collection. Refer to it by index number only. Since you can create multiple nondefault instances of a form, and each instance has the same name, you can have more than one form with the same name in the **Forms** collection, without any means of distinguishing them other than by index number.
 
 [!include[Support and feedback](~/includes/feedback-boilerplate.md)]

access/Concepts/Reports/set-form-report-and-control-properties-in-code.md

@@ -32,7 +32,7 @@ Me.RecordSource = "SELECT * FROM Customers " _
 
 ## Set a property of a control
 
-Refer to the control in the **[Controls](../../../api/Access.Form.Controls.md)** collection of the **Form** or **Report** object on which it resides. You can refer to the **Controls** collection either implicitly or explicitly, but the code executes faster if you use an implicit reference. The following examples set the **Visible** property of a text box called CustomerID on the Customers form:
+Refer to the control in the **[Controls](../../../api/Access.Form.Controls.md)** collection of the **Form** or **Report** object on which it resides. Refer to the **Controls** collection either implicitly or explicitly, but the code executes faster if you use an implicit reference. The following examples set the **Visible** property of a text box called CustomerID on the Customers form:
 
 
 ```vb

access/Concepts/Settings/set-form-report-and-control-properties-in-visual-basic.md

@@ -32,7 +32,7 @@ Me.RecordSource = "SELECT * FROM Customers " _
 
 ## Set a property of a control
 
-Refer to the control in the **[Controls](../../../api/Access.Controls.md)** collection of the **Form** or **Report** object on which it resides. You can refer to the **Controls** collection either implicitly or explicitly, but the code executes faster if you use an implicit reference. The following examples set the **Visible** property of a text box called CustomerID on the Customers form:
+Refer to the control in the **[Controls](../../../api/Access.Controls.md)** collection of the **Form** or **Report** object on which it resides. Refer to the **Controls** collection either implicitly or explicitly, but the code executes faster if you use an implicit reference. The following examples set the **Visible** property of a text box called CustomerID on the Customers form:
 
 
 ```vb

api/Access.AccessObject.Properties.md

@@ -26,7 +26,7 @@ _expression_ A variable that represents an **[AccessObject](Access.AccessObject.
 
 ## Remarks
 
-The **AccessObjectProperties** collection object is the collection of all the properties related to an **AccessObject** object. You can refer to individual members of the collection by using the member object's index or a string expression that is the name of the member object. 
+The **AccessObjectProperties** collection object is the collection of all the properties related to an **AccessObject** object. Refer to individual members of the collection by using the member object's index or a string expression that is the name of the member object. 
 
 The first member object in the collection has an index value of 0, and the total number of member objects in the collection is the value of the **AccessObjectProperties** collection's **Count** property minus 1.
 

api/Access.AllDatabaseDiagrams.md

@@ -21,7 +21,7 @@ The **AllDatabaseDiagrams** collection contains an **[AccessObject](Access.Acces
 
 The **CurrentData** or **CodeData** object has an **AllDatabaseDiagrams** collection containing **AccessObject** objects that describe instances of all database diagrams specified by **CurrentData** or **CodeData**. For example, you can enumerate the **AllDatabaseDiagrams** collection in Visual Basic to set or return the values of properties of individual **AccessObject** objects in the collection.
 
-You can refer to an individual **AccessObject** object in the **AllDatabaseDiagrams** collection either by referring to the object by name, or by referring to its index within the collection. If you want to refer to a specific object in the **AllDatabaseDiagrams** collection, it's better to refer to the database diagram by name because a database diagram's collection index may change.
+Refer to an individual **AccessObject** object in the **AllDatabaseDiagrams** collection either by referring to the object by name, or by referring to its index within the collection. If you want to refer to a specific object in the **AllDatabaseDiagrams** collection, it's better to refer to the database diagram by name because a database diagram's collection index may change.
 
 The **AllDatabaseDiagrams** collection is indexed beginning with zero. If you refer to a database diagram by its index, the first database diagram is AllDatabaseDiagrams(0), the second database diagram is AllDatabaseDiagrams(1), and so on.