Markdown and PS Styles

Author: ArieHein

reference/7.5/Microsoft.PowerShell.Diagnostics/Get-Counter.md

@@ -262,7 +262,8 @@ The pipeline is used with the `Where-Object` cmdlet to find a subset of the path
 counter sets complete list of counter paths, remove the pipeline (`|`) and `Where-Object` command.
 
 The `$_` is an automatic variable for the current object in the pipeline.
-For more information, see [about_Automatic_Variables](../Microsoft.PowerShell.Core/About/about_Automatic_Variables.md).
+For more information, see
+[about_Automatic_Variables](../Microsoft.PowerShell.Core/About/about_Automatic_Variables.md).
 
 ```powershell
 (Get-Counter -ListSet Memory).Paths | Where-Object { $_ -like "*Cache*" }
@@ -659,4 +660,4 @@ In PowerShell 7, when using the **ListSet** parameter, `Get-Counter` can't retri
 
 [Start-Job](../Microsoft.PowerShell.Core/Start-Job.md)
 
-[Where-Object](..//Microsoft.PowerShell.Core/Where-Object.md)
+[Where-Object](../Microsoft.PowerShell.Core/Where-Object.md)

reference/7.5/Microsoft.PowerShell.Diagnostics/Get-WinEvent.md

@@ -151,9 +151,9 @@ with the asterisk (`*`) wildcard to display each property.
 
 ### Example 3: Configure the classic Security log
 
-This command gets an **EventLogConfiguration** object that represents the classic **Security** log. The
-object is then used to configure settings for the log, such as max file size, file path, and whether the
-log is enabled.
+This command gets an **EventLogConfiguration** object that represents the classic **Security** log.
+The object is then used to configure settings for the log, such as max file size, file path, and
+whether the log is enabled.
 
 ```powershell
 $log = Get-WinEvent -ListLog Security
@@ -196,17 +196,18 @@ ProviderLatency                : 1000
 ProviderControlGuid            :
 ```
 
-The `Get-WinEvent` cmdlet uses the **ListLog** parameter to specify the **Security** log. The object is
-saved to a variable. The **MaximumSizeInBytes** property is set to 1 gigabyte on the object. The
+The `Get-WinEvent` cmdlet uses the **ListLog** parameter to specify the **Security** log. The object
+is saved to a variable. The **MaximumSizeInBytes** property is set to 1 gigabyte on the object. The
 **SaveChanges** method is called to push the change to the system inside of a try block to handle
-access violations. The `Get-WinEvent` cmdlet is called again on the **Security** log and piped to the
-`Format-List` cmdlet to verify that the **MaximumSizeInBytes** property has been saved on the machine.
+access violations. The `Get-WinEvent` cmdlet is called again on the **Security** log and piped to
+the `Format-List` cmdlet to verify that the **MaximumSizeInBytes** property has been saved on the
+machine.
 
 ### Example 4: Get event logs from a server
 
 This command only gets event logs on the local computer that contain events. It's possible for a
 log's **RecordCount** to be null or zero. The example uses the `$_` variable. For more information,
-see [about_Automatic_Variables](../Microsoft.PowerShell.Core/about/about_automatic_variables.md).
+see [about_Automatic_Variables](../Microsoft.PowerShell.Core/About/about_Automatic_Variables.md).
 
 ```powershell
 Get-WinEvent -ListLog * -ComputerName localhost | Where-Object { $_.RecordCount }
@@ -233,7 +234,8 @@ is a property of the object with a non-null value.
 
 This example gets objects that represent the **Application** event logs on three computers:
 Server01, Server02, and Server03. The **ForEach** keyword is used because the **ComputerName**
