Markdown and PS Styles

reference/7.5/Microsoft.PowerShell.Core/About/about_Job_Details.md

@@ -145,14 +145,15 @@ start the job.
 - When you use `Start-Job` to start a job on a local computer, the job consists
   of an executive parent job and a child job that runs the command.
 
-- When you use the **AsJob** parameter of `Invoke-Command` to start a job on one or
-  more computers, the job consists of an executive parent job and a child job
-  for each job run on each computer.
+- When you use the **AsJob** parameter of `Invoke-Command` to start a job on
+  one or more computers, the job consists of an executive parent job and a
+  child job for each job run on each computer.
 
-- When you use `Invoke-Command` to run a `Start-Job` command on one or more remote
-  computers, the result is the same as a local command run on each remote
-  computer. The command returns a job object for each computer. The job object
-  consists of an executive parent job and one child job that runs the command.
+- When you use `Invoke-Command` to run a `Start-Job` command on one or more
+  remote computers, the result is the same as a local command run on each
+  remote computer. The command returns a job object for each computer. The job
+  object consists of an executive parent job and one child job that runs the
+  command.
 
 The parent job represents all of the child jobs. When you manage a parent job,
 you also manage the associated child jobs. For example, if you stop a parent
@@ -239,10 +240,10 @@ exist only in a particular session. Workflow jobs can be suspended and
 resumed.
 
 The cmdlets that you use to manage custom jobs depend on the job type. For
-some, you use the standard job cmdlets, such as `Get-Job` and `Start-Job`. Others
-come with specialized cmdlets that manage only a particular type of job. For
-detailed information about custom job types, see the help topics about the job
-type.
+some, you use the standard job cmdlets, such as `Get-Job` and `Start-Job`.
+Others come with specialized cmdlets that manage only a particular type of job.
+For detailed information about custom job types, see the help topics about the
+job type.
 
 To find the job type of a job, use the `Get-Job` cmdlet. `Get-Job` returns
 different job objects for different types of jobs. The value of the
@@ -265,9 +266,9 @@ The following table lists the job types that come with PowerShell.
 | PSEventJob     | Created using`Register-ObjectEvent` and specifying an    |
 |                | action with the **Action** parameter.                    |
 
-NOTE: Before using the `Get-Job` cmdlet to get jobs of a particular type, verify
-that the module that adds the job type is imported into the current session.
-Otherwise, `Get-Job` does not get jobs of that type.
+NOTE: Before using the `Get-Job` cmdlet to get jobs of a particular type,
+verify that the module that adds the job type is imported into the current
+session. Otherwise, `Get-Job` does not get jobs of that type.
 
 ## Examples
 
@@ -354,7 +355,7 @@ Id         Name            JobTriggers     Command       Enabled
 - [about_Jobs](about_Jobs.md)
 - [about_Remote](about_Remote.md)
 - [about_Remote_Jobs](about_Remote_Jobs.md)
-- [about_Thread_Jobs](/powershell/module/microsoft.powershell.core/about/about_Thread_Jobs)
+- [about_Thread_Jobs](about_Thread_Jobs)
 - [Invoke-Command](xref:Microsoft.PowerShell.Core.Invoke-Command)
 - [Get-Job](xref:Microsoft.PowerShell.Core.Get-Job)
 - [Remove-Job](xref:Microsoft.PowerShell.Core.Remove-Job)

reference/7.5/Microsoft.PowerShell.Core/About/about_Join.md

@@ -24,8 +24,8 @@ in the command.
 The following diagram shows the syntax for the join operator.
 
 ```powershell
--Join <String[]>
-<String[]> -Join <Delimiter>
+-join <String[]>
+<String[]> -join <Delimiter>
 ```
 
 #### Parameters

reference/7.5/Microsoft.PowerShell.Core/About/about_Language_Keywords.md

@@ -184,8 +184,8 @@ do {<statement list>} until (<condition>)
 
 ## `dynamicparam`
 
-Specifies one part of the body of a function, along with the `begin`, `process`,
-and `end` keywords. Dynamic parameters are added at runtime.
+Specifies one part of the body of a function, along with the `begin`,
+`process`, and `end` keywords. Dynamic parameters are added at runtime.
 
 Syntax:
 

reference/7.5/Microsoft.PowerShell.Core/About/about_Language_Modes.md

@@ -339,7 +339,7 @@ Beginning in PowerShell 7.2, the `New-Object` cmdlet is disabled in
 
 <!-- link references -->
 [01]: /powershell/scripting/learn/remoting/jea/session-configurations
