rewrite provider topics into about files for 6.0

.openpublishing.redirection.json

@@ -374,6 +374,136 @@
             "redirect_url": "/powershell/scripting/powershell-scripting",
             "redirect_document_id": "False"
         },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Core/Providers/FileSystem-Provider/Add-Content-for-FileSystem.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Core/Providers/about_FileSystem_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Core/Providers/FileSystem-Provider/Clear-Content-for-FileSystem.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Core/Providers/about_FileSystem_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Core/Providers/FileSystem-Provider/Get-ChildItem-for-FileSystem.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Core/Providers/about_FileSystem_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Core/Providers/FileSystem-Provider/Get-Content-for-FileSystem.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Core/Providers/about_FileSystem_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Core/Providers/FileSystem-Provider/Get-Item-for-FileSystem.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Core/Providers/about_FileSystem_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Core/Providers/FileSystem-Provider/Remove-Item-for-FileSystem.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Core/Providers/about_FileSystem_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Core/Providers/FileSystem-Provider/Set-Content-for-FileSystem.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Core/Providers/about_FileSystem_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Core/Providers/FileSystem-Provider/Test-Path-for-FileSystem.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Core/Providers/about_FileSystem_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Security/Providers/get-childitem-for-certificate.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Security/Providers/about_Certificate_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Security/Providers/move-item-for-certificate.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Security/Providers/about_Certificate_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Security/Providers/new-item-for-certificate.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Security/Providers/about_Certificate_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Security/Providers/remove-item-for-certificate.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Security/Providers/about_Certificate_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.WSMan.Management/Providers/New-Item-for-ClientCertificate.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Security/Providers/about_Certificate_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.WSMan.Management/Providers/New-Item-for-InitializationParameters.md",
