Merge pull request Azure#891 from tajaber/patch-1

Update BlockCloudObjectTakeoverThroughHardMatch explanation

Author: CelesteDG

azureadps-1.0/MSOnline/Set-MsolDirSyncFeature.md

@@ -27,12 +27,12 @@ You can use the following synchronization features with this cmdlet:
 - **PasswordSync**
 - **SynchronizeUpnForManagedUsers**: Allows for the synchronization of UserPrincipalName updates from on-premises for managed (non-federated) users that have been assigned a license. These updates will be blocked if this feature isn't enabled. Once this feature is enabled, it can't be disabled.
 - **BlockSoftMatch**: When this feature is enabled, it will block the soft match feature. Customers are encouraged to enable this feature and keep it enabled until soft matching is required again for their tenancy. This flag should be enabled again after any soft matching has completed and is no longer needed.
-- **BlockCloudObjectTakeoverThroughHardMatch**: When this feature is enabled, and
+- **BlockCloudObjectTakeoverThroughHardMatch**: When this feature is not enabled, and
 
     -  an object is synced for which an object with a matching source anchor already exists in Azure AD and,
     - that object in Azure AD doesn't have DirSyncEnabled set to "true", then
 
-    the default behavior would be to hard match the cloud object with the on premises object and set the DirSyncEnabled flag of the Cloud object to "true". <br>
+    the default behavior would be to hard match the cloud object with the on premises object and set the DirSyncEnabled flag of the Cloud object to "true". <br><br>
     When enabling this feature, the cloud object is no longer matched and the DirSyncEnabled flag isn't set to "true". Instead, an error is thrown: Error Code: `InvalidHardMatch`, Error Message: `Another cloud created object with the same source anchor already exists in Azure Active Directory`.
 
 Enabling some of these features, such as EnableSoftMatchOnUpn and SynchronizationUpnForManagedUsers, is a permanent operation.