typo cleanup

- Behavio -> Behavior - defeault -> default - sytem -> system - embeded -> embedded - proporties -> properties - Customm -> Custom - Toogle -> Toggle - Forumula -> Formula - galler -> gallery - currect -> correct - otained -> obtained - obect -> ojbect - Distribition -> Distribution - requestiong -> requesting - detault -> default - houshold -> household - prroperties -> properties - attept -> attempt - collecton -> collection - emptry -> empty - proprety -> property - elgible -> eligible - resoruce -> resource - appointements -> appointments - explict -> explicit - comarison -> comparison - decathalon -> decathlon - Condtion -> Condition - occurence -> occurrence
MicrosoftDocs · Feb 16, 2019 · 00476ba · 00476ba
1 parent c23445c
commit 00476ba
Show file tree

Hide file tree

Showing 28 changed files with 53 additions and 53 deletions.
diff --git a/F1/vislinkreplacebehavio-enumeration-visio-vis_sdr-chm70555.md b/F1/vislinkreplacebehavio-enumeration-visio-vis_sdr-chm70555.md
@@ -1,5 +1,5 @@
 ---
-title: VisLinkReplaceBehavio Enumeration, Visio [vis_sdr.chm70555]
+title: VisLinkReplaceBehavior Enumeration, Visio [vis_sdr.chm70555]
 keywords: vis_sdr.chm70555
 f1_keywords:
 - vis_sdr.chm70555
@@ -10,7 +10,7 @@ localization_priority: Normal
 ---
 
 
-# VisLinkReplaceBehavio Enumeration, Visio [vis_sdr.chm70555]
+# VisLinkReplaceBehavior Enumeration, Visio [vis_sdr.chm70555]
 
 Hi there! You have landed on one of our F1 Help redirector pages. Please select the topic you were looking for below.
 

diff --git a/Language/Glossary/vbe-glossary.md b/Language/Glossary/vbe-glossary.md
@@ -303,7 +303,7 @@ Any self-contained work created with an application and given a unique file name
 
 ## document design mode
 
-A design mode toggled by the host application typically via a button on the developer ribbon where mouse interactions with controls embeded in a document adjusts its placement, size and proporties instead of activating its actions.
+A design mode toggled by the host application typically via a button on the developer ribbon where mouse interactions with controls embedded in a document adjusts its placement, size and properties instead of activating its actions.
 
 
 ## Double data type

