Header and blank line updates (MicrosoftDocs#3765)

* Header and blank line updates

* Fixing build error

Author: bobbytreed

reference/6/Microsoft.PowerShell.Core/About/About.md

@@ -5,11 +5,9 @@ locale:  en-us
 keywords:  powershell,cmdlet
 title:  about_Aliases
 ---
-
 # About Aliases
 
 ## SHORT DESCRIPTION
-
 Describes how to use alternate names for cmdlets and commands in
 PowerShell.
 

reference/6/Microsoft.PowerShell.Core/About/about_Aliases.md

@@ -8,7 +8,6 @@ online version: http://go.microsoft.com/fwlink/?LinkId=821476
 schema: 2.0.0
 title: Enable-PSSessionConfiguration
 ---
-
 # Enable-PSSessionConfiguration
 
 ## SYNOPSIS
@@ -22,6 +21,7 @@ Enable-PSSessionConfiguration [[-Name] <String[]>] [-Force] [-SecurityDescriptor
 ```
 
 ## DESCRIPTION
+
 The **Enable-PSSessionConfiguration** cmdlet enables registered session configurations that have been disabled, such as by using the Disable-PSSessionConfiguration or Disable-PSRemoting cmdlets, or the *AccessMode* parameter of Register-PSSessionConfiguration.
 This is an advanced cmdlet that is designed to be used by system administrators to manage customized session configurations for their users.
 
@@ -38,20 +38,23 @@ Instead, use the more comprehensive cmdlet, Enable-PSRemoting.
 ## EXAMPLES
 
 ### Example 1: Re-enable the default session
+
 ```
 PS C:\> Enable-PSSessionConfiguration
 ```
 
 This command re-enables the Microsoft.PowerShell default session configuration on the computer.
 
 ### Example 2: Re-enable specified sessions
+
 ```
 PS C:\> Enable-PSSessionConfiguration -Name MaintenanceShell, AdminShell
 ```
 
 This command re-enables the MaintenanceShell and AdminShell session configurations on the computer.
 
 ### Example 3: Re-enable the all sessions
+
 ```
 PS C:\> Enable-PSSessionConfiguration -Name *
 PS C:\> Get-PSSessionConfiguration | Enable-PSSessionConfiguration
@@ -64,6 +67,7 @@ Therefore, you can use either.
 **Enable-PSSessionConfiguration** does not generate an error if you enable a session configuration that is already enabled.
 
 ### Example 4: Re-enable a session and specify a new security descriptor
+
 ```
 PS C:\> Enable-PSSessionConfiguration -Name MaintenanceShell -SecurityDescriptorSDDL "O:NSG:BAD:P(A;;GXGWGR;;;BA)(A;;GAGR;;;S-1-5-21-123456789-188441444-3100496)S:P"
 ```
@@ -73,6 +77,7 @@ This command re-enables the MaintenanceShell session configuration and specifies
 ## PARAMETERS
 
 ### -Force
+
 Indicates that the cmdlet does not prompt you for confirmation, and restarts the WinRM service without prompting.
 Restarting the service makes the configuration change effective.
 
@@ -91,6 +96,7 @@ Accept wildcard characters: False
 ```
 
 ### -Name
+
 Specifies the names of session configurations to enable.
 Enter one or more configuration names.
 Wildcard characters are permitted.
@@ -112,6 +118,7 @@ Accept wildcard characters: False
 ```
 
 ### -NoServiceRestart
+
 Indicates that the cmdlet does not restart the service.
 
 ```yaml
@@ -127,6 +134,7 @@ Accept wildcard characters: False
 ```
 
 ### -SecurityDescriptorSddl
+
 Specifies a security descriptor with which this cmdlet replaces the security descriptor on the session configuration.
 
 If you omit this parameter, **Enable-PSSessionConfiguration** only deletes the deny all item from the security descriptor.
@@ -144,6 +152,7 @@ Accept wildcard characters: False
 ```
 
 ### -SkipNetworkProfileCheck
+
 Indicates that this cmdlet enables the session configuration when the computer is on a public network.
 This parameter enables a firewall rule for public networks that allows remote access only from computers in the same local subnet.
 By default, **Enable-PSSessionConfiguration** fails on a public network.
@@ -170,6 +179,7 @@ Accept wildcard characters: False
 ```
 
 ### -Confirm
+
 Prompts you for confirmation before running the cmdlet.
 
 ```yaml
@@ -185,6 +195,7 @@ Accept wildcard characters: False
 ```
 
 ### -WhatIf
+
 Shows what would happen if the cmdlet runs.
 The cmdlet is not run.
 
@@ -201,19 +212,23 @@ Accept wildcard characters: False
 ```
 
 ### CommonParameters
+
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216).
 
 ## INPUTS
 
 ### Microsoft.PowerShell.Commands.PSSessionConfigurationCommands#PSSessionConfiguration, System.String
+
 You can pipe a session configuration object or a string that contains the name of a session configuration to this cmdlet.
 
 ## OUTPUTS
 
 ### None
+
 This cmdlet does not return any objects.
 
 ## NOTES
+
 * To run this cmdlet on Windows Vista, Windows Server 2008, and later versions of the Windows operating system, you must start Windows PowerShell by using the Run as administrator option.
 
 *

reference/6/Microsoft.PowerShell.Core/Enable-PSSessionConfiguration.md

@@ -8,7 +8,6 @@ online version: http://go.microsoft.com/fwlink/?LinkID=403736
 schema: 2.0.0
 title: Enter-PSHostProcess
 ---
-
 # Enter-PSHostProcess
 
 ## SYNOPSIS
@@ -17,26 +16,31 @@ Connects to and enters into an interactive session with a local process.
 ## SYNTAX
 
 ### ProcessIdParameterSet (Default)
+
 ```
 Enter-PSHostProcess [-Id] <Int32> [[-AppDomainName] <String>] [<CommonParameters>]
 ```
 
 ### ProcessParameterSet
+
 ```
 Enter-PSHostProcess [-Process] <Process> [[-AppDomainName] <String>] [<CommonParameters>]
 ```
 
 ### ProcessNameParameterSet
+
 ```
 Enter-PSHostProcess [-Name] <String> [[-AppDomainName] <String>] [<CommonParameters>]
 ```
 
 ### PSHostProcessInfoParameterSet
+
 ```
 Enter-PSHostProcess [-HostProcessInfo] <PSHostProcessInfo> [[-AppDomainName] <String>] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
+
 The **Enter-PSHostProcess** cmdlet connects to and enters into an interactive session with a local process.
 
 Instead of creating a new process to host PowerShell and run a remote session, the remote, interactive session is run in an existing process that is already running PowerShell.
@@ -58,6 +62,7 @@ To support attaching to processes on remote computers, the **Enter-PSHostProcess
 ## EXAMPLES
 
 ### Example 1: Start debugging a runspace within the Windows PowerShell ISE process
+
 ```
 In this example, you run **Enter-PSHostProcess** from within the Windows PowerShell console to enter the Windows PowerShell ISE process. In the resulting interactive session, you can find a runspace that you want to debug by running Get-Runspace, and then debug the runspace.
 PS C:\> Enter-PSHostProcess -Name powershell_ise
@@ -132,6 +137,7 @@ Accept wildcard characters: False
 ```
 
 ### -Id
+
 Specifies a process by the process ID.
 To get a process ID, run the Get-Process cmdlet.
 
@@ -148,6 +154,7 @@ Accept wildcard characters: False
 ```
 
 ### -Name
+
 Specifies a process by the process name.
 To get a process name, run the Get-Process cmdlet.
 You can also get process names from the Properties dialog box of a process in Task Manager.
@@ -165,6 +172,7 @@ Accept wildcard characters: False
 ```
 
 ### -Process
+
 Specifies a process by the process object.
 The simplest way to use this parameter is to save the results of a **Get-Process** command that returns process that you want to enter in a variable, and then specify the variable as the value of this parameter.
 
@@ -181,6 +189,7 @@ Accept wildcard characters: False
 ```
 
 ### CommonParameters
+
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216).
 
 ## INPUTS
@@ -190,6 +199,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 ## OUTPUTS
 
 ## NOTES
+
 * **Enter-PSHostProcess** cannot enter the process of the PowerShell session in which you are running the command. You can, however, enter the process of another PowerShell session, or a Windows PowerShell ISE session that is running at the same time as the session in which you are running **Enter-PSHostProcess**.
 
   **Enter-PSHostProcess** can enter only those processes that are hosting PowerShell.