Fix build error

Author: sdwheeler

docset/winserver2022-ps/grouppolicy/Get-GPPermission.md

@@ -48,9 +48,9 @@ Get-GPPermission -Name "TestGpo" -TargetName "Domain Users" -TargetType Group
 ```
 
 ```Output
-Trustee         : Domain Users 
-TrusteeType     : Group 
-PermissionLevel : GpoRead 
+Trustee         : Domain Users
+TrusteeType     : Group
+PermissionLevel : GpoRead
 Inherited       : False
 ```
 
@@ -73,50 +73,50 @@ This command gets the permission level for the Domain Admins group on the GPO wi
 `fa4a9473-6e2a-4b78-175e68d97bde` in the `Sales.Contoso.com` domain. The `DC1.sales.contoso.com`
 domain controller is contacted to complete the operation.
 
-If the domain of the user that is running the session (or, for startup and shutdown scripts, the
-computer) is different from the sales.contoso.com domain, a trust must exist between the two
+If the domain of the user that's running the session (or, for startup and shutdown scripts, the
+computer) is different from the `sales.contoso.com` domain, a trust must exist between the two
 domains, or the command fails.
 
 ### Example 3: Get the permission level for all security principals on the specified GPO
 
 ```powershell
-Get-GPPermission -Name "TestGPO" -All 
+Get-GPPermission -Name "TestGPO" -All
 ```
 
 ```Output
-Trustee     : Authenticated Users 
-TrusteeType : WellKnownGroup 
-Permission  : GpoApply 
-Inherited   : False 
-
-Trustee     : Domain Admins 
-TrusteeType : Group 
-Permission  : GpoEditDeleteModifySecurity 
-Inherited   : False 
-
-Trustee     : Enterprise Admins 
-TrusteeType : Group 
-Permission  : GpoEditDeleteModifySecurity 
-Inherited   : False 
-
-Trustee     : ENTERPRISE DOMAIN CONTROLLERS 
-TrusteeType : WellKnownGroup 
-Permission  : GpoRead 
-Inherited   : False 
-
-Trustee     : SYSTEM 
-TrusteeType : WellKnownGroup 
-Permission  : GpoEditDeleteModifySecurity 
+Trustee     : Authenticated Users
+TrusteeType : WellKnownGroup
+Permission  : GpoApply
+Inherited   : False
+
+Trustee     : Domain Admins
+TrusteeType : Group
+Permission  : GpoEditDeleteModifySecurity
+Inherited   : False
+
+Trustee     : Enterprise Admins
+TrusteeType : Group
+Permission  : GpoEditDeleteModifySecurity
+Inherited   : False
+
+Trustee     : ENTERPRISE DOMAIN CONTROLLERS
+TrusteeType : WellKnownGroup
+Permission  : GpoRead
+Inherited   : False
+
+Trustee     : SYSTEM
+TrusteeType : WellKnownGroup
+Permission  : GpoEditDeleteModifySecurity
 Inherited   : False
 ```
 
 This command gets the permission level for each security principal that has permissions on the GPO
-named TestGPO.
+named `TestGPO`.
 
 ### Example 4: Get the display name of each GPO for a specific permissions
 
 ```powershell
