Merge branch 'master' into fix-2740-examples-format

Author: tiburd

docset/winserver2012-ps/activedirectory/Get-ADUser.md

@@ -36,7 +36,7 @@ Get-ADUser [-AuthType <ADAuthType>] [-Credential <PSCredential>] -LDAPFilter <St
 The **Get-ADUser** cmdlet gets a specified user object or performs a search to get multiple user objects.
 
 The *Identity* parameter specifies the Active Directory user to get.
-You can identify a user by its distinguished name (DN), GUID, security identifier (SID), Security Account Manager (SAM) account name, or name.
+You can identify a user by its distinguished name (DN), GUID, security identifier (SID), or Security Account Manager (SAM) account name.
 You can also set the parameter to a user object variable such as `$<localUserObject>` or pass a user object through the pipeline to the *Identity* parameter.
 
 To search for and retrieve more than one user, use the *Filter* or *LDAPFilter* parameters.

docset/winserver2012-ps/scheduledtasks/New-ScheduledTask.md

@@ -38,18 +38,18 @@ PS C:\> Register-ScheduledTask T1 -InputObject $task
 
 In this example, the set of commands uses several cmdlets and variables to define and then register a scheduled task.
 
-The first command uses the **New-ScheduledTaskAction** cmdlet to assign the executable file tskmgr.exe to the variable $A.
+The first command uses the **New-ScheduledTaskAction** cmdlet to assign the executable file `tskmgr.exe` to the variable `$action`.
 
-The second command uses the **New-ScheduledTaskTrigger** cmdlet to assign the value AtLogon to the variable $T.
+The second command uses the **New-ScheduledTaskTrigger** cmdlet to assign the value `AtLogon` to the variable `$trigger`.
 
-The third command assigns the principal of the scheduled task `Contoso\Administrator` to the variable $P.
+The third command assigns the principal of the scheduled task `Contoso\Administrator` to the variable `$principal`.
 
-The fourth command uses the **New-ScheduledTaskSettingsSet** cmdlet to assign a task settings object to the variable $S.
+The fourth command uses the **New-ScheduledTaskSettingsSet** cmdlet to assign a task settings object to the variable `$settings`.
 
-The fifth command creates a new task and assigns the task definition to the variable $D.
+The fifth command creates a new task and assigns the task definition to the variable `$task`.
 
 The sixth command (hypothetically) runs at a later time.
-It registers the new scheduled task and defines it by using the $D variable.
+It registers the new scheduled task and defines it by using the `$task` variable.
 
 ### Example 2: Define a scheduled task with multiple actions
 ```powershell

docset/winserver2012r2-ps/activedirectory/Get-ADUser.md

@@ -38,7 +38,7 @@ Get-ADUser [-AuthType <ADAuthType>] [-Credential <PSCredential>] -LDAPFilter <St
 The **Get-ADUser** cmdlet gets a specified user object or performs a search to get multiple user objects.
 
 The *Identity* parameter specifies the Active Directory user to get.
-You can identify a user by its distinguished name (DN), GUID, security identifier (SID), Security Account Manager (SAM) account name, or name.
+You can identify a user by its distinguished name (DN), GUID, security identifier (SID), or Security Account Manager (SAM) account name.
 You can also set the parameter to a user object variable such as `$<localUserObject>` or pass a user object through the pipeline to the *Identity* parameter.
 
 To search for and retrieve more than one user, use the *Filter* or *LDAPFilter* parameters.

docset/winserver2012r2-ps/scheduledtasks/New-ScheduledTask.md

@@ -40,18 +40,18 @@ PS C:\> Register-ScheduledTask T1 -InputObject $task
 
 In this example, the set of commands uses several cmdlets and variables to define and then register a scheduled task.
 
-The first command uses the **New-ScheduledTaskAction** cmdlet to assign the executable file tskmgr.exe to the variable $A.
+The first command uses the **New-ScheduledTaskAction** cmdlet to assign the executable file `tskmgr.exe` to the variable `$action`.
 
-The second command uses the **New-ScheduledTaskTrigger** cmdlet to assign the value AtLogon to the variable $T.
+The second command uses the **New-ScheduledTaskTrigger** cmdlet to assign the value `AtLogon` to the variable `$trigger`.
 
-The third command assigns the principal of the scheduled task `Contoso\Administrator` to the variable $P.
+The third command assigns the principal of the scheduled task `Contoso\Administrator` to the variable `$principal`.
 
-The fourth command uses the **New-ScheduledTaskSettingsSet** cmdlet to assign a task settings object to the variable $S.
+The fourth command uses the **New-ScheduledTaskSettingsSet** cmdlet to assign a task settings object to the variable `$settings`.
 
-The fifth command creates a new task and assigns the task definition to the variable $D.
+The fifth command creates a new task and assigns the task definition to the variable `$task`.
 
 The sixth command (hypothetically) runs at a later time.
-It registers the new scheduled task and defines it by using the $D variable.
+It registers the new scheduled task and defines it by using the `$task` variable.
 
 ### Example 2: Define a scheduled task with multiple actions
 ```powershell

