Restyled by prettier-markdown

Author: restyled-commits

docs/guides/ti/ti_factory_data_user_guide.md

@@ -33,17 +33,16 @@ Each element is described in more detail below:
    Developers can configure this per device. Elements in this file are from the
    specification.
 2. Matter Application with dummy factory data: Any TI Matter example application
-3. MCUBoot: MCUBoot image used for OTA. This is built
-   with the Matter application and does not require additional build steps from
-   developers.
+3. MCUBoot: MCUBoot image used for OTA. This is built with the Matter
+   application and does not require additional build steps from developers.
 4. create_factory_data.py: Processes a factory data JSON file and generates a
    hex file with the unique factory data values configured in the JSON file.
 5. factory_data_trim.py: When using the custom factory data option, this script
    removes the dummy factory data which is required to be able to successfully
    compile the application.
 6. `oad`\_and_factory_data_merge_tool.py: Merges the factory data hex, Matter
-   application without factory data and MCUBoot image to generate a
-   functional hex that can be programmed onto the device.
+   application without factory data and MCUBoot image to generate a functional
+   hex that can be programmed onto the device.
 
 ## Flash memory layout
 
@@ -52,8 +51,8 @@ Each element is described in more detail below:
 ## How to use
 
 Out of box factory data location is configured to be on second last page of
-flash. For CC13x4, the starting address is `0xFE800`. This can be configured
-in the linker file.
+flash. For CC13x4, the starting address is `0xFE800`. This can be configured in
+the linker file.
 
 To configure:
 
@@ -95,8 +94,7 @@ FLASH_FACTORY_DATA (R)  : ORIGIN = 0x000fe800, LENGTH = 0x00000900
 
 3. In the example's args.gni file, set 'custom_factory_data' to true
 
-It is recommended to keep 2 dedicated pages for CC13x4 for factory
-data.
+It is recommended to keep 2 dedicated pages for CC13x4 for factory data.
 
 ### Formatting certs and keys for JSON file
 
@@ -113,6 +111,6 @@ being copied into the JSON file.
 The example application can be built using the instructions in the example's
 README. The factory data from the JSON file will be formatted into a hex file
 that will then be merged into the final executable. The final executable will be
-named _{example-application}-mcuboot.hex_ for CC13x4, and the factory data that was
-inputted into the JSON file will be named
+named _{example-application}-mcuboot.hex_ for CC13x4, and the factory data that
+was inputted into the JSON file will be named
 _{example-application}-factory-data.hex_.