-parameter accepts only one value. For more information, see [about_Foreach](../Microsoft.PowerShell.Core/about/about_Foreach.md).
+parameter accepts only one value. For more information, see
+[about_Foreach](../Microsoft.PowerShell.Core/About/about_Foreach.md).
 
 ```powershell
 $S = 'Server01', 'Server02', 'Server03'
@@ -574,7 +576,8 @@ Get-WinEvent -LogName 'Windows PowerShell' -FilterXPath $XPath
 This example uses the **FilterHashtable** parameter to get events from the **Application** log. The
 hash table uses **key/value** pairs. For more information about the **FilterHashtable** parameter,
 see [Creating Get-WinEvent queries with FilterHashtable](/powershell/scripting/samples/Creating-Get-WinEvent-queries-with-FilterHashtable).
-For more information about hash tables, see [about_Hash_Tables](../Microsoft.PowerShell.Core/about/about_hash_tables.md).
+For more information about hash tables, see
+[about_Hash_Tables](../Microsoft.PowerShell.Core/About/about_Hash_Tables.md).
 
 ```powershell
 $Date = (Get-Date).AddDays(-2)
@@ -739,8 +742,9 @@ Help.
 
 Use an XML query to create a complex query that contains several XPath statements. The XML format
 also allows you to use a **Suppress XML** element that excludes events from the query. For more
-information about the XML schema for event log queries, see [Query Schema](/windows/win32/wes/queryschema-schema)
-and the XML Event Queries section of [Event Selection](/previous-versions/aa385231(v=vs.85)).
+information about the XML schema for event log queries, see
+[Query Schema](/windows/win32/wes/queryschema-schema) and the XML Event Queries section of
+[Event Selection](/previous-versions/aa385231(v=vs.85)).
 
 You may also create a **Suppress** element using the **FilterHashtable** parameter.
 
@@ -760,7 +764,8 @@ Accept wildcard characters: False
 
 Specifies an XPath query that this cmdlet select events from one or more logs.
 
-For more information about the XPath language, see [XPath Reference](/previous-versions/dotnet/netframework-4.0/ms256115(v=vs.100))
+For more information about the XPath language, see
+[XPath Reference](/previous-versions/dotnet/netframework-4.0/ms256115(v=vs.100))
 and the Selection Filters section of [Event Selection](/previous-versions/aa385231(v=vs.85)).
 
 ```yaml
@@ -841,8 +846,8 @@ cmdlet.
 > [!NOTE]
 > PowerShell does not limit the amount of logs you can request. However, the `Get-WinEvent` cmdlet
 > queries the Windows API which has a limit of 256. This can make it difficult to filter through all
-> of your logs at one time. You can work around this by using a `foreach` loop to iterate through each
-> log like this: `Get-WinEvent -ListLog * | ForEach-Object{ Get-WinEvent -LogName $_.LogName }`
+> of your logs at one time. You can work around this by using a `foreach` loop to iterate through
+> each log like this: `Get-WinEvent -ListLog * | ForEach-Object{ Get-WinEvent -LogName $_.LogName }`
 
 ```yaml
 Type: System.String[]
@@ -939,7 +944,8 @@ Accept wildcard characters: True
 
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
 -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose,
--WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+-WarningAction, and -WarningVariable. For more information, see
+[about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
 
 ## INPUTS
 
@@ -980,11 +986,11 @@ Environment (Windows PE).
 
 ## RELATED LINKS
 
-[about_Automatic_Variables](../Microsoft.PowerShell.Core/about/about_automatic_variables.md)
+[about_Automatic_Variables](../Microsoft.PowerShell.Core/About/about_Automatic_Variables.md)
 
-[about_Foreach](../Microsoft.PowerShell.Core/about/about_Foreach.md)
+[about_Foreach](../Microsoft.PowerShell.Core/About/about_Foreach.md)
 
-[about_Hash_Tables](../Microsoft.PowerShell.Core/about/about_hash_tables.md)
+[about_Hash_Tables](../Microsoft.PowerShell.Core/About/about_Hash_Tables.md)
 
 [Creating Get-WinEvent queries with FilterHashtable](/powershell/scripting/samples/Creating-Get-WinEvent-queries-with-FilterHashtable)
 

reference/7.5/Microsoft.PowerShell.Management/Add-Content.md

@@ -159,8 +159,7 @@ set to `False`.
 ### Example 7: Use Filters with Add-Content
 
 You can specify a filter to the `Add-Content` cmdlet. When using filters to qualify the **Path**
-parameter, you need to include a trailing asterisk (`*`) to indicate the contents of the
-path.
+parameter, you need to include a trailing asterisk (`*`) to indicate the contents of the path.
 
 The following command adds the word "Done" the content of all `*.txt` files in the `C:\Temp`
 directory.
@@ -429,8 +428,8 @@ You can use the `Add-Content` cmdlet to change the content of any alternate data
 block files that are downloaded from the Internet. If you verify that a downloaded file is safe, use
 the `Unblock-File` cmdlet.
 
-This parameter was introduced in PowerShell 3.0.  As of PowerShell 7.2, `Add-Content` can
-target alternative data streams on both files and directories.
+This parameter was introduced in PowerShell 3.0.  As of PowerShell 7.2, `Add-Content` can target
+alternative data streams on both files and directories.
 
 ```yaml
 Type: System.String

reference/7.5/Microsoft.PowerShell.Management/Clear-Item.md

@@ -180,7 +180,8 @@ typed. No characters are interpreted as wildcards. If the path includes escape c
 it in single quotation marks. Single quotation marks tell PowerShell not to interpret any characters
 as escape sequences.
 
-For more information, see [about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
+For more information, see
+[about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
 
 ```yaml
 Type: System.String[]

reference/7.5/Microsoft.PowerShell.Management/Clear-ItemProperty.md

@@ -90,11 +90,13 @@ Accept wildcard characters: True
 
 ### -Filter
 
-Specifies a filter to qualify the **Path** parameter. The [FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md)
-provider is the only installed PowerShell provider that supports the use of filters. You can find
-the syntax for the **FileSystem** filter language in [about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md).
-Filters are more efficient than other parameters, because the provider applies them when the cmdlet
-gets the objects rather than having PowerShell filter the objects after they are retrieved.
+Specifies a filter to qualify the **Path** parameter. The
+[FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) provider is the only
+installed PowerShell provider that supports the use of filters. You can find the syntax for the
+**FileSystem** filter language in
+[about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). Filters are more efficient
+than other parameters, because the provider applies them when the cmdlet gets the objects rather
+than having PowerShell filter the objects after they are retrieved.
 
 ```yaml
 Type: System.String
@@ -153,7 +155,8 @@ typed. No characters are interpreted as wildcards. If the path includes escape c
 it in single quotation marks. Single quotation marks tell PowerShell not to interpret any characters
 as escape sequences.
 
-For more information, see [about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
+For more information, see
+[about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
 
 ```yaml
 Type: System.String[]

reference/7.5/Microsoft.PowerShell.Management/Copy-Item.md

@@ -536,7 +536,8 @@ typed. No characters are interpreted as wildcards. If the path includes escape c
 it in single quotation marks. Single quotation marks tell PowerShell not to interpret any characters
 as escape sequences.
 
-For more information, see [about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
+For more information, see
+[about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
 
 ```yaml
 Type: System.String[]

reference/7.5/Microsoft.PowerShell.Management/Copy-ItemProperty.md

@@ -108,11 +108,13 @@ Accept wildcard characters: True
 
 ### -Filter
 
-Specifies a filter to qualify the **Path** parameter. The [FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md)
-provider is the only installed PowerShell provider that supports the use of filters. You can find
-the syntax for the **FileSystem** filter language in [about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md).
-Filters are more efficient than other parameters, because the provider applies them when the cmdlet
-gets the objects rather than having PowerShell filter the objects after they are retrieved.
+Specifies a filter to qualify the **Path** parameter. The
+[FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) provider is the only
+installed PowerShell provider that supports the use of filters. You can find the syntax for the
+**FileSystem** filter language in
+[about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). Filters are more efficient
+than other parameters, because the provider applies them when the cmdlet gets the objects rather
+than having PowerShell filter the objects after they are retrieved.
 
 ```yaml
 Type: System.String
@@ -172,7 +174,8 @@ typed. No characters are interpreted as wildcards. If the path includes escape c
 it in single quotation marks. Single quotation marks tell PowerShell not to interpret any characters
 as escape sequences.
 
-For more information, see [about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
+For more information, see
+[about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
 
 ```yaml
 Type: System.String[]

reference/7.5/Microsoft.PowerShell.Management/Debug-Process.md

@@ -238,7 +238,7 @@ This cmdlet returns no output.
 
 This cmdlet uses the AttachDebugger method of the Windows Management Instrumentation (WMI)
 Win32_Process class. For more information about this method, see
-[AttachDebugger method](https://go.microsoft.com/fwlink/?LinkId=143640) in the MSDN library.
+[AttachDebugger method](https://go.microsoft.com/fwlink/?LinkId=143640) in Microsoft Learn.
 
 ## RELATED LINKS
 

reference/7.5/Microsoft.PowerShell.Management/Get-ChildItem.md

@@ -11,7 +11,6 @@ title: Get-ChildItem
 # Get-ChildItem
 
 ## SYNOPSIS
-
 Gets the items and child items in one or more specified locations.
 
 ## SYNTAX
@@ -124,7 +123,7 @@ as follows:
 - `s` (system)
 
 For more information about the mode flags, see
-[about_Filesystem_Provider](../microsoft.powershell.core/about/about_filesystem_provider.md#attributes-flagsexpression).
+[about_Filesystem_Provider](../microsoft.powershell.core/About/about_Filesystem_Provider.md#attributes-flagsexpression).
 
 ### Example 2: Get child item names in a directory
 
@@ -346,8 +345,8 @@ authority.
 Get-ChildItem -Path Cert:\* -Recurse -CodeSigningCert
 ```
 
-For more information about the Certificate provider and the `Cert:` drive,
-see [about_Certificate_Provider](../Microsoft.PowerShell.Security/About/about_Certificate_Provider.md).
+For more information about the Certificate provider and the `Cert:` drive, see
+[about_Certificate_Provider](../Microsoft.PowerShell.Security/About/about_Certificate_Provider.md).
 
 ### Example 8: Get items using the Depth parameter
 
@@ -437,7 +436,7 @@ filesystem object returned by `Get-ChildItem` and is displayed in the default ou
 
 ```powershell
 PS D:\> New-Item -ItemType Junction -Name tmp -Target $env:TEMP
-PS D:\> Get-ChildItem | Select-Object name,LinkTarget
+PS D:\> Get-ChildItem | Select-Object name, LinkTarget
 
 Name     LinkTarget
 ----     ----------
@@ -508,7 +507,8 @@ The **Attributes** parameter supports the following properties:
 - **System**
 - **Temporary**
 
-For a description of these attributes, see the [FileAttributes Enumeration](/dotnet/api/system.io.fileattributes).
+For a description of these attributes, see the
+[FileAttributes Enumeration](/dotnet/api/system.io.fileattributes).
 
 To combine attributes, use the following operators:
 
@@ -863,7 +863,8 @@ typed. No characters are interpreted as wildcards. If the path includes escape c
 it in single quotation marks. Single quotation marks tell PowerShell to not interpret any characters
 as escape sequences.
 
-For more information, see [about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
+For more information, see
+[about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
 
 ```yaml
 Type: System.String[]

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

@@ -129,7 +129,8 @@ to create sample content in a file named `Stream.txt`.
 
 ```powershell
 Set-Content -Path .\Stream.txt -Value 'This is the content of the Stream.txt file'
-# Specify a wildcard to the Stream parameter to display all streams of the recently created file.
+# Specify a wildcard to the Stream parameter to display all streams of the recently
+# created file.
 Get-Item -Path .\Stream.txt -Stream *
 ```
 
@@ -168,7 +169,8 @@ This is the content of the Stream.txt file
 ```
 
 ```powershell
-# Use the Stream parameter of Add-Content to create a new Stream containing sample content.
+# Use the Stream parameter of Add-Content to create a new Stream containing sample
+# content.
 $addContentSplat = @{
     Path = '.\Stream.txt'
     Stream = 'NewStream'
@@ -212,7 +214,7 @@ Added a stream named NewStream to Stream.txt
 ```
 
 The **Stream** parameter is a dynamic parameter of the
-[FileSystem provider](../microsoft.powershell.core/about/about_filesystem_provider.md#stream-string).
+[FileSystem provider](../microsoft.powershell.core/About/about_Filesystem_Provider.md#stream-string).
 By default `Get-Content` only retrieves data from the default, or `:$DATA` stream. **Streams** can
 be used to store hidden data such as attributes, security settings, or other data. They can also be
 stored on directories without being child items.

reference/7.5/Microsoft.PowerShell.Management/Get-HotFix.md

@@ -216,7 +216,7 @@ The `Get-HotFix` output might vary on different operating systems.
 
 ## RELATED LINKS
 
-[about_Arrays](/powershell/module/microsoft.powershell.core/about/about_arrays)
+[about_Arrays](/powershell/module/microsoft.powershell.core/About/about_Arrays)
 
 [Add-Content](Add-Content.md)
 

reference/7.5/Microsoft.PowerShell.Management/Get-Item.md

@@ -170,7 +170,7 @@ In PowerShell 6.2, an alternate view was added to get hardlink information. To g
 information, pipe the output to `Format-Table -View childrenWithHardlink`
 
 ```powershell
-Get-Item C:\Windows\System32\ntoskrnl.exe | Format-Table -view childrenWithHardLink
+Get-Item C:\Windows\System32\ntoskrnl.exe | Format-Table -View childrenWithHardLink
 ```
 
 ```Output
@@ -441,7 +441,8 @@ typed. No characters are interpreted as wildcards. If the path includes escape c
 it in single quotation marks. Single quotation marks tell PowerShell not to interpret any characters
 as escape sequences.
 
-For more information, see [about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
+For more information, see
+[about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
 
 ```yaml
 Type: System.String[]

reference/7.5/Microsoft.PowerShell.Management/Get-ItemPropertyValue.md

@@ -70,7 +70,7 @@ This command gets the values of the **LastWriteTime**, **CreationTime**, and **R
 a folder. The property values are returned in the order in which you specified the property names.
 
 ```powershell
-Get-ItemPropertyValue -Path 'C:\Program Files\PowerShell' -Name LastWriteTime,CreationTime,Root
+Get-ItemPropertyValue -Path 'C:\Program Files\PowerShell' -Name LastWriteTime, CreationTime, Root
 ```
 
 ```output
@@ -140,11 +140,13 @@ Accept wildcard characters: True
 
 ### -Filter
 
-Specifies a filter to qualify the **Path** parameter. The [FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md)
-provider is the only installed PowerShell provider that supports the use of filters. You can find
-the syntax for the **FileSystem** filter language in [about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md).
-Filters are more efficient than other parameters, because the provider applies them when the cmdlet
-gets the objects rather than having PowerShell filter the objects after they are retrieved.
+Specifies a filter to qualify the **Path** parameter. The
+[FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) provider is the only
+installed PowerShell provider that supports the use of filters. You can find the syntax for the
+**FileSystem** filter language in
+[about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). Filters are more
+efficient than other parameters, because the provider applies them when the cmdlet gets the objects
+rather than having PowerShell filter the objects after they are retrieved.
 
 ```yaml
 Type: System.String
@@ -185,7 +187,8 @@ typed. No characters are interpreted as wildcards. If the path includes escape c
 it in single quotation marks. Single quotation marks tell PowerShell not to interpret any characters
 as escape sequences.
 
-For more information, see [about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
+For more information, see
+[about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
 
 ```yaml
 Type: System.String[]