Merging latest to live (#861)

* Fixing the cross file reference anchors (#855)

* Removing 'preview' from WMF 5.0 release notes (#857)

Add an optional extended description…

* In the about topics examples, adding 'space' after the PS prompt (#859)

* In the about topics examples, adding 'space' after the PS prompt

* Adding 'space' after the PS prompt - II

* Adding 'space' after the PS prompt - III

* Fixing the prompt to say PS instead of CPS (#860)

Author: HemantMahawar

Diff for: reference/3.0/Microsoft.PowerShell.Core/About/about_Arrays.md

@@ -90,13 +90,13 @@ The syntax of the array operator is as follows:
 You can use the array operator to create an array of zero or
 one object.
 
-PS C:>$a = @("One")
-PS C:>$a.Count
+PS C:> $a = @("One")
+PS C:> $a.Count
 # 1
 
 
-PS C:>$b = @()
-PS C:>$b.Count
+PS C:> $b = @()
+PS C:> $b.Count
 # 0
 
 

Diff for: reference/3.0/Microsoft.PowerShell.Core/About/about_Command_Precedence.md

@@ -176,7 +176,7 @@ ModuleName property of commands.
 
 For example, to find the source of the Get-Date cmdlet, type:
 
-PS C:>(Get-Command Get-Date).ModuleName
+PS C:> (Get-Command Get-Date).ModuleName
 Microsoft.PowerShell.Utility
 
 # CALL OPERATOR

Diff for: reference/3.0/Microsoft.PowerShell.Core/About/about_Escape_Characters.md

@@ -46,11 +46,11 @@ being substituted for the variable.
 
 For example:
 
-PS C:>$a = 5
+PS C:> $a = 5
 PS C:>"The value is stored in $a."
 The value is stored in 5.
 
-PS C:>$a = 5
+PS C:> $a = 5
 PS C:>"The value is stored in `$a."
 The value is stored in $a.
 

Diff for: reference/3.0/Microsoft.PowerShell.Core/About/about_Functions.md

@@ -279,7 +279,7 @@ You can use all of the parameters of Get-Command when you call
 the Get-MyCommand function. The parameters and parameter values
 are passed to the command using @Args.
 
-PS C:>Get-MyCommand -Name Get-ChildItem
+PS C:> Get-MyCommand -Name Get-ChildItem
 CommandType     Name                ModuleName
 -----------     ----                ----------
 Cmdlet          Get-ChildItem       Microsoft.PowerShell.Management

Diff for: reference/3.0/Microsoft.PowerShell.Core/About/about_Group_Policy_Settings.md

@@ -108,8 +108,8 @@ To turn on module logging for a module, use the following command format.
 The module must be imported into the session and the setting is effective
 only in the current session.
 
-PS C:>Import-Module <Module-Name>
-PS C:>(Get-Module <Module-Name>).LogPipelineExecutionDetails = $true
+PS C:> Import-Module <Module-Name>
+PS C:> (Get-Module <Module-Name>).LogPipelineExecutionDetails = $true
 
 To turn on module logging for all sessions on a particular computer,
 add the previous commands to the all-users Windows PowerShell profile

Diff for: reference/3.0/Microsoft.PowerShell.Core/About/about_Job_Details.md

@@ -179,7 +179,7 @@ When you display the Name and ChildJob properties of the job in $j, it
 shows that the command returned a job object with three child jobs, one for
 each computer.
 
-CPS C:> $j | Format-List Name, ChildJobs
+PS C:> $j | Format-List Name, ChildJobs
 
 Name      : Job3
 ChildJobs : {Job4, Job5, Job6}

Diff for: reference/3.0/Microsoft.PowerShell.Core/About/about_Jobs.md

@@ -94,7 +94,7 @@ returns all of the jobs that were started in the current session.
 
 For example, the following command gets the jobs in the current session.
 
-PS C:>Get-Job
+PS C:> Get-Job
 
 Id  Name  PSJobTypeName State      HasMoreData  Location   Command
 --  ----  ------------- -----      -----------  --------   -------

Diff for: reference/3.0/Microsoft.PowerShell.Core/About/about_Language_Modes.md

@@ -214,7 +214,7 @@ configuration file, the session configuration has a LanguageMode
 property. You can find the language mode by getting the value
 of the LanguageMode property.
 
-PS C:>(Get-PSSessionConfiguration -Name Test).LanguageMode
+PS C:> (Get-PSSessionConfiguration -Name Test).LanguageMode
 FullLanguage
 
 On other session configurations, you can find the language
@@ -228,7 +228,7 @@ ConstrainedLanguage session by getting the value of the
 LanguageMode property of the session state.
 
 For example:
-PS C:>$ExecutionContext.SessionState.LanguageMode
+PS C:> $ExecutionContext.SessionState.LanguageMode
 ConstrainedLanguage
 
 However, in sessions with  RestrictedLanguage and

Diff for: reference/3.0/Microsoft.PowerShell.Core/About/about_PowerShell_Ise_exe.md

@@ -81,32 +81,32 @@ Displays help for PowerShell_ISE.exe.
 These commands start Windows PowerShell ISE. The commands are equivalent
 and can be used interchangeably.
 
-PS C:>PowerShell_ISE.exe
-PS C:>PowerShell_ISE
+PS C:> PowerShell_ISE.exe
+PS C:> PowerShell_ISE
 # PS C:>ISE
 
 
 These commands open the Get-Profile.ps1 script in Windows PowerShell ISE.
 The commands are equivalent and can be used interchangeably.
 
-PS C:>PowerShell_ISE.exe -File .\Get-Profile.ps1
-PS C:>ISE -File .\Get-Profile.ps1
-PS C:>ISE .\Get-Profile.ps1
+PS C:> PowerShell_ISE.exe -File .\Get-Profile.ps1
+PS C:> ISE -File .\Get-Profile.ps1
+PS C:> ISE .\Get-Profile.ps1
 
 This command opens the Get-Backups.ps1 and Get-BackupInstance.ps1 scripts
 in Windows PowerShell ISE. To open more than one file, use a comma to
 separate the file names and enclose the entire file name value in quotation
 marks.
 
-PS C:>ISE -File ".\Get-Backups.ps1,Get-BackupInstance.ps1"
+PS C:> ISE -File ".\Get-Backups.ps1,Get-BackupInstance.ps1"
 
 This command starts Windows PowerShell ISE with no profiles.
 
-PS C:>ISE -NoProfile
+PS C:> ISE -NoProfile
 
 This command gets help for PowerShell_ISE.exe.
 
-PS C:>ISE -help
+PS C:> ISE -help
 
 # SEE ALSO
 

Diff for: reference/3.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md

@@ -45,16 +45,16 @@ commands  are defined in the session in which the command runs.
 In the following example, the $ps variable is defined in the
 temporary  session in which the Get-WinEvent command runs.
 
-PS C:>Invoke-Command -ComputerName S1 -ScriptBlock {$ps = "Windows PowerShell"; Get-WinEvent -LogName $ps}
+PS C:> Invoke-Command -ComputerName S1 -ScriptBlock {$ps = "Windows PowerShell"; Get-WinEvent -LogName $ps}
 
 Similarly, when the command runs in a persistent session (PSSession),
 the remote variable must be defined in the same PSSession.
 
-PS C:>$s = New-PSSession -ComputerName S1
+PS C:> $s = New-PSSession -ComputerName S1
 
-PS C:>Invoke-Command -ComputerName S1 -ScriptBlock {$ps = "Windows PowerShell"}
+PS C:> Invoke-Command -ComputerName S1 -ScriptBlock {$ps = "Windows PowerShell"}
 
-PS C:>Invoke-Command -Sessions $s -ScriptBlock {Get-WinEvent -LogName $ps}
+PS C:> Invoke-Command -Sessions $s -ScriptBlock {Get-WinEvent -LogName $ps}
 
 # USING LOCAL VARIABLES
 
@@ -74,16 +74,16 @@ In the following example, the $ps variable is created in the local
 session, but is used in the session in which the command runs. The
 Using scope modifier identifies $ps as a local variable.
 
-PS C:>$ps = "Windows PowerShell"
-PS C:>Invoke-Command -ComputerName S1 -ScriptBlock {Get-WinEvent -LogName $Using:ps}
+PS C:> $ps = "Windows PowerShell"
+PS C:> Invoke-Command -ComputerName S1 -ScriptBlock {Get-WinEvent -LogName $Using:ps}
 
 You can also use the Using scope modifier in PSSessions.
 
-PS C:>$s = New-PSSession -ComputerName S1
+PS C:> $s = New-PSSession -ComputerName S1
 
-PS C:>$ps = "Windows PowerShell"
+PS C:> $ps = "Windows PowerShell"
 
-PS C:>Invoke-Command -Sessions $s -ScriptBlock {Get-WinEvent -LogName $Using:ps}
+PS C:> Invoke-Command -Sessions $s -ScriptBlock {Get-WinEvent -LogName $Using:ps}
 
 # USING LOCAL VARIABLES IN WINDOWS POWERSHELL 2.0
 

Diff for: reference/3.0/Microsoft.PowerShell.Core/About/about_Splatting.md

@@ -89,8 +89,8 @@ replaces the dollar sign ($HashArguments) in the command.
 
 To provide a value for the WhatIf switch parameter, use $True or $False.
 
-PS C:>$HashArguments = @{ Path = "test.txt"; Destination = "test2.txt"; WhatIf = $true }
-PS C:>Copy-Item @HashArguments
+PS C:> $HashArguments = @{ Path = "test.txt"; Destination = "test2.txt"; WhatIf = $true }
+PS C:> Copy-Item @HashArguments
 
 Note: In the first command, the At symbol (@) indicates a hash table, not
 a splatted value. The syntax for hash tables in Windows PowerShell is:
@@ -115,8 +115,8 @@ values are in position order in the array. The second command uses the
 $ArrayArguments variable in a command in splatting. The At symbol
 (@ArrayArguments) replaces the dollar sign ($ArrayArguments) in the command.
 
-PS C:>$ArrayArguments = "test.txt", "test2.txt"
-PS C:>Copy-Item @ArrayArguments -WhatIf
+PS C:> $ArrayArguments = "test.txt", "test2.txt"
+PS C:> Copy-Item @ArrayArguments -WhatIf
 
 # EXAMPLES
 

Diff for: reference/3.0/Microsoft.PowerShell.Core/About/about_WQL.md

@@ -224,9 +224,9 @@ Get-CimInstance returns a CimInstance object, instead of
 the ManagementObject that Get-WmiObject returns, but
 the objects are quite similar.
 
-PS C:>(Get-CimInstance -Query "Select * from Win32_Bios").GetType().FullName
+PS C:> (Get-CimInstance -Query "Select * from Win32_Bios").GetType().FullName
 Microsoft.Management.Infrastructure.CimInstance
-PS C:>(Get-WmiObject -Query "Select * from Win32_Bios").GetType().FullName
+PS C:> (Get-WmiObject -Query "Select * from Win32_Bios").GetType().FullName
 System.Management.ManagementObject
 
 USING THE [wmisearcher] TYPE ACCELERATOR
@@ -287,12 +287,12 @@ When you use the [wmisearcher] type accelerator, it
 changes the query string into a ManagementObjectSearcher
 object, as shown in the following commands.
 
-PS C:>$a = "Select * from Win32_Bios"
-PS C:>$a.GetType().FullName
+PS C:> $a = "Select * from Win32_Bios"
+PS C:> $a.GetType().FullName
 System.String
 
-PS C:>$a = [wmisearcher]"Select * from Win32_Bios"
-PS C:>$a.GetType().FullName
+PS C:> $a = [wmisearcher]"Select * from Win32_Bios"
+PS C:> $a.GetType().FullName
 System.Management.ManagementObjectSearcher
 
 This command format works on any query. The following
@@ -511,8 +511,8 @@ Select-Object cmdlet gets the Name and ProcessID
 properties, and the Sort-Object cmdlet sorts the
 results in alphabetical order by name.
 
-PS C:>$query = "Select * from win32_Process where name LIKE '[A-P]%'"
-PS C:>Get-WmiObject -Query $query |
+PS C:> $query = "Select * from win32_Process where name LIKE '[A-P]%'"
+PS C:> Get-WmiObject -Query $query |
 Select-Object -Property Name, ProcessID |
 Sort-Object -Property Name
 
@@ -523,8 +523,8 @@ do not begin with any of the following letters:
 
 and followed zero or more letters.
 
-PS C:>$query = "Select * from win32_Process where name LIKE '[^ASWPRCUN]%'"
-PS C:>Get-WmiObject -Query $query |
+PS C:> $query = "Select * from win32_Process where name LIKE '[^ASWPRCUN]%'"
+PS C:> Get-WmiObject -Query $query |
 Select-Object -Property Name, ProcessID |
 Sort-Object -Property Name
 
@@ -588,8 +588,8 @@ For example, the following commands get all instances
 of the Win32_Process WMI class but returns them
 only if the process name is winword.exe or excel.exe.
 
-PS C:>$q = "Select * from Win32_Process where Name = 'winword.exe' or Name = 'excel.exe'"
-PS C:>Get-WmiObject -Query $q
+PS C:> $q = "Select * from Win32_Process where Name = 'winword.exe' or Name = 'excel.exe'"
+PS C:> Get-WmiObject -Query $q
 
 The Or statement can be used with more than two
 conditions. In the following query, the Or statement
@@ -613,7 +613,7 @@ ID of 6512.
 
 Note that the commands use the Get-CimInstance cmdlet.
 
-PS C:>$q = "Select * from Win32_Process where Name = 'winword.exe' and ProcessID =6512"
+PS C:> $q = "Select * from Win32_Process where Name = 'winword.exe' and ProcessID =6512"
 PS C:> Get-CimInstance -Query $q
 
 ProcessId        Name             HandleCount      WorkingSetSize   VirtualSize
@@ -657,17 +657,17 @@ For example, the following commands get processes
 that have a null value for the IntallDate property.
 The commands return many processes.
 
-PS C:>$q = "Select * from Win32_Process where InstallDate is null"
-PS C:>Get-WmiObject -Query $q
+PS C:> $q = "Select * from Win32_Process where InstallDate is null"
+PS C:> Get-WmiObject -Query $q
 
 In contrast, the following command, gets user
 accounts that have a null value for the Description
 property. This command does not return any user
 accounts, even though most user accounts do not have
 any value for the Description property.
 
-PS C:>$q = "Select * from Win32_UserAccount where Description is null"
-PS C:>Get-WmiObject -Query $q
+PS C:> $q = "Select * from Win32_UserAccount where Description is null"
+PS C:> Get-WmiObject -Query $q
 
 To find the user accounts that have no value for
 the Description property, use the equality operator
@@ -685,14 +685,14 @@ sensitive.
 The following WQL query returns only local user
 accounts from a domain joined computer.
 
-PS C:>$q = "Select * from Win32_UserAccount where LocalAccount = True"
-PS C:>Get-CimInstance -Query $q
+PS C:> $q = "Select * from Win32_UserAccount where LocalAccount = True"
+PS C:> Get-CimInstance -Query $q
 
 To find domain accounts, use a value of False,
 as shown in the following example.
 
-PS C:>$q = "Select * from Win32_UserAccount where LocalAccount = False"
-PS C:>Get-CimInstance -Query $q
+PS C:> $q = "Select * from Win32_UserAccount where LocalAccount = False"
+PS C:> Get-CimInstance -Query $q
 
 # USING THE ESCAPE CHARACTER
 

Diff for: reference/3.0/Microsoft.PowerShell.Management/Clear-Item.md

@@ -41,7 +41,7 @@ Clear-Item is similar to Clear-Content, but it works on aliases and variables, i
 ```
 PS C:\>Clear-Item Variable:TestVar1
 -or-
-PS C:>Set-location Variable:PS Variable:\> Clear-Item Testvar1
+PS C:> Set-location Variable:PS Variable:\> Clear-Item Testvar1
 ```
 
 This command deletes the value of the variable, Testvar1.

Diff for: reference/3.0/PSScheduledJob/About/about_Scheduled_Jobs.md

@@ -197,7 +197,7 @@ are not subject to job options or affected by job triggers -- and
 their output is not saved in the Output directory of the scheduled
 job directory.
 
-PS C:>Start-Job -DefinitionName ProcessJob
+PS C:> Start-Job -DefinitionName ProcessJob
 
 The following command deletes the ProcessJob scheduled job and all
 saved results of its job instances.

Diff for: reference/3.0/PSWorkflow/About/about_ActivityCommonParameters.md

@@ -584,7 +584,7 @@ workflow Test-Workflow
 Get-Service -UseDefaultInput $True
 }
 
-PS C:>Test-Workflow -InputObject WinRm
+PS C:> Test-Workflow -InputObject WinRm
 
 Status   Name               DisplayName                            PSComputerName
 ------   ----               -----------                            --------------

Diff for: reference/3.0/PSWorkflow/About/about_Suspend-Workflow.md

@@ -72,7 +72,7 @@ Suspend-Workflow
 (Get-Date)- $a
 }
 
-PS C:>Test-Suspend
+PS C:> Test-Suspend
 
 Id     Name            PSJobTypeName   State         HasMoreData     Location             Command
 --     ----            -------------   -----         -----------     --------             -------
@@ -89,13 +89,13 @@ To wait for the job to be resumed, use the Wait
 parameter, or use the Get-Job cmdlet to get the current
 job object.
 
-PS C:>Resume-Job -Name Job8
+PS C:> Resume-Job -Name Job8
 
 Id     Name            PSJobTypeName   State         HasMoreData     Location             Command
 --     ----            -------------   -----         -----------     --------             -------
 8      Job8            PSWorkflowJob   Suspended     True            localhost            Test-Suspend
 
-PS C:>Get-Job -Name Job8
+PS C:> Get-Job -Name Job8
 
 Id     Name            PSJobTypeName   State         HasMoreData     Location             Command
 --     ----            -------------   -----         -----------     --------             -------
@@ -109,7 +109,7 @@ command that followed the Suspend-Workflow cmdlet. The value
 of the $a variable, which was populated before the suspension,
 is available to the workflow when it resumes.
 
-PS C:>Get-Job -Name Job8 | Receive-Job
+PS C:> Get-Job -Name Job8 | Receive-Job
 
 Days              : 0
 Hours             : 0

Diff for: reference/4.0/Microsoft.PowerShell.Core/About/about_Arrays.md

@@ -91,13 +91,13 @@ The syntax of the array operator is as follows:
 You can use the array operator to create an array of zero or
 one object.
 
-PS C:>$a = @("One")
-PS C:>$a.Count
+PS C:> $a = @("One")
+PS C:> $a.Count
 # 1
 
 
-PS C:>$b = @()
-PS C:>$b.Count
+PS C:> $b = @()
+PS C:> $b.Count
 # 0