Update chip-tool pairing documentation to match current behavior. (pr…

…oject-chip#10292)

docs/QUICK_START.md

@@ -32,7 +32,11 @@ controller.
 
 #### IP Pairing
 
-`chip-tool pairing onnetwork 34567890` will use PASE over IP to pair a device.
+`chip-tool pairing onnetwork 20202021` will use PASE over IP to pair a device.
+
+NOTE: On Linux, if the device is actually running after unit tests ran you have
+to use `chip-tool pairing onnetwork 34567890`, because the unit tests change the
+device configuration.
 
 NOTE: to run both the Node and Controller as separate processes on the same
 Linux or Mac machine, build the all-clusters-app with BLE disabled as follows:

examples/chip-tool/README.md

@@ -78,10 +78,20 @@ or equivalently:
 
 #### Pair a device over IP
 
-The command below will pair to a localhost device (`::1`) running the
-`all-clusters-app` on the default port (`5540`) over IPv6:
+The command below will discover devices and try to pair with the first one it
+discovers using the provided setup code.
 
-    $ chip-tool pairing onnetwork 0 20202021 3840 ::1 5540
+    $ chip-tool pairing onnetwork 20202021
+
+The command below will discover devices with long discriminator 3840 and try to
+pair with the first one it discovers using the provided setup code.
+
+    $ chip-tool pairing onnetwork-long 20202021 3840
+
+The command below will discover devices based on the given QR code (which
+devices log when they start up) and try to pair with the first one it discovers.
+
+    $ chip-tool pairing qrcode MT:#######
 
 ### Forget the currently-commissioned device
 

examples/ota-requestor-app/linux/README.md

@@ -22,7 +22,7 @@ In one terminal:
 In a second terminal:
 
 ```
-./chip-tool pairing onnetwork 0 20202021 3840 ::1 5540
+./chip-tool pairing onnetwork-long 20202021 3840
 ./chip-ota-requestor-app [-p <provider node id>]
 ```