-Get-GPO -All | ForEach-Object { 
+Get-GPO -All | ForEach-Object {
     if ( $_ |
             $params = @{
                 TargetName  = 'contoso\Domain Admins'
@@ -130,26 +130,27 @@ Get-GPO -All | ForEach-Object {
 ```
 
 ```Output
-Default Domain Policy 
-TestGPO-1 
-TestGPO-2 Default Domain Controllers Policy 
-Internet Security 
+Default Domain Policy
+TestGPO-1
+TestGPO-2 Default Domain Controllers Policy
+Internet Security
 TestGPO
 ```
 
 This command lists the display name of each GPO (in the domain) on which the specified security
 principal has permissions.
 
-First, `Get-GPO` is used to retrieve all the GPOs in the domain (**Get-GPO -All**). Then, the
-collection is piped into the `Foreach-Object` command. As each GPO is evaluated, it is piped into
-`Get-GPPermissions`. If a permission level is returned, the DisplayName property of the GPO is
-printed ($_.DisplayName).
+First, `Get-GPO` is used to retrieve all the GPOs in the domain (`Get-GPO -All`). Then, the
+collection is piped into the `Foreach-Object` command. As each GPO is evaluated, it's piped into
+`Get-GPPermissions`. If a permission level is returned, the **DisplayName** property of the GPO is
+printed.
 
-Note: The ErrorAction parameter is set to SilentlyContinue for Get-GPPermissions. This is because a
-non-terminating error occurs if the specified security principal does not have permissions on the
-GPO. Specifying the ErrorAction as SilentlyContinue prevents the error messages from being printed
-for GPOS on which the security principal does not have permissions. For more information about the
-ErrorAction parameter, see about_CommonParameters.
+The **ErrorAction** parameter is set to `SilentlyContinue`. This is because a non-terminating error
+occurs if the specified security principal doesn't have permissions on the GPO. Specifying the
+**ErrorAction** as `SilentlyContinue` prevents the error messages from being printed for GPOS on
+which the security principal doesn't have permissions. For more information about the
+**ErrorAction** parameter, see
+[about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
 
 ## PARAMETERS
 
@@ -161,7 +162,7 @@ permissions on the GPO.
 ```yaml
 Type: System.Management.Automation.SwitchParameter
 Parameter Sets: (All)
-Aliases: 
+Aliases:
 
 Required: False
 Position: Named
@@ -172,17 +173,14 @@ Accept wildcard characters: False
 
 ### -DomainName
 
-Specifies the domain for this cmdlet.
-You must specify the fully qualified domain name (FQDN) of the domain. 
+Specifies the domain for this cmdlet. You must specify the fully qualified domain name (FQDN) of the
+domain. The GPO specified must exist in this domain.
 
-For the `Get-GPPermission` cmdlet, the GPO for which to get the permission level must exist in
-this domain.
-
-If you do not specify the **Domain** parameter, the domain of the user that is running the current
+If you don't specify the **Domain** parameter, the domain of the user that's running the current
 session is used. If the cmdlet is being run from a computer startup or shutdown script, the domain
 of the computer is used. For more information, see the Notes section in the full Help.
 
-If you specify a domain that is different from the domain of the user that is running the current
+If you specify a domain that's different from the domain of the user that's running the current
 session (or, for a startup or shutdown script, the computer), a trust must exist between that domain
 and the domain of the user or the computer.
 
@@ -204,7 +202,7 @@ Accept wildcard characters: False
 ### -Guid
 
 Specifies the GPO from which to retrieve the permission level by its globally unique identifier
-(GUID). The GUID uniquely identifies the GPO.
+(GUID). The `GUID` uniquely identifies the GPO.
 
 You can also refer to the **Guid** parameter by its built-in alias, **Id**. For more information,
 see [about_Aliases](/powershell/module/microsoft.powershell.core/about/about_aliases).
@@ -225,7 +223,7 @@ Accept wildcard characters: False
 
 Specifies the GPO from which to retrieve the permission level by its display name.
 
-The display name is not guaranteed to be unique in the domain. If another GPO with the same display
+The display name isn't guaranteed to be unique in the domain. If another GPO with the same display
 name exists in the domain an error occurs. You can use the **Guid** parameter to uniquely identify a
 GPO.
 
@@ -249,7 +247,7 @@ Accept wildcard characters: False
 Specifies the name of the domain controller that this cmdlet contacts to complete the operation. You
 can specify either the fully qualified domain name (FQDN) or the host name.
 
-If you do not specify the name by using the **Server** parameter, the PDC emulator is contacted.
+If you don't specify the name using the **Server** parameter, the PDC emulator is contacted.
 
 You can also refer to the **Server** parameter by its built-in alias, **DC**. For more information,
 see [about_Aliases](/powershell/module/microsoft.powershell.core/about/about_aliases).
@@ -274,16 +272,14 @@ security principal (domain\account) or just its name.
 
 For instance, in the `contoso.com` domain, to specify:
 
-- The user someuser, use `contoso\someuser` or `someuser`.
-
+- The username, use `contoso\someuser` or `someuser`.
 - The Domain Admins security group, use `contoso\Domain Admins` or `Domain Admins`.
-
-- The computer computer-01, use `contoso\computer-01` or `computer-01`.
+- The computer name, use `contoso\computer-01` or `computer-01`.
 
 ```yaml
 Type: System.String
 Parameter Sets: (All)
-Aliases: 
+Aliases:
 
 Required: False
 Position: Named
@@ -294,20 +290,17 @@ Accept wildcard characters: False
 
 ### -TargetType
 
-The type of security principal for which to get the permission level.
-
-The acceptable values for this parameter are:
+The type of security principal for which to get the permission level. The acceptable values for this
+parameter are:
 
 - Computer
-
 - User
-
 - Group
 
 ```yaml
 Type: PermissionTrusteeType
 Parameter Sets: (All)
-Aliases: 
+Aliases:
 Accepted values: Computer, User, Group
 
 Required: False
@@ -333,26 +326,26 @@ GPOs from different domains are not supported.
 
 ## OUTPUTS
 
-###
+### Microsoft.GroupPolicy.GPPermissionCollection
+
+### Microsoft.GroupPolicy.GPPermission
 
 This cmdlet returns an object that represents permissions for the specified security principal
 (user, group, or computer) on the GPO.
 
 ## NOTES
 
-* You can use the *DomainName* parameter to explicitly specify the domain for this cmdlet.
-
-  If you do not explicitly specify the domain, the cmdlet uses the default domain. The default
-  domain is the domain that is used to access network resources by the security context under which
-  the current session is running. This domain is typically the domain of the user that is running
-  the session. For example, the domain of the user who started the session by opening Windows
-  PowerShell or the domain of a user that is specified in a runas command. However, computer startup
-  and shutdown scripts run under the context of the LocalSystem account. The LocalSystem account is
-  a built-in local account, and it accesses network resources under the context of the computer
-  account. Therefore, when this cmdlet is run from a startup or shutdown script, the default domain
-  is the domain to which the computer is joined.
+You can use the **DomainName** parameter to explicitly specify the domain for this cmdlet. If you do
+not explicitly specify the domain, the cmdlet uses the default domain. The default domain is the
+domain that is used to access network resources by the security context under which the current
+session is running. This domain is typically the domain of the user that is running the session. For
+example, the domain of the user who started the session by opening Windows PowerShell or the domain
+of a user that is specified in a runas command. However, computer startup and shutdown scripts run
+under the context of the LocalSystem account. The LocalSystem account is a built-in local account,
+and it accesses network resources under the context of the computer account. Therefore, when this
+cmdlet is run from a startup or shutdown script, the default domain is the domain to which the
+computer is joined.
 
 ## RELATED LINKS
 
 [Set-GPPermission](./Set-GPPermission.md)
-