-[02]: about_member-access_enumeration.md
+[02]: about_Member-Access_Enumeration.md
 [03]: about_Session_Configuration_Files.md
 [04]: about_Session_Configurations.md
 [05]: xref:Microsoft.PowerShell.Core.New-PSSessionConfigurationFile

reference/7.5/Microsoft.PowerShell.Core/About/about_Logging_Non-Windows.md

@@ -295,11 +295,11 @@ To view PowerShell log data from a command line on macOS, use the `log` command
 in the **Terminal** or other shell host application. These commands can be run
 from **PowerShell**, **Z Shell**, or **Bash**.
 
-In the following example, the `log` command is used to show the log data on your
-system as it's occurring in realtime. The **process** parameter filters the log
-data for only the `pwsh` process. If you have more than one instance of `pwsh`
-running, the **process** parameter also accepts a process ID as its value. The
-**level** parameter shows messages at the specified level and below.
+In the following example, the `log` command is used to show the log data on
+your system as it's occurring in realtime. The **process** parameter filters
+the log data for only the `pwsh` process. If you have more than one instance of
+`pwsh` running, the **process** parameter also accepts a process ID as its
+value. The **level** parameter shows messages at the specified level and below.
 
 ```powershell
 log stream --predicate "subsystem == 'com.microsoft.powershell'" --level info

reference/7.5/Microsoft.PowerShell.Core/About/about_Logging_Windows.md

@@ -203,8 +203,7 @@ private key:
 
 ```powershell
 Get-WinEvent Microsoft-Windows-PowerShell/Operational |
-    Where-Object Id -eq 4104 |
-    Unprotect-CmsMessage
+    Where-Object Id -eq 4104 | Unprotect-CmsMessage
 ```
 
 ## See also

reference/7.5/Microsoft.PowerShell.Core/About/about_Member-Access_Enumeration.md

@@ -57,8 +57,8 @@ During member-access enumeration for a property, the operator returns the value
 of the property for each item that has that property. If no items have the
 specified property, the operator returns `$null`.
 
-During member-access enumeration for a method, the operator attempts to call the
-method on each item in the collection. If any item in the collection does
+During member-access enumeration for a method, the operator attempts to call
+the method on each item in the collection. If any item in the collection does
 not have the specified method, the operator returns the **MethodNotFound**
 exception.
 
@@ -333,7 +333,7 @@ in the array.
 ### Collections containing PSCustomObject instances
 
 If the collection of objects contains instances of **PSCustomObject** items,
-PowerShell unexpectedly retruns `$null` values when the accessed property is
+PowerShell unexpectedly returns `$null` values when the accessed property is
 missing.
 
 In the following examples at least one object has the referenced property.

reference/7.5/Microsoft.PowerShell.Core/About/about_Methods.md

@@ -115,8 +115,8 @@ two method signatures:
 ```
 
 The first method signature takes the destination file name (and a path). The
-following example uses the first `CopyTo` method to copy the `Final.txt` file to
-the `C:\Bin` directory.
+following example uses the first `CopyTo` method to copy the `Final.txt` file
+to the `C:\Bin` directory.
 
 ```powershell
 (Get-ChildItem c:\final.txt).CopyTo("c:\bin\final.txt")

reference/7.5/Microsoft.PowerShell.Core/About/about_Module_Manifests.md

@@ -1559,10 +1559,10 @@ imported as `Get-ExampleItem`.
 [03]: /powershell/gallery/concepts/package-manifest-affecting-ui
 [04]: /powershell/scripting/dev-cross-plat/performance/module-authoring-considerations
 [05]: /powershell/scripting/developer/module/supporting-updatable-help
-[06]: about_experimental_features.md#declaring-experimental-features-in-modules-written-in-powershell
+[06]: about_Experimental_Features.md#declaring-experimental-features-in-modules-written-in-powershell
 [07]: about_Format.ps1xml.md
 [08]: about_Language_Modes.md
-[09]: about_powershell_editions.md
+[09]: about_Powershell_Editions.md
 [10]: about_Types.ps1xml.md
 [11]: about_Updatable_Help.md
 [13]: xref:Microsoft.PowerShell.Core.New-ModuleManifest

reference/7.5/Microsoft.PowerShell.Core/About/about_Modules.md

@@ -248,8 +248,7 @@ For example, to find the commands in the **BitsTransfer** module, type:
 Get-Command -Module BitsTransfer
 ```
 
-For more information about the `Get-Command` cmdlet, see
-[Get-Command][11].
+For more information about the `Get-Command` cmdlet, see [Get-Command][11].
 
 ## Remove a module
 

reference/7.5/Microsoft.PowerShell.Core/About/about_Object_Creation.md