docset/winserver2016-ps/activedirectory/Get-ADUser.md

@@ -39,7 +39,7 @@ Get-ADUser [-AuthType <ADAuthType>] [-Credential <PSCredential>] -LDAPFilter <St
 The **Get-ADUser** cmdlet gets a specified user object or performs a search to get multiple user objects.
 
 The *Identity* parameter specifies the Active Directory user to get.
-You can identify a user by its distinguished name (DN), GUID, security identifier (SID), Security Account Manager (SAM) account name, or name.
+You can identify a user by its distinguished name (DN), GUID, security identifier (SID), or Security Account Manager (SAM) account name.
 You can also set the parameter to a user object variable such as `$<localUserObject>` or pass a user object through the pipeline to the *Identity* parameter.
 
 To search for and retrieve more than one user, use the *Filter* or *LDAPFilter* parameters.

docset/winserver2016-ps/scheduledtasks/New-ScheduledTask.md

@@ -41,18 +41,18 @@ PS C:\> Register-ScheduledTask T1 -InputObject $task
 
 In this example, the set of commands uses several cmdlets and variables to define and then register a scheduled task.
 
-The first command uses the **New-ScheduledTaskAction** cmdlet to assign the executable file tskmgr.exe to the variable $A.
+The first command uses the **New-ScheduledTaskAction** cmdlet to assign the executable file `tskmgr.exe` to the variable `$action`.
 
-The second command uses the **New-ScheduledTaskTrigger** cmdlet to assign the value AtLogon to the variable $T.
+The second command uses the **New-ScheduledTaskTrigger** cmdlet to assign the value `AtLogon` to the variable `$trigger`.
 
-The third command assigns the principal of the scheduled task `Contoso\Administrator` to the variable $P.
+The third command assigns the principal of the scheduled task `Contoso\Administrator` to the variable `$principal`.
 
-The fourth command uses the **New-ScheduledTaskSettingsSet** cmdlet to assign a task settings object to the variable $S.
+The fourth command uses the **New-ScheduledTaskSettingsSet** cmdlet to assign a task settings object to the variable `$settings`.
 
-The fifth command creates a new task and assigns the task definition to the variable $D.
+The fifth command creates a new task and assigns the task definition to the variable `$task`.
 
 The sixth command (hypothetically) runs at a later time.
