Merge pull request #879 from prgundel/patch-4

Addressing build issues and quality problems in sharepoint-online documentation

Author: Ruchika-mittal01

sharepoint/docs-conceptual/sharepoint-online/connect-sharepoint-online.md

@@ -1,5 +1,8 @@
 ---
+manager: mengkel
+ms.author: samkabue
 title: Get started with the SharePoint Online Management Shell
+description:  Get started with the SharePoint Online Management Shell
 ---
 
 # Get started with SharePoint Online Management Shell #

sharepoint/docs-conceptual/sharepoint-online/introduction-sharepoint-online-management-shell.md

@@ -1,4 +1,6 @@
 ---
+manager: mengkel
+ms.author: samkabue
 title: Intro to SharePoint Online Management Shell
 description: Intro to SharePoint Online Management Shell
 ---
@@ -32,4 +34,4 @@ After you get familiar with SharePoint sites and users, try using SharePoint Onl
 
 ## How do I get permissions and set up the environment?
 
-To use SharePoint Online PowerShell commands, you must be a SharePoint admin in your organization. For info about installing the SharePoint Online Management Shell module and connecting to the SharePoint Online service, see [Get started with SharePoint Online Management Shell](connect-sharepoint-online.md)
+To use SharePoint Online PowerShell commands, you must be a SharePoint admin in your organization. For info about installing the SharePoint Online Management Shell module and connecting to the SharePoint Online service, see [Get started with SharePoint Online Management Shell](connect-sharepoint-online.md).

sharepoint/sharepoint-ps/sharepoint-online/Invoke-SPOSiteSwap.md

@@ -5,8 +5,7 @@ online version: https://learn.microsoft.com/powershell/module/sharepoint-online/
 applicable: SharePoint Online
 title: Invoke-SPOSiteSwap
 schema: 2.0.0
-author: WayneEwington
-ms.author: waynewin
+ms.author: divyasru
 ms.reviewer:
 ---
 
@@ -35,14 +34,14 @@ Swaps the location of a source site with a target site while archiving the origi
 
 Please note, the target site must be either:
 
-- The root site, for example <https://tenant-name.sharepoint.com>; or
-- The search center site, for example <https://tenant-name.sharepoint.com/search>.
+- The root site, for example `https://tenant-name.sharepoint.com`; or
+- The search center site, for example `https://tenant-name.sharepoint.com/search`.
 
 When the swap is initiated, the target site is moved to the archive location and the source site is moved to the target location. By default, a site redirect is created at the source location that will redirect traffic to the target location.
 
-If the target is the root site at <https://tenant-name.sharepoint.com>, then the following preparation activities should be performed prior to performing the swap:
+If the target is the root site at `https://tenant-name.sharepoint.com`, then the following preparation activities should be performed prior to performing the swap:
 
-1. Any Featured links defined in SharePoint Start Page at <https://tenant-name.sharepoint.com/_layouts/15/sharepoint.aspx> will not be displayed after performing the swap. If required, the Featured links should be documented so they can be manually recreated after the swap.
+1. Any Featured links defined in SharePoint Start Page at `https://tenant-name.sharepoint.com/_layouts/15/sharepoint.aspx` will not be displayed after performing the swap. If required, the Featured links should be documented so they can be manually recreated after the swap.
 2. Functionality such as external sharing and application interfaces are dependent on the policies and permissions defined at the root site. Review the source site to ensure that it has the required policies and permissions as per the existing root site. This includes external sharing settings as well as site permissions.
 3. Larger tenants that have more than ~10,000 licenses will need to run the [Page Diagnostic Tool](/office365/enterprise/page-diagnostics-for-spo) against the source site (ensure that the user running the Page Diagnostic Tool has edit rights on the source site). Any analysis results that have the category Attention required (Red) or Improvement opportunities (Orange) will need to be remediated before performing the swap. 
 
@@ -91,9 +90,9 @@ Archives the existing Search Center site at <https://contoso.sharepoint.com/sear
 
 URL of the source site. The site at this location must exist before performing the swap.
 
-If the target is the root site at <https://tenant-name.sharepoint.com> then the source site must be either a Modern Team Site (STS#3) or a Communication Site (SITEPAGEPUBLISHING#0) and **the publishing feature can never have been activated on the source site**.
+If the target is the root site at `https://tenant-name.sharepoint.com` then the source site must be either a Modern Team Site (STS#3) or a Communication Site (SITEPAGEPUBLISHING#0) and **the publishing feature can never have been activated on the source site**.
 
-If the target is the search center site at <https://tenant-name.sharepoint.com/search> then the source site must be either a Search Center Site (SRCHCEN#0) or a Basic Search Center Site (SRCHCENTERLITE#0).
+If the target is the search center site at `https://tenant-name.sharepoint.com/search` then the source site must be either a Search Center Site (SRCHCEN#0) or a Basic Search Center Site (SRCHCENTERLITE#0).
 
 ```yaml
 Type: String
@@ -114,8 +113,8 @@ URL of the target site that the source site will be swapped to. The site at this
 
 The target site must be either:
 
-- The root site at <https://tenant-name.sharepoint.com> or
-- The search center site at <https://tenant-name.sharepoint.com/search.>
+- The root site at `https://tenant-name.sharepoint.com` or
+- The search center site at `https://tenant-name.sharepoint.com/search`
 
 ```yaml
 Type: String

sharepoint/sharepoint-ps/sharepoint-online/New-SPOMigrationPackage.md

@@ -14,7 +14,8 @@ ms.reviewer:
 
 ## SYNOPSIS
 
-**Note**: This cmdlet has been deprecated. To migrate to SharePoint and Microsoft 365 using PowerShell, see [Migrate to SharePoint using PowerShell](https://learn.microsoft.com/sharepointmigration/overview-spmt-ps-cmdlets).
+> [!NOTE]
+> This cmdlet has been deprecated. To migrate to SharePoint and Microsoft 365 using PowerShell, see [Migrate to SharePoint using PowerShell](https://learn.microsoft.com/sharepointmigration/overview-spmt-ps-cmdlets).
 
 Cmdlet to create a new migration package based on source files in a local or network shared folder.
 
@@ -223,7 +224,7 @@ Accept wildcard characters: False
 
 ### -TargetWebUrl
 
-The fully qualified web URL to use as the web address part of the base URL in the package metadata. If this is not provided, "<http://fileserver/sites/user"> will be used instead within the package metadata.
+The fully qualified web URL to use as the web address part of the base URL in the package metadata. If this is not provided, "`http://fileserver/sites/user`" will be used instead within the package metadata.
 
 ```yaml
 Type: String

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md

@@ -775,8 +775,7 @@ The valid values are:
 - True (default) - The Shared with Everyone folder is created.  
 - False - No folder is created when the site and OneDrive for Business document library is created.
 
-The default behavior of the Shared with Everyone folder changed in August 2015.  
-For additional information about the change, see [Provision the Shared with Everyone folder in OneDrive for Business](https://support.office.com/article/Provision-the-Shared-with-Everyone-folder-in-OneDrive-for-Business-6bb02c91-fd0b-42ba-9457-3921cb6dc5b2).
+The default behavior of the Shared with Everyone folder changed in August 2015.
 
 ```yaml
 Type: Boolean