article polishing

Author: jansenbe

docs/transform/modernize-classic-sites.md

@@ -1,49 +1,49 @@
 # Introduction
 
-SharePoint Online is continuously evolving and improving, which is a great thing for you as consumer from the service. One of the key improvements is the availability of modern sites, being modern Office 365 Group connected team sites or communication sites, combined with more and more functionality that can be consumed from a beautiful modern user interface. All of this is great...but you might ask yourself the question: "I've lots of classic (team) sites...how do I bring those into the modern SharePoint world?". There's no magic switch that automatically transforms your classic sites into modern sites, but it possible to transform a classic site into a modern site following the guidance described in this article series.
+SharePoint Online is continuously evolving and improving, which is a great thing for you as consumer from the service. One of the key improvements is the availability of modern sites, being modern Office 365 Group connected team sites or communication sites, combined with more and more functionality that can be consumed from a beautiful modern user interface. All of this is great...but you might ask yourself the question: "I've lots of classic (team) sites...how do I bring those into the modern SharePoint world?". There's no magic switch that automatically transforms your classic sites into modern sites, but it is possible to transform a classic site into a modern site following the guidance described in this article series.
 
 ## Steps in a site modernization
 
-If you want to transform (or also referred to as "modernize") a classic site into a modern group connected site then you can do this by following the below outlined steps.
+If you want to transform (or also referred to as "modernize") a classic site into a modern Office 365 Group connected site then you can do this by following the below outlined steps.
 
 ### Enable your sites to fully leverage the modern user interface
 
-The most visible aspect of modern sites is obviously it's modern user interface. If you've not turned of the modern experience at tenant level (**SharePoint Lists and Libraries experience** setting in tenant admin center) then already certain pages will show up using a modern user interface:
+The most visible aspect of a modern site is obviously it's modern user interface. If you've not turned of the modern experience at tenant level (**SharePoint Lists and Libraries experience** setting in tenant admin center) then already certain pages will show up using a modern user interface:
 
-- List and library pages for most list and libraries
+- List and library pages for most lists and libraries
 - Site Contents page
 - Site Usage page
 - Recycle Bin pages
 
-If you scan over your site you'll however notice that following pages are still shown using the classic user interface:
+If you navigate your site you'll however notice that following pages are still shown using the classic user interface:
 
-- Home page and all other site pages
+- Home page and all other site pages (wiki pages and/or web part pages)
 - List and library pages for certain lists and libraries
 
 If you want to maximize the use of the modern user interface for your site pages plus list and library pages then checkout the [Modernize your user interface](modernize-userinterface.md) article. During this user interface you'll modernization you will also have to handle the modernization of your customizations as explained in [Modernize your customizations](modernize-customizations.md).
 
 ### Connect your sites to Office 365 Groups
 
-Classic (team) sites are not connected to an Office 365 Group whereas modern team sites are: the connection to an Office 365 Group does open the site to consume other Office 365 Services like Teams, Planner, Outlook,...So connecting your sites to an Office 365 Group is an essential part of a site modernization. There are two options to make this happen:
+Classic (team) sites are not connected to an Office 365 Group whereas modern team sites are: the connection to an Office 365 Group does open up the site for consuming other Office 365 Services like Teams, Planner, Outlook,...So connecting your site to an Office 365 Group is an essential part of a site modernization. There are two options to make this happen:
 
 - You can have each site owner do this on their behalf using a wizard that can be launched from the user interface
-- You perform a bulk operation in which you connect an Office 365 Group to a series of sites in one go
+- You perform a bulk operation in which you connect an Office 365 Group to a series of sites in one go. This option is the preferred one for enterprise customers as it will allow you to control the used configuration (public/private, site classification, alias name)
 
 You can read up on all the details needed to make this happen in our [Connect to Office 365 Group](modernize-connect-to-office365-group.md) article.
 
 ### Switch to a modern tenant scoped branding
 
-Having SharePoint (team) sites use your company branding is a very common thing and for classic sites you've used one or more of the following component: site themes, CSS and master pages. Master pages and CSS are however not compatible with the modern user interface, so you will need to evaluate if these branding customizations are still relevant or not. Classic site themes are respected in a modern user interface but since we now have tenant controlled site theming switching over to that model will future proof your modernized site.
+Having SharePoint (team) sites use your company branding is a very common thing and for classic sites you've used one or more of the following components: site themes, alternate CSS and master pages. Master pages and alternate CSS are however not compatible with the modern user interface, so you will need to evaluate whether these branding customizations are still relevant or not. Classic site themes are respected in a modern user interface but since we now have tenant controlled site theming, switching over to that model will future proof your modernized site.
 
 Learn more via the [Modernize your site branding](modernize-branding.md) article.
 
 ## What process to follow
 