-It registers the new scheduled task and defines it by using the $D variable.
+It registers the new scheduled task and defines it by using the `$task` variable.
 
 ### Example 2: Define a scheduled task with multiple actions
 ```powershell

docset/winserver2019-ps/activedirectory/Get-ADUser.md

@@ -39,7 +39,7 @@ Get-ADUser [-AuthType <ADAuthType>] [-Credential <PSCredential>] -LDAPFilter <St
 The **Get-ADUser** cmdlet gets a specified user object or performs a search to get multiple user objects.
 
 The *Identity* parameter specifies the Active Directory user to get.
-You can identify a user by its distinguished name (DN), GUID, security identifier (SID), Security Account Manager (SAM) account name, or name.
+You can identify a user by its distinguished name (DN), GUID, security identifier (SID), or Security Account Manager (SAM) account name.
 You can also set the parameter to a user object variable such as `$<localUserObject>` or pass a user object through the pipeline to the *Identity* parameter.
 
 To search for and retrieve more than one user, use the *Filter* or *LDAPFilter* parameters.

docset/winserver2019-ps/scheduledtasks/New-ScheduledTask.md

@@ -41,18 +41,18 @@ PS C:\> Register-ScheduledTask T1 -InputObject $task
 
 In this example, the set of commands uses several cmdlets and variables to define and then register a scheduled task.
 
-The first command uses the **New-ScheduledTaskAction** cmdlet to assign the executable file tskmgr.exe to the variable $A.
+The first command uses the **New-ScheduledTaskAction** cmdlet to assign the executable file `tskmgr.exe` to the variable `$action`.
 
-The second command uses the **New-ScheduledTaskTrigger** cmdlet to assign the value AtLogon to the variable $T.
+The second command uses the **New-ScheduledTaskTrigger** cmdlet to assign the value `AtLogon` to the variable `$trigger`.
 
-The third command assigns the principal of the scheduled task `Contoso\Administrator` to the variable $P.
+The third command assigns the principal of the scheduled task `Contoso\Administrator` to the variable `$principal`.
 
-The fourth command uses the **New-ScheduledTaskSettingsSet** cmdlet to assign a task settings object to the variable $S.
+The fourth command uses the **New-ScheduledTaskSettingsSet** cmdlet to assign a task settings object to the variable `$settings`.
 
-The fifth command creates a new task and assigns the task definition to the variable $D.
+The fifth command creates a new task and assigns the task definition to the variable `$task`.
 
 The sixth command (hypothetically) runs at a later time.
-It registers the new scheduled task and defines it by using the $D variable.
+It registers the new scheduled task and defines it by using the `$task` variable.
 
 ### Example 2: Define a scheduled task with multiple actions
 ```powershell

docset/winserver2022-ps/activedirectory/Get-ADUser.md

@@ -39,7 +39,7 @@ Get-ADUser [-AuthType <ADAuthType>] [-Credential <PSCredential>] -LDAPFilter <St
 The **Get-ADUser** cmdlet gets a specified user object or performs a search to get multiple user objects.
 
 The *Identity* parameter specifies the Active Directory user to get.
-You can identify a user by its distinguished name (DN), GUID, security identifier (SID), Security Account Manager (SAM) account name, or name.
+You can identify a user by its distinguished name (DN), GUID, security identifier (SID), or Security Account Manager (SAM) account name.
 You can also set the parameter to a user object variable such as `$<localUserObject>` or pass a user object through the pipeline to the *Identity* parameter.
 
 To search for and retrieve more than one user, use the *Filter* or *LDAPFilter* parameters.

docset/winserver2022-ps/scheduledtasks/New-ScheduledTask.md

@@ -41,18 +41,18 @@ PS C:\> Register-ScheduledTask T1 -InputObject $task
 
 In this example, the set of commands uses several cmdlets and variables to define and then register a scheduled task.
 
-The first command uses the **New-ScheduledTaskAction** cmdlet to assign the executable file tskmgr.exe to the variable $A.
+The first command uses the **New-ScheduledTaskAction** cmdlet to assign the executable file `tskmgr.exe` to the variable `$action`.
 
-The second command uses the **New-ScheduledTaskTrigger** cmdlet to assign the value AtLogon to the variable $T.
+The second command uses the **New-ScheduledTaskTrigger** cmdlet to assign the value `AtLogon` to the variable `$trigger`.
 
-The third command assigns the principal of the scheduled task `Contoso\Administrator` to the variable $P.
+The third command assigns the principal of the scheduled task `Contoso\Administrator` to the variable `$principal`.
 
-The fourth command uses the **New-ScheduledTaskSettingsSet** cmdlet to assign a task settings object to the variable $S.
+The fourth command uses the **New-ScheduledTaskSettingsSet** cmdlet to assign a task settings object to the variable `$settings`.
 
-The fifth command creates a new task and assigns the task definition to the variable $D.
+The fifth command creates a new task and assigns the task definition to the variable `$task`.
 
 The sixth command (hypothetically) runs at a later time.
-It registers the new scheduled task and defines it by using the $D variable.
+It registers the new scheduled task and defines it by using the `$task` variable.
 
 ### Example 2: Define a scheduled task with multiple actions
 ```powershell