Update exchange-online-powershell-v2.md

Per email convo re: Minimum property sets

Author: chrisda

exchange/docs-conceptual/exchange-online-powershell-v2.md

@@ -67,17 +67,11 @@ You can download the EXO V2 module from the PowerShell gallery [here](https://ww
 - You can use the following versions of Windows:
 
   - Windows 10
-
   - Windows 8.1
-
   - Windows Server 2019
-
   - Windows Server 2016
-
   - Windows Server 2012 or Windows Server 2012 R2
-
   - Windows 7 Service Pack 1 (SP1)<sup>*</sup>
-
   - Windows Server 2008 R2 SP1<sup>*</sup>
 
   <sup>\*</sup> This version of windows has reached end of support, and is now only supported when running in Azure virtual machines. To use this version of Windows, you need to install the Microsoft .NET Framework 4.5 or later and then the Windows Management Framework 5.1. For more information, see [Windows Management Framework 5.1](https://aka.ms/wmf5download).
@@ -241,9 +235,9 @@ Get-EXOCASMailbox -Properties EwsEnabled, MAPIBlockOutlookNonCachedMode -Propert
 
 We've also included a Minimum property set (or *minset*) in the available property sets that includes a bare minimum set of properties for the cmdlet output.
 
-- If you don't use the *PropertySets* or *Properties* parameters, you automatically get the properties that are included in the Minimum property set.
+- If you don't use the *PropertySets* or *Properties* parameters, you automatically get the properties in the Minimum property set.
 
-- If you use the *PropertySets* or *Properties* parameters, you you only get the specified properties.
+- If you use the *PropertySets* or *Properties* parameters, you get the specified properties **and** the properties in the Minimum property set.
 
 Either way, the cmdlet output will contain far fewer properties, and the time it takes to return those results will be much faster.
 
@@ -257,16 +251,8 @@ In contrast, the same **Get-Mailbox** cmdlet would return at least 230 propertie
 
 For details about the property sets that are available in EXO V2 module cmdlets, see [Property sets in Exchange Online PowerShell V2 cmdlets](cmdlet-property-sets.md) or the individual EXO V2 module cmdlet reference topics.
 
-EXO cmdlets also provide a way to retrieve all properties for an object by using the _ProperySets_ parameter with the value `All`.
-
-The following example returns all properties for the 10 mailboxes:
-
-```PowerShell
-Get-EXOMailbox -ResultSize 10 -PropertySets All
-```
-
 > [!NOTE]
-> We highly discourage using the _PropertySets_ parameter with the value `All` because it slows down the cmdlet and reduces reliability. Always use the _PropertySets_ and _Properties_ parameters to retrieve only the required properties.
+> Although you can retrieve all properties for an object by using the _PropertySets_ parameter with the value All, we highly discourage this because it slows down the cmdlet and reduces reliability. Always use the _PropertySets_ and _Properties_ parameters to retrieve the minimum number of properties.
 
 For more information about filtering in the EXO V2 module, see [Filters in the Exchange Online V2 module](filters-v2.md).
 
@@ -325,7 +311,7 @@ For more information about filtering in the EXO V2 module, see [Filters in the E
 
 - Use EXO V2 cmdlets even if WinRM Basic Auth is disabled on client machine. Note that remote PowerShell cmdlets require WinRM Basic Auth, and they won't be available if it's disabled.
 
--  Identity parameter for V2 cmdlets now supports Name and Alias as well. Note that using Alias or Name slows down the performance of V2 cmdlets, so we don't recommend using them.
+- Identity parameter for V2 cmdlets now supports Name and Alias as well. Note that using Alias or Name slows down the performance of V2 cmdlets, so we don't recommend using them.
 
 - Fixed issue where the data type of attributes returned by V2 cmdlet was different from remote PowerShell cmdlets. We still have few attributes which have differing data types, and we plan to handle them in coming months.