Restyle [nrfconnect] Added support for WiFi communication

docs/guides/nrfconnect_factory_data_configuration.md

@@ -558,9 +558,10 @@ Alternatively, you can also add `CONFIG_CHIP_FACTORY_DATA_BUILD=y` Kconfig
 setting to the example's `prj.conf` file.
 
 Each factory data parameter has a default value. These are described in the
-[Kconfig file](https://github.com/project-chip/connectedhomeip/blob/master/config/nrfconnect/chip-module/Kconfig). Setting a new value
-for the factory data parameter can be done either by providing it as a build
-argument list or by using interactive Kconfig interfaces.
+[Kconfig file](https://github.com/project-chip/connectedhomeip/blob/master/config/nrfconnect/chip-module/Kconfig).
+Setting a new value for the factory data parameter can be done either by
+providing it as a build argument list or by using interactive Kconfig
+interfaces.
 
 ### Providing factory data parameters as a build argument list
 
@@ -581,8 +582,8 @@ Alternatively, you can add the relevant Kconfig option lines to the example's
 You can edit all configuration options using the interactive Kconfig interface.
 
 See the
-[Configuring nRF Connect examples](./nrfconnect_examples_configuration.md)
-page for information about how to configure Kconfig options.
+[Configuring nRF Connect examples](./nrfconnect_examples_configuration.md) page
+for information about how to configure Kconfig options.
 
 In the configuration window, expand the items
 `Modules -> connectedhomeip (/home/arbl/matter/connectedhomeip/config/nrfconnect/chip-module) -> Connected Home over IP protocol stack`.
@@ -690,15 +691,18 @@ file containing all [factory data components](#factory-data-components) in any
 format and then implement a parser to read out all parameters and pass them to a
 provider. Each manufacturer can implement a factory data set on its own by
 implementing a parser and a factory data accessor inside the Matter stack. Use
-the [nRF Connect Provider](https://github.com/project-chip/connectedhomeip/blob/master/src/platform/nrfconnect/FactoryDataProvider.h)
-and [FactoryDataParser](https://github.com/project-chip/connectedhomeip/blob/master/src/platform/nrfconnect/FactoryDataParser.h) as
-examples.
+the
+[nRF Connect Provider](https://github.com/project-chip/connectedhomeip/blob/master/src/platform/nrfconnect/FactoryDataProvider.h)
+and
+[FactoryDataParser](https://github.com/project-chip/connectedhomeip/blob/master/src/platform/nrfconnect/FactoryDataParser.h)
+as examples.
 
 You can read the factory data set from the device's flash memory in different
 ways, depending on the purpose and the format. In the nRF Connect example, the
 factory data is stored in the CBOR format. The device uses the
-[Factory Data Parser](https://github.com/project-chip/connectedhomeip/blob/master/src/platform/nrfconnect/FactoryDataParser.h) to read
-out raw data, decode it, and store it in the `FactoryData` structure. The
+[Factory Data Parser](https://github.com/project-chip/connectedhomeip/blob/master/src/platform/nrfconnect/FactoryDataParser.h)
+to read out raw data, decode it, and store it in the `FactoryData` structure.
+The
 [Factor Data Provider](https://github.com/project-chip/connectedhomeip/blob/master/src/platform/nrfconnect/FactoryDataProvider.c)
 implementation uses this parser to get all needed factory data parameters and
 provide them to the Matter core.

zephyr/module.yml

@@ -10,5 +10,5 @@ build:
     cmake: config/nrfconnect/chip-module
     kconfig: config/nrfconnect/chip-module/Kconfig
     depends:
-    - nrfxlib
-    - openthread
+        - nrfxlib
+        - openthread