diff --git a/Language/Reference/User-Interface-Help/array-function.md b/Language/Reference/User-Interface-Help/array-function.md
@@ -28,7 +28,7 @@ In the following example, the first [statement](../../Glossary/vbe-glossary.md#s
 
 ```vb
 Dim A As Variant, B As Long, i As Long
-A = Array(10, 20, 30)  ' A is a three element list by defeault indexed 0 to 2
+A = Array(10, 20, 30)  ' A is a three element list by default indexed 0 to 2
 B = A(2)               ' B is now 30
 ReDim Preserve A(4)    ' Extend A's length to five elements
 A(4) = 40              ' Set the fifth element's value

diff --git a/Language/Reference/User-Interface-Help/left-top-properties.md b/Language/Reference/User-Interface-Help/left-top-properties.md
@@ -32,7 +32,7 @@ Setting the **Left** or **Top** property to 0 places the control's edge at the l
 
 ## Remarks
 
-For most systems, the recommended range of values for **Left** and **Top** is from -32,767 to +32,767. Other values may also work depending on your sytem configuration. 
+For most systems, the recommended range of values for **Left** and **Top** is from -32,767 to +32,767. Other values may also work depending on your system configuration. 
 
 For a **[ComboBox](combobox-control.md)**, values of **Left** and **Top** apply to the text portion of the control, not to the list portion. When you move or size a control, its new **Left** setting is automatically entered in the property sheet. When you print a form, the control's horizontal or vertical location is determined by its **Left** or **Top** setting.
 

diff --git a/...ce/Concepts/customize-the-office-fluent-ribbon-by-using-a-managed-com-add-in.md b/...ce/Concepts/customize-the-office-fluent-ribbon-by-using-a-managed-com-add-in.md
@@ -139,7 +139,7 @@ In this step you add code to the Extensibility.IDTExtensibility2::OnConnection t
 
 5. Insert the following statement into the **GetCustomUI** method, overwriting the existing code: `return GetResource("customUI.xml");`
 
-6. Insert the following method below the **GetCustommUI** method:
+6. Insert the following method below the **GetCustomUI** method:
 
    ```cs
     private string GetResource(string resourceName) 

diff --git a/Library-Reference/Concepts/getting-started-with-vba-in-office.md b/Library-Reference/Concepts/getting-started-with-vba-in-office.md
@@ -193,14 +193,14 @@ Remember how you chose cell B2 to display the **Stop Recording** button again? T
 
 The lines of code that start with an apostrophe and colored green by the editor are comments that explain the code or remind you and other programmers the purpose of the code. VBA ignores any line, or portion of a line, that begins with a single quote. Writing clear and appropriate comments in your code is an important topic, but that discussion is out of the scope of this article. Subsequent references to this code in the article do not include those four comment lines.
 
-When the macro recorder generates the code, it uses a complex algorithm to determine the methods and the properties that you intended. If you do not recognize a given property, there are many resources available to help you. For example, in the macro that you recorded, the macro recorder generated code that refers to the **ForumulaR1C1** property. Not sure what that means?
+When the macro recorder generates the code, it uses a complex algorithm to determine the methods and the properties that you intended. If you do not recognize a given property, there are many resources available to help you. For example, in the macro that you recorded, the macro recorder generated code that refers to the **FormulaR1C1** property. Not sure what that means?
 
 > [!NOTE] 
 > Be aware that **Application** object is implied in all VBA macros. The code that you recorded works with **Application.** at the beginning of each line.
 
 ### Using Developer Help
 
-Select **ForumulaR1C1** in the recorded macro and press F1. The Help system runs a quick search, determines that the appropriate subjects are in the Excel Developer section of the Excel Help, and lists the **FormulaR1C1** property. You can choose the link to read more about the property, but before you do, be aware of the **Excel Object Model Reference** link near the bottom of the window. Choose the link to view a long list of objects that Excel uses in its object model to describe the Worksheets and their components. 
+Select **FormulaR1C1** in the recorded macro and press F1. The Help system runs a quick search, determines that the appropriate subjects are in the Excel Developer section of the Excel Help, and lists the **FormulaR1C1** property. You can choose the link to read more about the property, but before you do, be aware of the **Excel Object Model Reference** link near the bottom of the window. Choose the link to view a long list of objects that Excel uses in its object model to describe the Worksheets and their components. 
 
 Choose any one of those to see the properties and methods that apply to that particular object, along with cross references to different related options. Many Help entries also have brief code examples that can help you. For example, you can follow the links in the **Borders** object to see how to set a border in VBA.
 

diff --git a/Library-Reference/Concepts/overview-of-the-office-fluent-ribbon.md b/Library-Reference/Concepts/overview-of-the-office-fluent-ribbon.md
@@ -141,7 +141,7 @@ This sample makes the following changes to the ribbon in Word, in the following
 
 4. Adds a new **SampleGroup** group to the **My Tab** tab.
 
-5. Adds a large-sized ToogleButton1 button to **My Group** and specifies an onAction callback along with a GetPressed callback.
+5. Adds a large-sized ToggleButton1 button to **My Group** and specifies an onAction callback along with a GetPressed callback.
 
 6. Adds a **CheckBox1** check box to **My Group** with a custom screentip and specifies an onAction callback.
 

diff --git a/Office-Mac/idMSOExcelMac.md b/Office-Mac/idMSOExcelMac.md
@@ -628,12 +628,12 @@ Office 2016 for Mac apps do not support some of the idMSOs that Office for Windo
 |PictureArtisticEffectsGallery|gallery|
 |PictureArtisticEffectsReset|button|
 |PictureBackgroundRemoval|toggleButton|
-|PictureBrightnessAndContrastGallery|galler|
+|PictureBrightnessAndContrastGallery|gallery|
 |PictureChange|button|
 |PictureColorDialog|button|
 |PictureColorMenu|menu|
 |PictureColorReset|button|
-|PictureColorTempertatureGallery|galler|
+|PictureColorTempertatureGallery|gallery|
 |PictureCorrectionsDialog|button|
 |PictureCorrectionsMenu|menu|
 |PictureCorrectionsReset|button|
@@ -659,18 +659,18 @@ Office 2016 for Mac apps do not support some of the idMSOs that Office for Windo
 |PictureFillCrop|button|
 |PictureFitCrop|button|
 |PictureInsertFromFile|button|
-|PictureRecolorGallery|galler|
+|PictureRecolorGallery|gallery|
 |PictureRecolorMoreColorsDialog|button|
 |PictureReflectionGallery|gallery|
 |PictureReset|button|
 |PictureResetAndSize|button|
 |PictureResetSplitButton|splitButton|
 |PictureRotationGallery|gallery|
-|PictureSaturationGallery|galler|
+|PictureSaturationGallery|gallery|
 |PicturesCompress|button|
 |PictureSetTransparentColor|toggleButton|
 |PictureShapeGallery|gallery|
-|PictureSharpenSoftenGallery|galler|
+|PictureSharpenSoftenGallery|gallery|
 |PictureStylesGallery|gallery|
 |PictureTransparencyGallery|gallery|
 |PivotClearAll|button|

diff --git a/Office-Mac/idMSOPowerPointMac.md b/Office-Mac/idMSOPowerPointMac.md
@@ -33,7 +33,7 @@ Office 2016 for Mac apps do not support some of the idMSOs that Office for Windo
 |AlignLeft|toggleButton|
 |AlignRight|toggleButton|
 |AnimationAutoPreview|toggleButton|
-|AnimationChangeGallery|galler|
+|AnimationChangeGallery|gallery|
 |AnimationDuration|control|
 |AnimationPainter|control|
 |AnimationPreview|button|
@@ -70,7 +70,7 @@ Office 2016 for Mac apps do not support some of the idMSOs that Office for Windo
 |BorderTop|toggleButton|
 |BrightnessLess|button|
 |BrightnessMore|button|
-|BuildOrderChangeGallery|galler|
+|BuildOrderChangeGallery|gallery|
 |BulletsAndNumberingBulletsDialog|button|
 |BulletsAndNumberingNumberingDialog|button|
 |BulletsGallery|gallery|
@@ -136,8 +136,8 @@ Office 2016 for Mac apps do not support some of the idMSOs that Office for Windo
 |Cut|button|
 |DateAndTimeInsert|button|
 |DuplicateSelectedSlides|button|
-|EffectOptionsColorsGallery|galler|
-|EffectOptionsGallery|galler|
+|EffectOptionsColorsGallery|gallery|
+|EffectOptionsGallery|gallery|
 |EffectOptionsMenu|menu|
 |EquationAccentGallery|gallery|
 |EquationDelimiterGallery|gallery|
@@ -380,12 +380,12 @@ Office 2016 for Mac apps do not support some of the idMSOs that Office for Windo
 |PickUpStyle|button|
 |PictureArtisticEffectsGallery|gallery|
 |PictureBackgroundRemoval|toggleButton|
-|PictureBrightnessAndContrastGallery|galler|
+|PictureBrightnessAndContrastGallery|gallery|
 |PictureChange|button|
 |PictureColorDialog|button|
 |PictureColorMenu|menu|
 |PictureColorReset|button|
-|PictureColorTempertatureGallery|galler|
+|PictureColorTempertatureGallery|gallery|
 |PictureCorrectionsDialog|button|
 |PictureCorrectionsMenu|menu|
 |PictureCorrectionsReset|button|
@@ -413,18 +413,18 @@ Office 2016 for Mac apps do not support some of the idMSOs that Office for Windo
 |PictureFitCrop|button|
 |PictureInsertFromFile|button|
 |PictureInsertFromFilePowerPoint|menu|
-|PictureRecolorGallery|galler|
+|PictureRecolorGallery|gallery|
 |PictureRecolorMoreColorsDialog|button|
 |PictureReflectionGallery|gallery|
 |PictureReset|button|
 |PictureResetAndSize|button|
 |PictureResetSplitButton|splitButton|
 |PictureRotationGallery|gallery|
-|PictureSaturationGallery|galler|
+|PictureSaturationGallery|gallery|
 |PicturesCompress|button|
 |PictureSetTransparentColor|toggleButton|
 |PictureShapeGallery|gallery|
-|PictureSharpenSoftenGallery|galler|
+|PictureSharpenSoftenGallery|gallery|
 |PictureStylesGallery|gallery|
 |PictureTransparencyGallery|gallery|
 |PowerPointPageSetup|gallery|

diff --git a/Office-Mac/idMSOWordMac.md b/Office-Mac/idMSOWordMac.md
@@ -729,14 +729,14 @@ Office 2016 for Mac apps do not support some of the idMSOs that Office for Windo
 |PictureArtisticEffectsGallery|gallery|
 |PictureArtisticEffectsReset|button|
 |PictureBackgroundRemoval|toggleButton|
-|PictureBrightnessAndContrastGallery|galler|
+|PictureBrightnessAndContrastGallery|gallery|
 |PictureBrightnessGallery|gallery|
 |PictureBulletsInsert|button|
 |PictureChange|button|
 |PictureColorDialog|button|
 |PictureColorMenu|menu|
 |PictureColorReset|button|
-|PictureColorTempertatureGallery|galler|
+|PictureColorTempertatureGallery|gallery|
 |PictureContrastGallery|gallery|
 |PictureCorrectionsDialog|button|
 |PictureCorrectionsMenu|menu|
@@ -764,18 +764,18 @@ Office 2016 for Mac apps do not support some of the idMSOs that Office for Windo
 |PictureFitCrop|button|
 |PictureInsertFromFile|button|
 |PicturePositionGallery|gallery|
-|PictureRecolorGallery|galler|
+|PictureRecolorGallery|gallery|
 |PictureRecolorMoreColorsDialog|button|
 |PictureReflectionGallery|gallery|
 |PictureReset|button|
 |PictureResetAndSize|button|
 |PictureResetSplitButton|splitButton|
 |PictureRotationGallery|gallery|
-|PictureSaturationGallery|galler|
+|PictureSaturationGallery|gallery|
 |PicturesCompress|button|
 |PictureSetTransparentColor|toggleButton|
 |PictureShapeGallery|gallery|
-|PictureSharpenSoftenGallery|galler|
+|PictureSharpenSoftenGallery|gallery|
 |PictureStylesGallery|gallery|
 |PictureTransparencyGallery|gallery|
 |PlayMacro|button|

diff --git a/...te-a-sendable-item-for-a-specific-account-based-on-the-current-folder-outloo.md b/...te-a-sendable-item-for-a-specific-account-based-on-the-current-folder-outloo.md
@@ -64,7 +64,7 @@ private void CreateMailItemFromAccount()
 ```
 
 
-The next method,  `CreateMeetingRequestFromAccount`, is similar to  `CreateMailItemFromAccount` except that it creates an **AppointmentItem** instead of a **MailItem**, and associates the  **AppointmentItem** with the account by using its [SendUsingAccount](../../../api/Outlook.AppointmentItem.SendUsingAccount.md) property. `CreateMeetingRequestFromAccount` creates an **AppointmentItem** in the Calendar folder of an account whose default delivery store is the same as the store for the folder that is displayed in the active explorer. `CreateMeetingRequestFromAccount` first identifies the appropriate account by matching the store of the current folder (obtained from the **Folder.Store** property) with the default delivery store of each account (otained with the **Account.DeliveryStore** property) that is defined in the **Accounts** collection for the session. `CreateMeetingRequestFromAccount` then creates the **AppointmentItem**. To associate the item with the account,  `CreateMeetingRequestFromAccount` assigns that account as the item's sending account by setting the [Account](../../../api/Outlook.Account.md) object to the **SendUsingAccount** property of the **AppointmentItem**. Assigning the  **SendUsingAccount** property is the important step because otherwise, the **AppointmentItem** is created for the primary account. At the end of the method, `CreateMeetingRequestFromAccount` displays the **AppointmentItem**. Note that if the current folder is not on a delivery store,  `CreateMeetingRequestFromAccount` simply creates the **AppointmentItem** for the primary account for the session.
+The next method,  `CreateMeetingRequestFromAccount`, is similar to  `CreateMailItemFromAccount` except that it creates an **AppointmentItem** instead of a **MailItem**, and associates the  **AppointmentItem** with the account by using its [SendUsingAccount](../../../api/Outlook.AppointmentItem.SendUsingAccount.md) property. `CreateMeetingRequestFromAccount` creates an **AppointmentItem** in the Calendar folder of an account whose default delivery store is the same as the store for the folder that is displayed in the active explorer. `CreateMeetingRequestFromAccount` first identifies the appropriate account by matching the store of the current folder (obtained from the **Folder.Store** property) with the default delivery store of each account (obtained with the **Account.DeliveryStore** property) that is defined in the **Accounts** collection for the session. `CreateMeetingRequestFromAccount` then creates the **AppointmentItem**. To associate the item with the account,  `CreateMeetingRequestFromAccount` assigns that account as the item's sending account by setting the [Account](../../../api/Outlook.Account.md) object to the **SendUsingAccount** property of the **AppointmentItem**. Assigning the  **SendUsingAccount** property is the important step because otherwise, the **AppointmentItem** is created for the primary account. At the end of the method, `CreateMeetingRequestFromAccount` displays the **AppointmentItem**. Note that if the current folder is not on a delivery store,  `CreateMeetingRequestFromAccount` simply creates the **AppointmentItem** for the primary account for the session.
 
 
 

diff --git a/outlook/Concepts/Accounts/identify-a-folder-with-an-account.md b/outlook/Concepts/Accounts/identify-a-folder-with-an-account.md
@@ -40,7 +40,7 @@ Outlook.Account GetAccountForFolder(Outlook.Folder folder)
     foreach (Outlook.Account account in Application.Session.Accounts) 
     { 
         // Match the DefaultStore.StoreID of the account 
-        // with the Store.StoreID for the currect folder. 
+        // with the Store.StoreID for the correct folder. 
         if (account.DeliveryStore.StoreID  == store.StoreID) 
         { 
             // Return the account whose default delivery store 

diff --git a/.../access-exchange-user-or-distribution-list-information-from-the-address-book.md b/.../access-exchange-user-or-distribution-list-information-from-the-address-book.md
@@ -27,7 +27,7 @@ Certain properties like  **OfficeLocation** and **JobTitle** are read-write and
 
 ## Exchange Distribution List
 
- The **ExchangeDistributionList** obect supports properties like **Alias**,  **[Comments](../../../api/Outlook.ExchangeDistributionList.Comments.md)**, and  **[PrimarySmtpAddress](../../../api/Outlook.ExchangeDistributionList.PrimarySmtpAddress.md)** that the parent **AddressEntry** object does not support. Other properties of the Exchange distribution list that are not exposed in the object model are accessible through **[ExchangeDistributionList.PropertyAccessor](../../../api/Outlook.ExchangeDistributionList.PropertyAccessor.md)**.
+ The **ExchangeDistributionList** object supports properties like **Alias**,  **[Comments](../../../api/Outlook.ExchangeDistributionList.Comments.md)**, and  **[PrimarySmtpAddress](../../../api/Outlook.ExchangeDistributionList.PrimarySmtpAddress.md)** that the parent **AddressEntry** object does not support. Other properties of the Exchange distribution list that are not exposed in the object model are accessible through **[ExchangeDistributionList.PropertyAccessor](../../../api/Outlook.ExchangeDistributionList.PropertyAccessor.md)**.
 
 The  **ExchangeDistributionList** object also supports methods like **[GetExchangeDistributionListMembers](../../../api/Outlook.ExchangeDistributionList.GetExchangeDistributionListMembers.md)**,  **[GetMemberOfList](../../../api/Outlook.ExchangeDistributionList.GetMemberOfList.md)** and **[GetOwners](../../../api/Outlook.ExchangeDistributionList.GetOwners.md)** to facilitate accessing information specific to a distribution list, such as full **AddressEntry** information for the associated members in this distribution list, other distribution lists that this list is a member of, and owners of this list.
 

diff --git a/...Book/identify-the-global-address-list-or-a-set-of-address-lists-with-a-store.md b/...Book/identify-the-global-address-list-or-a-set-of-address-lists-with-a-store.md
@@ -60,7 +60,7 @@ public Outlook.AddressList GetGlobalAddressList(Outlook.Store store)
         throw new ArgumentNullException(); 
     } 
 
-    // Obtain the store UID using the proprety string and  
+    // Obtain the store UID using the property string and  
     // property accessor on the store. 
     Outlook.PropertyAccessor oPAStore = store.PropertyAccessor; 
 

diff --git a/...-the-name-and-office-location-of-each-manager-belonging-to-an-exchange-distr.md b/...-the-name-and-office-location-of-each-manager-belonging-to-an-exchange-distr.md
@@ -12,7 +12,7 @@ localization_priority: Normal
 This topic describes how to allow a user to select an Exchange distribution list and display the name and office location of each member who is a manager belonging to that distribution list. The major steps of this procedure are as follows:
 
 
-1. The code sample below displays a  **Select Distribition List** dialog box for the user to select a distribution list.
+1. The code sample below displays a  **Select Distribution List** dialog box for the user to select a distribution list.
 
     It uses the  **[SelectNamesDialog](../../../api/Outlook.SelectNamesDialog.md)** object to display the dialog box and obtain user selection. The sample then obtains the user selection through the **[SelectNamesDialog.Recipients](../../../api/Outlook.SelectNamesDialog.Recipients.md)** property.
 

diff --git a/...ncepts/Creating-Form-Regions/add-a-form-region-to-an-existing-page-on-a-form.md b/...ncepts/Creating-Form-Regions/add-a-form-region-to-an-existing-page-on-a-form.md
@@ -15,7 +15,7 @@ This walkthrough shows how to add an adjoining form region to the **General** pa
 
 2. Use a text editor, such as Notepad, to create a form region manifest XML file for the form region. This file describes to Outlook how to display the form region (for example, title, and localized action names) and what it does (for example, custom actions and add-in support).
 
-3. Use the Windows Registry Editor to register the form region with a message class, identifying to Outlook the type of items that are elgible to use this form region.
+3. Use the Windows Registry Editor to register the form region with a message class, identifying to Outlook the type of items that are eligible to use this form region.
 
 4. Restart Outlook to use the updated Contact form.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -64,7 +64,7 @@ private void CreateMailItemFromAccount()
		```


		The next method, `CreateMeetingRequestFromAccount`, is similar to `CreateMailItemFromAccount` except that it creates an AppointmentItem instead of a MailItem, and associates the AppointmentItem with the account by using its [SendUsingAccount](../../../api/Outlook.AppointmentItem.SendUsingAccount.md) property. `CreateMeetingRequestFromAccount` creates an AppointmentItem in the Calendar folder of an account whose default delivery store is the same as the store for the folder that is displayed in the active explorer. `CreateMeetingRequestFromAccount` first identifies the appropriate account by matching the store of the current folder (obtained from the Folder.Store property) with the default delivery store of each account (otained with the Account.DeliveryStore property) that is defined in the Accounts collection for the session. `CreateMeetingRequestFromAccount` then creates the AppointmentItem. To associate the item with the account, `CreateMeetingRequestFromAccount` assigns that account as the item's sending account by setting the [Account](../../../api/Outlook.Account.md) object to the SendUsingAccount property of the AppointmentItem. Assigning the SendUsingAccount property is the important step because otherwise, the AppointmentItem is created for the primary account. At the end of the method, `CreateMeetingRequestFromAccount` displays the AppointmentItem. Note that if the current folder is not on a delivery store, `CreateMeetingRequestFromAccount` simply creates the AppointmentItem for the primary account for the session.
		The next method, `CreateMeetingRequestFromAccount`, is similar to `CreateMailItemFromAccount` except that it creates an AppointmentItem instead of a MailItem, and associates the AppointmentItem with the account by using its [SendUsingAccount](../../../api/Outlook.AppointmentItem.SendUsingAccount.md) property. `CreateMeetingRequestFromAccount` creates an AppointmentItem in the Calendar folder of an account whose default delivery store is the same as the store for the folder that is displayed in the active explorer. `CreateMeetingRequestFromAccount` first identifies the appropriate account by matching the store of the current folder (obtained from the Folder.Store property) with the default delivery store of each account (obtained with the Account.DeliveryStore property) that is defined in the Accounts collection for the session. `CreateMeetingRequestFromAccount` then creates the AppointmentItem. To associate the item with the account, `CreateMeetingRequestFromAccount` assigns that account as the item's sending account by setting the [Account](../../../api/Outlook.Account.md) object to the SendUsingAccount property of the AppointmentItem. Assigning the SendUsingAccount property is the important step because otherwise, the AppointmentItem is created for the primary account. At the end of the method, `CreateMeetingRequestFromAccount` displays the AppointmentItem. Note that if the current folder is not on a delivery store, `CreateMeetingRequestFromAccount` simply creates the AppointmentItem for the primary account for the session.



Expand Down