update per reviewer's comments

Author: v-lianna

support/windows-server/active-directory/active-directory-domain-join-troubleshooting-guidance.md

@@ -57,25 +57,7 @@ For more information, see [Error code 0x569: The user has not been granted the r
 
 ### Error code 0x6BF or 0xC002001C
 
-> The remote procedure call failed and did not execute.
-
-Here's an example from the *netsetup.log* file:
-
-```output
-mm/dd/yyyy hh:mm:ss:ms NetpGetLsaHandle: LsaOpenPolicy on \\<DC name>.<domain>.<tld> failed: 0xc002001c
-mm/dd/yyyy hh:mm:ss:ms NetpGetLsaPrimaryDomain: status: 0xc002001c
-mm/dd/yyyy hh:mm:ss:ms NetpJoinDomain: initiaing a rollback due to earlier errors
-mm/dd/yyyy hh:mm:ss:ms NetpJoinDomain: status of disconnecting from '\\<DC name>.<domain>.<tld>': 0x0
-mm/dd/yyyy hh:mm:ss:ms NetpDoDomainJoin: status: 0x6bf
-```
-
-This error occurs when a network device (router, firewall, or VPN device) rejects network packets between the client being joined and the DC.
-
-Make sure of the following items:
-
-- Verify the connectivity between the client being joined and the target DC over the required ports and protocols.
-- Disable bind time feature negotiation.
-- Disable TCP Chimney Offload and IP offload.
+For more information, see [Status code 0x6bf or 0xc002001c: The remote procedure call failed and did not execute](status-code-0x6bf-0xc002001c.md).
 
 ### Error code 0x6D9
 

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

@@ -32,9 +32,9 @@ NetpDoDomainJoin: status: 0x6bf
 
 This error occurs when a network device (router, firewall, or virtual private network (VPN) device) rejects network packets between the client being joined and the domain controller (DC).
 
-The difference to error 0x6BA (RPC_S_SERVER_UNAVAILABLE) is that with 0x6BA, the device can't create the TCP session to the server port. With error 0x6bf, the TCP session can be created, but the RPC request message can't be delivered successfully, and the TCP session is reset.
+The difference to error 0x6ba (RPC_S_SERVER_UNAVAILABLE) is that with 0x6ba, the device can't create the TCP session to the server port. With error 0x6bf, the TCP session can be created, but the RPC request message can't be delivered successfully, and the TCP session is reset.
 
-Another variation of an RPC network session problem is error 0x6BE (RPC_S_CALL_FAILED). In this case, the RPC request message can be delivered, but the TCP session is reset before the response is received.
+Another variation of an RPC network session problem is error 0x6be (RPC_S_CALL_FAILED). In this case, the RPC request message can be delivered, but the TCP session is reset before the response is received.
 
 ## Verify and test the connection
 
@@ -106,4 +106,4 @@ To troubleshoot this issue, use the following steps:
     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.
+To determine if there're any further network connectivity problems, collect a network trace if necessary when reproducing the issue. You can use `netsh trace` to generate an ETL file, and [convert the ETL file to a PCAP file](https://techcommunity.microsoft.com/blog/coreinfrastructureandsecurityblog/converting-etl-files-to-pcap-files/1133297), which Wireshark can read.