-There's **no one size fits all process** for site modernization: the previous chapter introduced the possible steps in a site modernization but whether you run all steps and in which order you run them is up to you to decide. Although there's no one size fits all process there's a recommended approach for site modernization:
+There's **no one size fits all process** for site modernization: the previous chapter introduced the steps in a site modernization but whether you run all steps and if so in which order you run them is up to you to decide. Although there's no one size fits all process there's a recommended approach for site modernization:
 
 ### Step 1: Enable the out-of-the-box modern user interface for lists and libraries
 
-Given you typically already have this enabled at tenant level and are already using this option it makes sense to further maximize the use. SharePoint will try to show your lists and libraries using the modern user interface but you might have customizations / configurations that prevent this. Checkout the [Maximize your use of the modern list and library user interface](modernize-userinterface-lists-and-libraries.md) article to learn more about how to unblock your lists and libraries for using the modern user interface.
+Given you typically already have this enabled at tenant level it makes sense to further maximize the use. SharePoint will try to show your lists and libraries using the modern user interface but you might have customizations and/or configurations that prevent this. Checkout the [Maximize your use of the modern list and library user interface](modernize-userinterface-lists-and-libraries.md) article to learn more about how to unblock your lists and libraries for using the modern user interface.
 
 ### Step 2: Connect your site to an Office 365 Group + switch to modern branding when needed
 

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

@@ -112,6 +112,9 @@ To help you verify this file before using it you can use below PowerShell script
 - **[ERROR] _siteUrl_ : Alias [_siteAlias_] was already marked as approved alias for another site in this file**: The proposed site alias was already defined for another site in earlier input lines of the bulk "groupify" CSV file
 - **[ERROR] _siteUrl_ : Site does not exist or is not available (status = _site.Status_)**: The provided site URL does not represent a reachable site collection
 
