Update Sandbox-Solution-Transformation-Guidance.md

Author: DhurataJ

docs/solution-guidance/Sandbox-Solution-Transformation-Guidance.md

@@ -87,7 +87,7 @@ Following are typical customizations that are included in the sandbox solutions
 |Web part|<p>Web parts are typically converted either to add-in parts or they are implemented with fully client-side technologies by using the JavaScript embed pattern. </p><p>For more information, see:<lu><li>[Customize your SharePoint site UI by using JavaScript](customize-your-sharepoint-site-ui-by-using-javascript.md)</li><li>[Create add-in parts to install with your SharePoint Add-in](../sp-add-ins/create-add-in-parts-to-install-with-your-sharepoint-add-in.md)</li><li>[How to update your SharePoint pages via the embedding of JavaScript](https://channel9.msdn.com/blogs/OfficeDevPnP/JavaScript-embedding-demo)</li><li>[Cross site collection navigation](https://channel9.msdn.com/blogs/OfficeDevPnP/Cross-site-collection-navigation)</li></lu></p>|
 |Visual web part|<p>Visual web parts are transformed in similar ways as normal web parts. User controls used in visual web parts must be replaced because in sandbox solution cases, it's included inside of the assembly.</p>|
 |Event receiver|<p>Event receivers can in many cases be replaced with the remote event receiver implementation. Remote event receivers do, however, need to hosted on some platform, typically on specific provider-hosted add-ins.</p><p>For more information, see:<lu><li>[Use remote event receivers in SharePoint](use-remote-event-receivers-in-sharepoint.md)</li><li>[How to use remote event receivers for your SharePoint add-ins](https://channel9.msdn.com/blogs/OfficeDevPnP/How-to-use-remote-event-receivers-for-your-SharePoint-add-ins)</li></lu></p>|
-|Feature receiver|<p>Feature receivers are typically replaced with a remote API based operation, such as using CSOM or REST for applying the needed customization or configuration at the site level. If a needed API is missing from the remote APIs (CSOM/REST), report this gap by using SharePoint UserVoice.</p><p>Feature receivers are used, for example, to set a custom master page or theme to a site when they are activated. These kinds of operations can be easily replaced with remote code-based solutions or by using [SharePoint UserVoice](https://sharepoint.uservoice.com/), which provides easy commands for controlling site configuration.</p>|
+|Feature receiver|<p>Feature receivers are typically replaced with a remote API based operation, such as using CSOM or REST for applying the needed customization or configuration at the site level. If a needed API is missing from the remote APIs (CSOM/REST), report this gap by using [SharePoint UserVoice](https://sharepoint.uservoice.com/).</p><p>Feature receivers are used, for example, to set a custom master page or theme to a site when they are activated. These kinds of operations can be easily replaced with remote code-based solutions or by using [PnP PowerShell](https://github.com/SharePoint/PnP-PowerShell/blob/master/README.md), which provides easy commands for controlling site configuration.</p>|
 |Custom workflow action|<p>The typical code migration path for these kinds of customizations is to use SharePoint workflows or alternative solutions such as Microsoft Flow or third-party solutions.</p>| 
 
 ## Removing sandbox code from your site