Update status-code-0x6bf-0xc002001c.md

Author: v-lianna

support/windows-server/active-directory/status-code-0x6bf-0xc002001c.md

@@ -24,7 +24,7 @@ When you check the **NetSetup.log** file, you see the following entries. For exa
 NetpGetLsaHandle: LsaOpenPolicy on \\<DC name>.<domain>.<tld> failed: 0xc002001c
 NetpGetLsaPrimaryDomain: status: 0xc002001c
 NetpJoinDomain: initiaing a rollback due to earlier errors
-NetpJoinDomain: status of disconnecting from ‘\\<DC name>.<domain>.<tld>’: 0x0
+NetpJoinDomain: status of disconnecting from '\\<DC name>.<domain>.<tld>': 0x0
 NetpDoDomainJoin: status: 0x6bf
 ```
 
@@ -38,68 +38,68 @@ To troubleshoot this issue, use the following steps:
 
 1. Verify the connectivity between the client being joined and the target DC over the required ports and protocols.
 
-|Server port  |Service/Protocol  |
-|---------|---------|
-|Transmission Control Protocol (TCP) 135     |RPC Endpoint Mapper         |
-|TCP 49152 - 65535     |RPC (dynamic ports allocation)         |
-|TCP 445     |Server Message Block (SMB)         |
-|User Datagram Protocol (UDP)/TCP 389     |Lightweight Directory Access Protocol (LDAP)         |
+    |Server port  |Service/Protocol  |
+    |---------|---------|
+    |Transmission Control Protocol (TCP) 135     |RPC Endpoint Mapper         |
+    |TCP 49152 - 65535     |RPC (dynamic ports allocation)         |
+    |TCP 445     |Server Message Block (SMB)         |
+    |User Datagram Protocol (UDP)/TCP 389     |Lightweight Directory Access Protocol (LDAP)         |
 
-Refer to the list of required ports in [How to configure a firewall for Active Directory domains and trusts](config-firewall-for-ad-domains-and-trusts.md).
+    Refer to the list of required ports in [How to configure a firewall for Active Directory domains and trusts](config-firewall-for-ad-domains-and-trusts.md).
 
 2. Test the connection between the client and the DC by running the following cmdlet:
 
-```powershell
-Test-NetConnection <IP_address_of_the_DC> -Port 389
-```
+    ```powershell
+    Test-NetConnection <IP_address_of_the_DC> -Port 389
+    ```
 
-The expected output is:
+    The expected output is:
 
-```output
-ComputerName            : <ComputerName>
-RemoteAddress           : <RemoteAddress>
-RemotePort              : 389
-InterfaceAlias          : Ethernet 2
-SourceAddress           : <SourceAddress>
-TcpTestSucceeded        : True
-```
+    ```output
+    ComputerName            : <ComputerName>
+    RemoteAddress           : <RemoteAddress>
+    RemotePort              : 389
+    InterfaceAlias          : Ethernet 2
+    SourceAddress           : <SourceAddress>
+    TcpTestSucceeded        : True
+    ```
 
-The output indicates that the LDAP port TCP 389 is open between the client and the DC.
+    The output indicates that the LDAP port TCP 389 is open between the client and the DC.
 
 3. Identify if a port (TCP/UDP) is blocked on a DC by using the [PortQry](https://www.microsoft.com/download/details.aspx?id=17148) command-line tool. For more information, see [Using the PortQry command-line tool](../networking/portqry-command-line-port-scanner-v2.md).
 
-Here are some example syntaxes:
-
-- `portqry -n <problem_server> -e 135`
-- `portqry -n <problem_server> -e 445`
-- `portqry -n <problem_server> -e 389`
-- `portqry -n <problem_server> -p UDP -e 389`
-- `portqry -n <problem_server> -r 49152:65535`
-
-Here are some example outputs:
-
-If the connection to TCP 135 port on the DC is blocked, you see the following output:
-
-```output
-C:\PortQryV2>portqry -n dc2 -e 135
-Querying target system called:
- Dc2
-Attempting to resolve name to IP address…
-Name resolved to 192.168.1.2
-querying...
-TCP port 135 <epmap service>: FILTERED
-```
-
-If the connection to TCP 389 port on the DC is successful, you see the following output:
-
-```output
-C:\PortQryV2>portqry -n dc2 -e 389
-Querying target system called:
- Dc2
-Attempting to resolve name to IP address…
-Name resolved to 192.168.1.2
-querying...
-TCP port 389 <ldap service>: LISTENING
-```
+    Here are some example syntaxes:
+
+    - `portqry -n <problem_server> -e 135`
+    - `portqry -n <problem_server> -e 445`
+    - `portqry -n <problem_server> -e 389`
+    - `portqry -n <problem_server> -p UDP -e 389`
+    - `portqry -n <problem_server> -r 49152:65535`
+
+    Here are some example outputs:
+
+    If the connection to TCP 135 port on the DC is blocked, you see the following output:
+
+    ```output
+    C:\PortQryV2>portqry -n dc2 -e 135
+    Querying target system called:
+    Dc2
+    Attempting to resolve name to IP address…
+    Name resolved to 192.168.1.2
+    querying...
+    TCP port 135 <epmap service>: FILTERED
+    ```
+
+    If the connection to TCP 389 port on the DC is successful, you see the following output:
+
+    ```output
+    C:\PortQryV2>portqry -n dc2 -e 389
+    Querying target system called:
+    Dc2
+    Attempting to resolve name to IP address…
+    Name resolved to 192.168.1.2
+    querying...
+    TCP port 389 <ldap service>: LISTENING
+    ```
 
 To determine if there're any further network connectivity problems, collect a network monitor trace if necessary when reproducing the issue.