@@ -289,7 +289,7 @@ New-PSSession -ComputerName Server01 -SessionOption @{
   IdleTimeout=43200000
   SkipCnCheck=$True
 }
-Register-ScheduledJob Name Test -FilePath .\Get-Inventory.ps1 -Trigger @{
+Register-ScheduledJob -Name Test -FilePath .\Get-Inventory.ps1 -Trigger @{
   Frequency="Daily"
   At="15:00"
 }

reference/7.5/Microsoft.PowerShell.Core/About/about_Objects.md

@@ -38,7 +38,7 @@ in commands to take action and manage data.
 
 You can discover an objects properties and methods using
 [Get-Member](xref:Microsoft.PowerShell.Utility.Get-Member) or the `psobject`
- [intrinsic member](about_Intrinsic_Members.md).
+[intrinsic member](about_Intrinsic_Members.md).
 
 ## Objects in Pipelines
 

reference/7.5/Microsoft.PowerShell.Core/About/about_Operator_Precedence.md

@@ -121,8 +121,8 @@ $read_only = ( Get-ChildItem *.txt | Where-Object {$_.isReadOnly} )
 
 Because the pipeline operator (`|`) has a higher precedence than the assignment
 operator (`=`), the files that the `Get-ChildItem` cmdlet gets are sent to the
-`Where-Object` cmdlet for filtering before they are assigned to the `$read_only`
-variable.
+`Where-Object` cmdlet for filtering before they are assigned to the
+`$read_only` variable.
 
 The following example demonstrates that the index operator takes precedence
 over the cast operator.
@@ -194,7 +194,7 @@ are reading and maintaining your scripts.
 [assign]: about_Assignment_Operators.md
 [compare]: about_Comparison_Operators.md
 [join]: about_Join.md
-[logic]: about_logical_operators.md
+[logic]: about_Logical_Operators.md
 [ops]: about_Operators.md
 [redir]: about_Redirection.md
 [scopes]: about_Scopes.md

reference/7.5/Microsoft.PowerShell.Core/About/about_Operators.md

@@ -251,7 +251,7 @@ For more information, see [about_Parsing][08].
 This example stores a command in a string and executes it using the call
 operator.
 
-```
+```powershell
 PS> $c = "Get-ExecutionPolicy"
 PS> $c
 Get-ExecutionPolicy
@@ -262,7 +262,7 @@ AllSigned
 The call operator doesn't parse strings. This means that you can't use
 command parameters within a string when you use the call operator.
 
-```
+```powershell
 PS> $c = "Get-Service -Name Spooler"
 PS> $c
 Get-Service -Name Spooler
@@ -276,7 +276,7 @@ try again.
 The [Invoke-Expression][25] cmdlet can execute code that causes parsing errors
 when using the call operator.
 
-```
+```powershell
 PS> & "1+1"
 &: The term '1+1' is not recognized as a name of a cmdlet, function, script
 file, or executable program. Check the spelling of the name, or if a path was
@@ -293,7 +293,7 @@ the contents of the quoted string instead of running the script. The call
 operator allows you to execute the contents of the string containing the
 filename.
 
-```
+```powershell
 PS C:\Scripts> Get-ChildItem
 
     Directory: C:\Scripts
@@ -465,7 +465,7 @@ objects to be formatted on the right side of the operator.
 "{0} {1,-10} {2:N}" -f 1,"hello",[math]::pi
 ```
 
-```output
+```Output
 1 hello      3.14
 ```
 
@@ -477,7 +477,7 @@ formatted string to.
 "{0:00} {1:000} {2:000000}" -f 7, 24, 365
 ```
 
-```output
+```Output
 07 024 000365
 ```
 
@@ -502,7 +502,7 @@ value.
 Given a list of indices, the index operator returns a list of members
 corresponding to those indices.
 
-```
+```powershell
 PS> $a = 1, 2, 3
 PS> $a[0]
 1
@@ -523,7 +523,7 @@ $h = @{key="value"; name="PowerShell"; version="2.0"}
 $h["name"]
 ```
 
-```output
+```Output
 PowerShell
 ```
 
@@ -532,7 +532,7 @@ $x = [xml]"<doc><intro>Once upon a time...</intro></doc>"
 $x["doc"]
 ```
 
-```output
+```Output
 intro
 -----
 Once upon a time...
@@ -542,7 +542,7 @@ When an object isn't an indexed collection, using the index operator to access
 the first element returns the object itself. Index values beyond the first
 element return `$null`.
 
-```
+```powershell
 PS> (2)[0]
 2
 PS> (2)[-1]
@@ -707,7 +707,7 @@ expression.
 
 ```powershell
 $myProcess.peakWorkingSet
-(Get-Process PowerShell).kill()
+(Get-Process PowerShell).Kill()
 'OS', 'Platform' | Foreach-Object { $PSVersionTable. $_ }
 ```
 
@@ -872,9 +872,9 @@ ${a}?[0]
 [10]: about_If.md
 [11]: about_Jobs.md
 [12]: about_Join.md
-[13]: about_logical_operators.md
+[13]: about_Logical_Operators.md
 [14]: about_Member-Access_Enumeration.md
-[15]: about_operator_precedence.md
+[15]: about_Operator_Precedence.md
 [16]: About_Pipeline_Chain_Operators.md
 [17]: about_Preference_Variables.md#ofs
 [18]: about_Redirection.md

reference/7.5/Microsoft.PowerShell.Core/About/about_PSConsoleHostReadLine.md

@@ -9,6 +9,7 @@ title: about_PSConsoleHostReadLine
 # about_PSConsoleHostReadLine
 
 ## Short description
+
 Explains how to customize how PowerShell reads input at the console prompt.
 
 ## Long description

reference/7.5/Microsoft.PowerShell.Core/About/about_PSCustomObject.md

@@ -296,6 +296,6 @@ properties.
 <!-- link references -->
 [01]: about_Object_Creation.md
 [02]: about_Objects.md
-[03]: about_type_accelerators.md
+[03]: about_Type_Accelerators.md
 [04]: xref:System.Management.Automation.PSCustomObject
 [05]: xref:System.Management.Automation.PSObject

reference/7.5/Microsoft.PowerShell.Core/About/about_PSItem.md

@@ -41,9 +41,9 @@ cases.
 
 ## ForEach-Object Process
 
-The [ForEach-Object][02] cmdlet is designed to operate
-on objects in the pipeline, executing the **Process** parameter's scriptblock
-once for every object in the pipeline.
+The [ForEach-Object][02] cmdlet is designed to operate on objects in the
+pipeline, executing the **Process** parameter's scriptblock once for every
+object in the pipeline.
 
 You can use `$PSItem` in the **Process** parameter's scriptblock but not in the
 **Begin** or **End** parameter scriptblocks. If you reference `$PSItem` in the
@@ -374,9 +374,9 @@ with the default format for the current culture by casting the value to
 ## See also
 
 - [about_Arrays][04]
-- [about_automatic_variables][01]
+- [about_Automatic_Variables][01]
 - [about_Comparison_Operators][12]
-- [about_functions][08]
+- [about_Functions][08]
 - [about_Script_Blocks][14]
 - [about_Switch][07]
 - [ForEach-Object][02]

reference/7.5/Microsoft.PowerShell.Core/About/about_PackageManagement.md

@@ -42,8 +42,7 @@ us define some terms:
   stored in a specific package source.
 
 The PackageManagement module includes the following cmdlets. For more
-information, see the [PackageManagement](/powershell/module/packagemanagement)
-help.
+information, see the [PackageManagement][01] help.
 
 - `Get-PackageProvider`: Returns a list of package providers that are
    connected to PackageManagement.
@@ -101,7 +100,7 @@ More Information About the PackageManagement Project
 
 For more information about the PackageManagement open development project,
 including how to create a PackageManagement package provider, see the
-PackageManagement project on GitHub at https://oneget.org.
+PackageManagement project on GitHub at [https://oneget.org][02].
 
 ## See also
 
@@ -115,3 +114,7 @@ PackageManagement project on GitHub at https://oneget.org.
 - [Register-PackageSource](xref:PackageManagement.Register-PackageSource)
 - [Set-PackageSource](xref:PackageManagement.Set-PackageSource)
 - [Unregister-PackageSource](xref:PackageManagement.Unregister-PackageSource)
+
+<!-- link references -->
+[01]: /powershell/module/packagemanagement
+[02]: https://oneget.org

reference/7.5/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md

@@ -93,6 +93,6 @@ example, see the [Visualize parameter binding][01] article.
 
 <!-- link references -->
 [01]: /powershell/scripting/learn/deep-dives/visualize-parameter-binding
-[02]: about_functions_advanced_parameters.md#valuefrompipeline-argument
-[03]: about_functions_advanced_parameters.md#valuefrompipelinebypropertyname-argument
+[02]: about_Functions_Advanced_Parameters.md#valuefrompipeline-argument
+[03]: about_Functions_Advanced_Parameters.md#valuefrompipelinebypropertyname-argument
 [04]: xref:Microsoft.PowerShell.Utility.Trace-Command