Fix MD warnings

Author: ArieHein

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

@@ -166,7 +166,7 @@ The syntax diagrams use the following symbols:
 
   The placeholder inside the angle brackets identifies the .NET type of the
   value that a parameter takes. For example, to use the **Name** parameter of
-  the `Get-Command ` cmdlet, you replace the `<string[]>` with one or more
+  the `Get-Command` cmdlet, you replace the `<string[]>` with one or more
   strings separated by commas (`,`).
 
 <!-- `[]` - also known as binkies -->

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

@@ -659,7 +659,7 @@ Both arguments are optional. If you don't specify any arguments, then
 
 ### PSTypeName attribute
 
-You can't use extended type names in a type declaration. The *PSTypeName**
+You can't use extended type names in a type declaration. The **PSTypeName**
 attribute allows you to restrict the type of the parameter to the extended
 type.
 

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

@@ -133,7 +133,6 @@ $service.Status -eq 'Running' ? (Stop-Service $service) : (Start-Service $servic
 In this example, if the service is running, it's stopped, and if its status is
 not **Running**, it's started.
 
-
 If a `<condition>`, `<if-true>`, or `<if-false>` expression calls a command,
 you must wrap it in parentheses. If you don't, PowerShell raises an argument
 exception for the command in the `<condition>` expression and parsing

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

@@ -87,7 +87,7 @@ The following examples are based on the current working directory being set to
 When using a path in a command, you can use a fully qualified path or a
 relative one. For example, suppose that your current working directory is
 `C:\Windows`. The following `Get-ChildItem` command retrieves all items in the
-`C:\TechDocs `directory:
+`C:\TechDocs` directory:
 
 ```powershell
 Get-ChildItem \TechDocs

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

@@ -233,7 +233,7 @@ drive:\location\child-location\...
 ```
 
 For example, to change your location to the `HKLM\Software` registry key, type
-a `Set-Location `command, such as:
+a `Set-Location` command, such as:
 
 ```powershell
 Set-Location HKLM:\SOFTWARE\

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

@@ -16,9 +16,9 @@ of a variable that is passed to it.
 
 ## Long description
 
-You can pass variables to functions *by reference* or *by value*.
+You can pass variables to functions _by reference_ or _by value_.
 
-When you pass a variable *by value*, you are passing a copy of the data.
+When you pass a variable _by value_, you are passing a copy of the data.
 
 In the following example, the function changes the value of the variable passed
 to it. In PowerShell, integers are value types so they are passed by value.
@@ -41,9 +41,9 @@ $var
 
 In the following example, a variable containing a `Hashtable` is passed to a
 function. `Hashtable` is an object type so by default it is passed to the
-function *by reference*.
+function _by reference_.
 
-When passing a variable *by reference*, the function can change the data and
+When passing a variable _by reference_, the function can change the data and
 that change persists after the function executes.
 
 ```powershell

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

@@ -500,7 +500,7 @@ from newest to oldest.
 
 Event Tracing for Windows (ETW) writes events to the log as events occur. The events are stored in
 the order of oldest to newest. An archived ETW file is saved as an `.etl` such as **TraceLog.etl**.
-The events are listed in the order in which they are written to the log, so the *Oldest* parameter
+The events are listed in the order in which they are written to the log, so the `Oldest` parameter
 is required.
 
 ```powershell

reference/7.5/Microsoft.PowerShell.Management/Join-Path.md

@@ -140,7 +140,7 @@ In this example, no parameter names are used, thus "a" binds to `Path`, "b" to `
 
 ### -AdditionalChildPath
 
-Specifies additional elements to append to the value of the *Path* parameter. The `ChildPath`
+Specifies additional elements to append to the value of the `Path` parameter. The `ChildPath`
 parameter is still mandatory and must be specified as well.
 
 This parameter is specified with the `ValueFromRemainingArguments` property which enables

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

@@ -171,7 +171,7 @@ Forces the cmdlet to set items that cannot otherwise be changed, such as read-on
 variables. The cmdlet cannot change constant aliases or variables.
 Implementation varies from provider to provider.
 For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md).
-Even using the *Force* parameter, the cmdlet cannot override security restrictions.
+Even using the `Force` parameter, the cmdlet cannot override security restrictions.
 
 ```yaml
 Type: System.Management.Automation.SwitchParameter

reference/7.5/Microsoft.PowerShell.Security/Set-ExecutionPolicy.md

@@ -235,7 +235,7 @@ policy. The policy is set for the default scope, `LocalMachine`.
 The `Get-ExecutionPolicy` cmdlet shows that `RemoteSigned` is the effective execution policy for
 the current PowerShell session.
 
-The `Start-ActivityTracker.ps1 script is executed from the current directory. The script is blocked
+The `Start-ActivityTracker.ps1` script is executed from the current directory. The script is blocked
 by `RemoteSigned` because the script isn't digitally signed.
 
 For this example, the script's code was reviewed and verified as safe to run. The `Unblock-File`