updates

Author: jansenbe

docs/transform/modernize-connect-to-office365-group-scanner.md

@@ -7,7 +7,7 @@ ms.prod: sharepoint
 
 # Understand and process the scanner results
 
-To help you understand which sites are ready to be group-connected, you can use the [SharePoint Modernization Scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization) to analyze your environment. Use this article to understand how you can use the scanner output to prepare your sites for being connected to an Office 365 group. The scanner as of version 1.5 will generate an Excel report plus several CSV files. It's recommended to use the Excel based dashboard to review the scanner data and when needed use the CSV data for more in depth data.
+To help you understand which sites are ready to be group-connected, you can use the [SharePoint Modernization Scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization) to analyze your environment. Use this article to understand how you can use the scanner output to prepare your sites for being connected to an Office 365 group. The scanner, as of version 1.5, will generate an Excel report plus several CSV files. It's recommended to use the Excel based dashboard to review the scanner data and when needed use the CSV data for more in depth data.
 
 ## Using the "Office 365 Group Connection Readiness" report
 
@@ -44,20 +44,20 @@ With that filter applied let's have a look at the typical warnings:
 
 ![Office 365 Group connection warnings](media/modernize/groupifyscanner_ready_5.png)
 
-- **SiteHasSubSites**: A group is connected to the root site of the site collection and not to individual sub sites. Having sub sites is fully supported but you can't use group connected services on your sub sites
-- **ModernUIIssues**: Since connecting to a group brings a modern home page this might result in existing customizations being "ignored" on that modern home page. You can optionally stick with your "current" home page if you run Office 365 Group connection using the API's or using the "bulk Office 365 Group connection" scripts.
-- **DefaultHomePageImpacted**: The default home page based upon this site's web template differs a lot from the new home page you get by connecting to a group. You can optionally stick with your "current" home page if you run Office 365 Group connection using the API's or using the "bulk Office 365 Group connection" scripts.
-- **ADGroupWillNotBeExpanded**: The site uses AD groups to grant access and the permissions granted via AD groups are not taken over by the Office 365 group. You can optionally "expand" the AD group and add the individual members to the respective Office 365 Group Owners and Members.
+- **SiteHasSubSites**: A group is connected to the root site of the site collection and not to individual sub sites. In the modern team and communication sites, the use of subsites is de-emphasized but having sub sites is fully supported. Important to understand is that you can't use group connected services on your sub sites.
+- **ModernUIIssues**: Since connecting to a group brings a modern home page this might result in existing customizations being "ignored" on that modern home page. The details of which modern UI issues were found by the scanner can be found in the next section. You can optionally stick with your "current" home page if you run Office 365 Group connection using the API's or using the "bulk Office 365 Group connection" scripts.
+- **DefaultHomePageImpacted**: The default home page based upon this site's web template differs a lot from the new home page you get by connecting to a group. You can optionally stick with your "current" home page if you run Office 365 Group connection using the API's or using the "bulk Office 365 Group connection" scripts. Another alternative is creating a new modern home page, as is shown in the "bulk Office 365 Group connection" script.
+- **ADGroupWillNotBeExpanded**: When you group-connect via the user interface, you have an option to define the Office 365 group's owners and members; when you bulk group-connect, the sample script explained later does the same. However, because an Office 365 group can only contain persons as Owners or Members, this means that if today you granted access to your SharePoint site by using an Azure Active Directory (Azure AD) security group, you can't add that Azure AD security group as an Office 365 group owner or member. If you want to only rely on the permissions defined on the Office 365 group, you must add all individual Azure AD group members as part of the group-connection process, but having identical access defined on both the SharePoint site and the Office 365 group is not needed, making this not a blocking issue.
 
 ### Modern UI Warnings
 
 ![Detailed modern UI warnings](media/modernize/groupifyscanner_ready_6.png)
 
-- **MasterPageUsed** or **AlternateCSSUsed**: These settings are ignored on any modern page. If your site is not using any classic pages anymore it's recommended to move away from custom master pages and alternate CSS. Checkout the [Modernize branding](modernize-branding.md) article to learn more.
-- **UserCustomActionUsed**: If you need to functionality offered by these user custom actions then you need to redesign those using SharePoint Framework extensions and deploy them. See the ModernizationUserCustomActionScanResults.csv for more details and checkout the [Modernize customizations](modernize-customizations.md) article for more details.
-- **PublishingFeatureEnabled**: Publishing features are not supported in combination with modern pages.
-- **ModernPageFeatureDisabled**: Modern pages have been disabled at web level and since by default your site will get a modern home page after being connected to an Office 365 Group it's highly recommended to enable the modern page feature.
-- **ModernListsBlockedAtSiteLevel** or **ModernListsBlockedAtWebLevel**: Modern list and library user interface was disabled at site or web level. Given your site by default will get a modern home page it's recommended to not block the modern user interface for lists and libraries.
+- **MasterPageUsed** or **AlternateCSSUsed**: Custom master pages or alternate CSS is not used on modern pages. If your site depends on these, you might want to verify that, because your custom master pages and CSS will not work on the modern home page that the site gets. Checkout the [Modernize branding](modernize-branding.md) article to learn more.
+- **UserCustomActionUsed**: Using user custom actions that embed JavaScript is common for customizing sites, but this does not work for modern pages. If you have user custom actions, you can build alternatives by using SharePoint Framework Extensions and install those to your site. See the ModernizationUserCustomActionScanResults.csv and checkout the [Modernize customizations](modernize-customizations.md) article for more details.
+- **PublishingFeatureEnabled**: The publishing features are not compatible with the modern page feature, which is a requirement due to the modern home page being set.
+- **ModernPageFeatureDisabled**: Because the site gets a modern home page after group-connection creation, it's important that the modern homepage feature is enabled.
+- **ModernListsBlockedAtSiteLevel** or **ModernListsBlockedAtWebLevel**: Preventing the modern user interface for lists and libraries is not blocking group-connection, but because group-connection is typically part of a site modernization, it makes no sense to prevent lists and libraries to use the modern user interface on an Office 365 group-connected site.
 
 ### Permission Warnings
 
@@ -73,7 +73,7 @@ Apply the following filter and confirm the "Sites ready for Office 365 Group con
 
 Filter | Validation
 ---------|----------
-![Sites not ready filter](media/modernize/groupifyscanner_notready_1.png) | ![Sites not ready graph](media/modernize/groupifyscanner_ready_2.png)
+![Sites not ready filter](media/modernize/groupifyscanner_notready_1.png) | ![Sites not ready graph](media/modernize/groupifyscanner_notready_2.png)
 
 At this point you have a list of all sites which are not ready to be connected to an Office 365 Group, so let's analyze why they're not. The key site to connect to an Office 365 group is the "classic" team site, so let's filter on those first: