Restyled by prettier-markdown

Author: restyled-commits

docs/guides/nxp/nxp_otbr_guide.md

@@ -1,6 +1,7 @@
 # Thread Border Router usage
 
-This document describes the use of the Thread Border router and secondary netwok interface for a Matter application
+This document describes the use of the Thread Border router and secondary netwok
+interface for a Matter application
 
 <hr>
 
@@ -15,42 +16,63 @@ This document describes the use of the Thread Border router and secondary netwok
 
 ## Thread Border Router overwiew
 
-This section contains an overview of the Border Router architecture and describes the general use cases.
+This section contains an overview of the Border Router architecture and
+describes the general use cases.
 
 <a name="using-the-thread-border-router-management-cluster"></a>
 
 ## Using the Thread Border Router management cluster
 
-The Thread Border Router management cluster allows provisioning of the Thread interface using a Matter commissioner. 
+The Thread Border Router management cluster allows provisioning of the Thread
+interface using a Matter commissioner.
 
-After the device has been provisioned over WIFI the set active dataset command can be used to configure the Thread active dataset on the border router. Once the dataset is set successfully the Thread network interface will be enabled and the device will create a new PAN or join an existing one if already present. Note that this command cannot be used on a device that already has an active dataset configured. In this situation the set pending dataset command must be used instead.
+After the device has been provisioned over WIFI the set active dataset command
+can be used to configure the Thread active dataset on the border router. Once
+the dataset is set successfully the Thread network interface will be enabled and
+the device will create a new PAN or join an existing one if already present.
+Note that this command cannot be used on a device that already has an active
+dataset configured. In this situation the set pending dataset command must be
+used instead.
 
-Before using the set active dataset command a fail-safe timer must be armed (recommend using a timeout of 120 seconds):
+Before using the set active dataset command a fail-safe timer must be armed
+(recommend using a timeout of 120 seconds):
 
 ```
 ubuntu@ubuntu:~$ ./chip-tool generalcommissioning arm-fail-safe timeout-seconds 1 node-id 0
 ```
-Then an active dataset in HEX TLV format (the same type used to provision a Matter over Thread device using the `ble-thread` command) can be used to provision the Border Router. What the active dataset should be is outside the scope of this README but as an example one can be obtained from the OpenThread cli on an already provisioned device using the `dataset active -x` command.
 
-Note that the Thread Border Router management cluster has been set to endpoint 2 in the zap file.
+Then an active dataset in HEX TLV format (the same type used to provision a
+Matter over Thread device using the `ble-thread` command) can be used to
+provision the Border Router. What the active dataset should be is outside the
+scope of this README but as an example one can be obtained from the OpenThread
+cli on an already provisioned device using the `dataset active -x` command.
+
+Note that the Thread Border Router management cluster has been set to endpoint 2
+in the zap file.
 
 ```
 ubuntu@ubuntu:~$ ./chip-tool threadborderroutermanagement set-active-dataset-request hex:<active-dataset> node id 2
 ```
 
-If the active dataset command is successful, a commissioning complete command must be send to disarm the fail-safe timer and commit the configuration to non-volatile storage.
+If the active dataset command is successful, a commissioning complete command
+must be send to disarm the fail-safe timer and commit the configuration to
+non-volatile storage.
 
 ```
 ubuntu@ubuntu:~$ ./chip-tool-19-jul generalcommissioning commissioning-complete node-id 0
 ```
 
-Note that this command cannot be used on a device that already has an active dataset configured. In this situation the set pending dataset command must be used instead.
+Note that this command cannot be used on a device that already has an active
+dataset configured. In this situation the set pending dataset command must be
+used instead.
 
 ```
 ubuntu@ubuntu:~$ ./chip-tool threadborderroutermanagement set-pending-dataset-request hex:<active-dataset> node id 2
 ```
 
-To read the active dataset of an already provisioned device, for example to make a joining Border Router use the same Thread network as an already configured one, the get active dataset command can be used:
+To read the active dataset of an already provisioned device, for example to make
+a joining Border Router use the same Thread network as an already configured
+one, the get active dataset command can be used:
 
 ```
 ubuntu@ubuntu:~$ ./chip-tool-19-jul threadborderroutermanagement get-active-dataset-request node-id 2
@@ -60,8 +82,12 @@ ubuntu@ubuntu:~$ ./chip-tool-19-jul threadborderroutermanagement get-active-data
 
 ## Using the Secondary Network commissioning interface
 
-To use the secondary network commissioning interface over Thread the device must not be provisioned over WIFI.
-The regular `ble-thread` pairing is used as for any other Matter over Thread device. The chip-tool will read all the endpoints of the device and discover Thread network commissioning cluster on endpoint 3 and use that to provision the device. As for any other Matter over Thread device a Thread Border Router is required in this case.
+To use the secondary network commissioning interface over Thread the device must
+not be provisioned over WIFI. The regular `ble-thread` pairing is used as for
+any other Matter over Thread device. The chip-tool will read all the endpoints
+of the device and discover Thread network commissioning cluster on endpoint 3
+and use that to provision the device. As for any other Matter over Thread device
+a Thread Border Router is required in this case.
 
 ```
 ubuntu@ubuntu:~$ ./chip-tool pairing ble-thread node-id hex:<active-dataset> 20202021 3840
@@ -71,6 +97,10 @@ ubuntu@ubuntu:~$ ./chip-tool pairing ble-thread node-id hex:<active-dataset> 202
 
 ## Using the Thread credential sharing mechanism
 
-The details about using the credential sharing mechanism are in the ot-nxp repo border router application [readme](https://github.com/NXP/ot-nxp/blob/v1.4.0-pvw1/examples/br/README-OTBR.md). See `Ephemeral Key functionality` section.
+The details about using the credential sharing mechanism are in the ot-nxp repo
+border router application
+[readme](https://github.com/NXP/ot-nxp/blob/v1.4.0-pvw1/examples/br/README-OTBR.md).
+See `Ephemeral Key functionality` section.
 
-Note that all OpenThread commands executed from then Matter CLI must have `otcli` prepended before the command.
+Note that all OpenThread commands executed from then Matter CLI must have
+`otcli` prepended before the command.

examples/all-clusters-app/nxp/rt/rw61x/README.md

@@ -125,10 +125,13 @@ user@ubuntu:~/Desktop/git/connectedhomeip/examples/all-clusters-app/nxp/rt/rw61x
 
 #### Building with Matter over Wifi + OpenThread Border Router configuration on RW612
 
-This configuration supports the Thread Border Router management cluster to provision the Thread credentials. Enabling the Matter CLI in order to control the
-Thread network on the Border Router is optional but recommended for other features like the Thread credential sharing.
+This configuration supports the Thread Border Router management cluster to
+provision the Thread credentials. Enabling the Matter CLI in order to control
+the Thread network on the Border Router is optional but recommended for other
+features like the Thread credential sharing.
 
-Note that the Thread Border Router management cluster is only supported on the thermostat application for now.
+Note that the Thread Border Router management cluster is only supported on the
+thermostat application for now.
 
 -   Build Matter with Border Router configuration with BLE commissioning
     (ble-wifi) :
@@ -147,7 +150,11 @@ Optional GN options that can be added when building an application:
 
 -   To enable the
     [secondary network commissioning interface](../../../../../docs/guides/nxp/nxp_otbr_guide.md#using-the-secondary-network-commissioning-interface),
-    the arguments `chip_enable_secondary_nwk_if=true` and `chip_device_config_thread_network_endpoint_id=2` must be added to the _gn gen_ command. Note that this is only supported when building the Matter over Wifi + OpenThread Border Router configuration. Note that is only supported on the on the thermostat application for now.
+    the arguments `chip_enable_secondary_nwk_if=true` and
+    `chip_device_config_thread_network_endpoint_id=2` must be added to the _gn
+    gen_ command. Note that this is only supported when building the Matter over
+    Wifi + OpenThread Border Router configuration. Note that is only supported
+    on the on the thermostat application for now.
 -   To enable the
     [matter CLI](README.md#testing-the-all-clusters-application-with-matter-cli-enabled),
     the argument `chip_enable_matter_cli=true` must be added to the _gn gen_
@@ -271,12 +278,13 @@ The "ble-thread" pairing method can be used in order to commission the device.
 
 #### Matter over wifi with openthread border router configuration :
 
-In order to create or join a Thread network on the Matter Border Router, the TBR management cluster or the 
-`otcli` commands from the matter CLI can be used. For more information about using the TBR management cluster follow instructions from ['Using the TBR management cluster'](../../../../../docs/guides/nxp/nxp_otbr_guide.md#using-the-thread-border-router-management-cluster).
+In order to create or join a Thread network on the Matter Border Router, the TBR
+management cluster or the `otcli` commands from the matter CLI can be used. For
+more information about using the TBR management cluster follow instructions from
+['Using the TBR management cluster'](../../../../../docs/guides/nxp/nxp_otbr_guide.md#using-the-thread-border-router-management-cluster).
 For more information about using the matter shell, follow instructions from
 ['Testing the all-clusters application with Matter CLI'](#testing-the-all-clusters-application-with-matter-cli-enabled).
 
-
 In this configuration, the device can be commissioned over Wi-Fi with the
 'ble-wifi' pairing method.
 
@@ -391,6 +399,7 @@ Done
 leader
 Done
 ```
+
 <a name="ota-software-update"></a>
 
 ## OTA Software Update
@@ -404,6 +413,8 @@ dedicated guide
 
 ## Thread Border Router overwiew
 
-To enable Thread Border Router support see the [build](README.md#building) section.
+To enable Thread Border Router support see the [build](README.md#building)
+section.
 
-The complete Border Router guide is located [here](../../../../../docs/guides/nxp/nxp_otbr_guide.md).
+The complete Border Router guide is located
+[here](../../../../../docs/guides/nxp/nxp_otbr_guide.md).