+> [!NOTE]
+> Please update the `$tenantAdminUrl` variable in the script to contain your tenant admin center URL (e.g. https://contoso-admin.sharepoint.com).
+
 [!code-powershell[validategroupifyinput](../../PnP-Tools/Solutions/SharePoint.Modernization/Scripts/Groupify/ValidateInput.ps1 "Validate groupify input file")]
 
 During script execution a log file will be generated combined with an error file which contains a subset of the log file (only the errors).
@@ -135,7 +138,8 @@ Now that we've an input file that's defining the sites that need to be "groupifi
 Running the below PowerShell script requires you to update the tenant admin center URL and at run time provide credentials and the CSV input file.
 
 > [!NOTE]
-> This is a sample script that you need to address to your needs by updating/dropping the **optional** parts or by adding additional modernization tasks (like setting a SharePoint site theme)
+> This is a sample script that you need to address to your needs by updating/dropping the **optional** parts or by adding additional modernization tasks (like setting a SharePoint site theme). Please update the `$tenantAdminUrl` variable in the script to contain your tenant admin center URL (e.g. https://contoso-admin.sharepoint.com).
+
 
 [!code-powershell[bulkgroupify](../../PnP-Tools/Solutions/SharePoint.Modernization/Scripts/Groupify/GroupifySite.ps1 "Bulk groupify sites")]
 

docs/transform/modernize-customizations.md

@@ -1,10 +1,10 @@
 # Introduction
 
-An important aspect of a site modernization is understanding the customizations that are used on that site as not all existing customizations continue to work after the site modernization. A classic example we see coming back a lot is a site banner showing some company information (e.g. a legal notice). This typically is realized via user custom action that embeds JavaScript on the page which on it's turn is responsible for showing the banner. This banner is visible on all classic pages, but will not be visible on modern pages. To workaround this problem you can implement the banner as a SharePoint Framework Application customizer extension and deploy that one to the site. In the article you'll get an overview of the customizations which are not compatible with the modern user interface and guidelines on how to remediate.
+An important aspect of a site modernization is understanding the customizations that are used on that site as not all existing customizations continue to work after the site modernization. A classic example we see coming back a lot is a site banner showing some company information (e.g. a legal notice). This typically is realized via user custom action that embeds JavaScript on the page which on it's turn is responsible for showing the banner. This banner is visible on all classic pages, but will not be visible on modern pages. To workaround this problem you can implement the banner as a SharePoint Framework Application customizer extension and deploy that one to the tenant/site. In this article you'll get an overview of the customizations which are not compatible with the modern user interface and guidelines on how to remediate.
 
 ## Customizations being used in list and libraries
 
-This chapter focusses on customizations that you might have implemented on your lists and libraries. In the SharePoint classic user interface you could actually edit the the list and library pages, but in the modern user experience this is not possible anymore. Moreover SharePoint will automatically fallback to the classic list and library user interface when it detects an incompatible customization, hence it's important to address these if you want to get 100% modern experience. The [SharePoint "Modern" user interface experience scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.UIExperience.Scanner) will help you get a deep understanding on the modern user interface compatibility of your lists and libraries.
+This chapter focusses on customizations that you might have implemented on your lists and libraries. SharePoint will automatically fallback to the classic list and library user interface when it detects an incompatible customization, hence it's important to address these if you want to get a 100% modern experience. The [SharePoint "Modern" user interface experience scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.UIExperience.Scanner) will help you get a deep understanding on the modern user interface compatibility of your lists and libraries.
 
 ### The use of JSLink
 
@@ -42,7 +42,7 @@ To learn more about SharePoint Framework (field customizer) extensions check out
 
 ### List scoped user custom actions that embed JavaScript or add custom menu options in the list ribbon or context menu
 
-Using a list user custom action that adds custom menu options or embeds JavaScript is next to JSLink a very common customization pattern which does not work anymore for the modern list and library experience. Luckily using SharePoint Framework Extensions you can realize similar customizations, more in particular via command set extension which allows you to add custom ECB menu items or custom buttons to the command bar of a list view for a list or a library. You can associate any JavaScript (TypeScript) action to these commands.
+Using a list user custom action that adds custom menu options or embeds JavaScript is next to JSLink a very common customization pattern which does not work anymore for the modern list and library experience. Luckily using SharePoint Framework Extensions you can realize similar customizations, more in particular via command set extensions which allows you to add custom ECB menu items or custom buttons to the command bar of a list or library. You can associate any JavaScript (TypeScript) action to these commands.
 
 ![List view command set](media/modernize/spfx-listview-commandset-doc-select.png)
 

docs/transform/modernize-userinterface-lists-and-libraries.md

@@ -1,6 +1,6 @@
 # Maximize your use of the modern list and library user interface
 
-Getting the maximum amount of lists and libraries present themselves using the modern user interface is the topic of this article. You might wonder "why not all lists and libraries?"...there's certain types of lists and libraries which are not (yet) built by the SharePoint team to show up in a modern user interface. Samples are a Task list, Events list,...For these you'll have to wait for the SharePoint team to implement a modern version or switch over to equivalent options like use Microsoft Planner instead of a classic task list or use the calendar of your Office 365 group instead of a classic SharePoint calendar. That being said there's also a category of lists and libraries that can be shown in modern but are blocked due to an incompatible configuration or customization.
+Getting the maximum amount of lists and libraries present themselves using the modern user interface is the topic of this article. You might wonder "why not all lists and libraries?"...there's certain types of lists and libraries which are not (yet) built by the SharePoint team to show up in a modern user interface. Samples are a Task list, Events list,...For these you'll have to wait for the SharePoint team to implement a modern version or switch over to equivalent options like using Microsoft Planner instead of a classic task list or using the calendar of your Office 365 group instead of a classic SharePoint events list calendar. That being said there's also a category of lists and libraries that can be shown in modern but are blocked due to an incompatible configuration or customization...and you can take action here.
 
 ## Detecting lists and libraries that will not use the modern user interface
 
@@ -21,12 +21,12 @@ To fix these blockers you can either remove the customization (in case it's not
 
 ## Fields of type BCS external data, Geolocation, OutcomeChoice, Image, Html, or SummaryLinks
 
-Certain field types (BCS external data, Geolocation, OutcomeChoice in edit mode, Image, Html and SummaryLinks) are not (yet) built to work in a modern user interface. To remediate these you can follow these approaches:
+Certain field types (BCS external data, Geolocation, OutcomeChoice in edit mode, Image, Html and SummaryLinks) are not (yet) built to work in a modern user interface. To remediate these you can apply below approaches:
 
-- Remove the field from the views: the field is still there in edit mode (so you get a classic edit experience)
+- Remove the field from the views: the field is still there, so you get a classic edit experience but at least the views are modern
 - Migrate the fields data into a new field which is compatible with modern
 - Completely drop the field if it's not being used
 
-## Having customized list view pages containing more than the list XSLTListViewWebPart
+## Having customized list view pages containing more than just the list XSLTListViewWebPart
 
 Classic list view and edit pages are editable by users, so you could for example add additional web parts on a list view page. If you've done that then the list will not show anymore in modern. To remediate this the only approach you can follow is to drop the added web parts from the list pages.