+            "redirect_url": "/powershell/module/Microsoft.WSMan.Management/Providers/about_WSMan_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.WSMan.Management/Providers/New-Item-for-Listener.md",
+            "redirect_url": "/powershell/module/Microsoft.WSMan.Management/Providers/about_WSMan_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.WSMan.Management/Providers/New-Item-for-Plugin.md",
+            "redirect_url": "/powershell/module/Microsoft.WSMan.Management/Providers/about_WSMan_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.WSMan.Management/Providers/New-Item-for-Resources.md",
+            "redirect_url": "/powershell/module/Microsoft.WSMan.Management/Providers/about_WSMan_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.WSMan.Management/Providers/New-Item-for-Security.md",
+            "redirect_url": "/powershell/module/Microsoft.WSMan.Management/Providers/about_WSMan_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Core/Providers/Alias-Provider.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Core/Providers/about_Alias_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Core/Providers/Environment-Provider.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Core/Providers/about_Environment_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Core/Providers/FileSystem-Provider.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Core/Providers/about_FileSystem_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Core/Providers/Function-Provider.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Core/Providers/about_Function_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Core/Providers/Registry-Provider.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Core/Providers/about_Registry_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Core/Providers/Variable-Provider.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Core/Providers/about_Variable_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.PowerShell.Security/Providers/Certificate-Provider.md",
+            "redirect_url": "/powershell/module/Microsoft.PowerShell.Security/Providers/about_Certificate_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference/6/Microsoft.WSMan.Management/Providers/WSMan-Provider.md",
+            "redirect_url": "/powershell/module/Microsoft.WSMan.Management/Providers/about_WSMan_Provider?view=powershell-6",
+            "redirect_document_id": false
+        },
         {
             "source_path": "reference/virtual-directory/core-powershell/ise/using-the-windows-powershell-ise.md",
             "redirect_url": "/powershell/scripting/core-powershell/ise/introducing-the-windows-powershell-ise",

reference/3.0/Microsoft.PowerShell.Management/Get-Content.md

@@ -1,4 +1,3 @@
-
 ---
 ms.date:  06/09/2017
 schema:  2.0.0
@@ -119,7 +118,7 @@ $Hash
 ```output
 Name                           Value
 ----                           -----
-Copyright                      � Microsoft Corporation. All rights reserved.
+Copyright                      © Microsoft Corporation. All rights reserved.
 ModuleToProcess                Microsoft.PowerShell.ScheduledJob.dll
 FormatsToProcess               PSScheduledJob.Format.ps1xml
 PowerShellVersion              3.0

reference/3.0/Microsoft.PowerShell.Management/New-PSDrive.md

@@ -33,26 +33,22 @@ However, because temporary drives are known only to PowerShell, you cannot acces
 
 The following features are added to `New-PSDrive` in Windows PowerShell 3.0:
 
-* **Mapped network drives**
-
+- Mapped network drives.
   You can use the **Persist** parameter of `New-PSDrive` to create Windows mapped network drives.
   Unlike temporary PowerShell drives, Windows mapped network drives are not session-specific.
   They are saved in Windows and they can be managed by using standard Windows tools, such as File Explorer and Net Use.
   Mapped network drives must have a drive-letter name and be connected to a remote file system location.
   When your command is scoped locally (no dot-sourcing), the **Persist** parameter does not persist the creation of a **PSDrive** beyond the scope in which the command is running.
   If you are running `New-PSDrive` inside a script, and you want the drive to persist indefinitely, you must dot-source the script.
   For best results, to force a new drive to persist indefinitely, add the **Scope** parameter to your command, and set its value to Global.
-
-* **External drives**
-
+- External drives.
   When an external drive is connected to the computer, PowerShell automatically adds a **PSDrive** to the file system that represents the new drive.
   You do not have to restart PowerShell.
   Similarly, when an external drive is disconnected from the computer, PowerShell automatically deletes the **PSDrive** that represents the removed drive.
+- Credentials for UNC Paths.
 
-* **Credentials for UNC Paths**
-
-  When the value of the **Root** parameter is a UNC path, such as \\\\Server\Share, the credential specified in the value of the **Credential** parameter is used to create the **PSDrive**.
-  Otherwise, **Credential** is not effective when you are creating new file system drives.
+When the value of the **Root** parameter is a UNC path, such as \\\\Server\Share, the credential specified in the value of the **Credential** parameter is used to create the **PSDrive**.
+Otherwise, **Credential** is not effective when you are creating new file system drives.
 
 ## EXAMPLES
 
@@ -70,7 +66,7 @@ P          FileSystem    \\Server01\Public
 
 This command creates a temporary PowerShell drive named P: that is mapped to the \\\\Server01\Public network share.
 
-It uses the *Name* parameter to specify a name for the drive, the *PSProvider* parameter to specify the PowerShell FileSystem provider, and the *Root* parameter to specify the network share.
+It uses the **Name** parameter to specify a name for the drive, the **PSProvider** parameter to specify the PowerShell FileSystem provider, and the **Root** parameter to specify the network share.
 
 When the command finishes, the contents of the \\\\Server01\Public share appear in the P: drive.
 To see them, type: `dir P:`.
@@ -90,9 +86,9 @@ MyDocs     FileSystem    C:\Documents and Settings\User01\My Documents
 This command creates a temporary PowerShell drive that provides quick access to a local directory.
 It creates a drive named MyDocs: that is mapped to the "C:\Documents and Settings\User01\My Documents" directory on the local computer.
 
-It uses *Name* to specify a name for the drive, *PSProvider* to specify the PowerShell FileSystem provider, *Root* to specify the path of the My Documents folder, and the *Description* parameter to create a description of the drive.
+It uses **Name** to specify a name for the drive, **PSProvider** to specify the PowerShell FileSystem provider, **Root** to specify the path of the My Documents folder, and the **Description** parameter to create a description of the drive.
 
-When the command finishes, the contents of the My Documents folder appear in the MyDocs: drive.
+When the command finishes, the contents of the My Documents folder appear in the `MyDocs:` drive.
 To see them, type: `dir MyDocs:`.
 
 ### Example 3: Create a drive for a registry key
@@ -110,9 +106,9 @@ MyCompany  Registry      HKEY_LOCAL_MACHINE\Software\MyCo...
 This command creates a temporary PowerShell drive that provides quick access to a frequently checked registry key.
 It creates a drive named MyCompany that is mapped to the `HKLM\Software\MyCompany` registry key.
 
-It uses *Name* to specify a name for the drive, *PSProvider* to specify the PowerShell Registry provider, and *Root* to specify the registry key.
+It uses **Name** to specify a name for the drive, **PSProvider** to specify the PowerShell Registry provider, and **Root** to specify the registry key.
 
-When the command finishes, the contents of the MyCompany key appear in the MyCompany: drive.
+When the command finishes, the contents of the MyCompany key appear in the `MyCompany:` drive.
 To see them, type: `dir MyCompany:`.
 
 ### Example 4: Create a persisted mapped network drive
@@ -128,14 +124,14 @@ Status       Local     Remote                    Network
 OK           S:        \\Server01\Scripts        Microsoft Windows Network
 ```
 
-This command creates the S mapped network drive on the local computer.
+This command creates the 'S' mapped network drive on the local computer.
 The 'S' drive is mapped to the \\\\Server01\Scripts network share.
 
 The command uses `New-PSDrive` to create the mapped network drive.
 It uses *Persist* to create a Windows mapped network drive that is saved on the local computer.
 
-The command uses *Name* to specify a letter name that Windows accepts and *Root* to specify a location on a remote computer.
-It uses *PSProvider* to specify the FileSystem provider.
+The command uses **Name** to specify a letter name that Windows accepts and **Root** to specify a location on a remote computer.
+It uses **PSProvider** to specify the FileSystem provider.
 
 The resulting drive can be viewed in other PowerShell sessions on the local computer, in Windows Explorer, and in other tools, such as Net Use.
 
@@ -200,7 +196,7 @@ X:                         \\products\public          Disconnected
 
 This example shows the difference between a persistent mapped network drive and a temporary PowerShell drive that is mapped to the same network share.
 
-If you close the PowerShell session and then open a new one, the PSDrive: drive is gone, and the X: drive persists. Therefore, when deciding which method to use to map network drives, consider how you will use the drive, whether it has to be persistent, and whether the drive has to be visible to other Windows features.
+If you close the PowerShell session and then open a new one, the PSDrive: drive is gone, and the `X:` drive persists. Therefore, when deciding which method to use to map network drives, consider how you will use the drive, whether it has to be persistent, and whether the drive has to be visible to other Windows features.
 
 ## PARAMETERS
 
@@ -209,10 +205,10 @@ If you close the PowerShell session and then open a new one, the PSDrive: drive
 Specifies a user account that has permission to perform this action.
 The default is the current user.
 
-Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the `Get-Credential` cmdlet.
+Type a user name, such as "User01" or "Domain01\User01", or enter a **PSCredential** object, such as one generated by the `Get-Credential` cmdlet.
 If you type a user name, this cmdlet prompts you for a password.
 
-Starting in Windows PowerShell 3.0, when the value of the *Root* parameter is a UNC path, you can use credentials to create file system drives.
+Starting in Windows PowerShell 3.0, when the value of the **Root** parameter is a UNC path, you can use credentials to create file system drives.
 This parameter is not supported by all PowerShell providers.
 
 ```yaml
@@ -271,13 +267,13 @@ Indicates that this cmdlet creates a Windows mapped network drive.
 Mapped network drives are saved in Windows on the local computer.
 They are persistent, not session-specific, and can be viewed and managed in File Explorer and other tools.
 
-When you scope the command locally, that is, without dot-sourcing, the *Persist* parameter does not persist the creation of a **PSDrive** beyond the scope in which you run the command.
+When you scope the command locally, that is, without dot-sourcing, the **Persist** parameter does not persist the creation of a **PSDrive** beyond the scope in which you run the command.
 If you run `New-PSDrive` inside a script, and you want the new drive to persist indefinitely, you must dot-source the script.
-For best results, to force a new drive to persist, specify Global as the value of the *Scope* parameterin addition to adding *Persist* to your command.
+For best results, to force a new drive to persist, specify Global as the value of the **Scope** parameter in addition to adding **Persist** to your command.
 
-The name of the drive must be a letter, such as D or E.
-The value of *Root* parameter must be a UNC path of a different computer.
-The value of the *PSProvider* parameter must be FileSystem.
+The name of the drive must be a letter, such as 'D' or 'E'.
+The value of **Root** parameter must be a UNC path of a different computer.
+The value of the **PSProvider** parameter must be FileSystem.
 
 To disconnect a Windows mapped network drive, use the `Remove-PSDrive` cmdlet.
 When you disconnect a Windows mapped network drive, the mapping is permanently deleted from the computer, not just deleted from the current session.
@@ -397,7 +393,7 @@ Accept wildcard characters: False
 
 Includes the command in the active transaction.
 This parameter is valid only when a transaction is in progress.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
 
 ```yaml
 Type: SwitchParameter
@@ -436,4 +432,4 @@ You cannot pipe input to this cmdlet.
 
 [Remove-PSDrive](Remove-PSDrive.md)
 
-[about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md)
+[about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md)

reference/4.0/Microsoft.PowerShell.Management/Get-Content.md

@@ -118,7 +118,7 @@ $Hash
 ```output
 Name                           Value
 ----                           -----
-Copyright                      � Microsoft Corporation. All rights reserved.
+Copyright                      © Microsoft Corporation. All rights reserved.
 ModuleToProcess                Microsoft.PowerShell.ScheduledJob.dll
 FormatsToProcess               PSScheduledJob.Format.ps1xml
 PowerShellVersion              3.0