diff --git a/examples/ota-requestor-app/efr32/README.md b/examples/ota-requestor-app/efr32/README.md
index f68d38f34221ce..e18d3d2a96cd32 100644
--- a/examples/ota-requestor-app/efr32/README.md
+++ b/examples/ota-requestor-app/efr32/README.md
@@ -82,8 +82,8 @@ See `examples/lighting-app/efr32/README.md`
 
            commander gbl create chip-efr32-ota-requestor-example.gbl --app chip-efr32-ota-requestor-example.s37
 
--   In a terminal start the provider app passing to it the path to the bootable image
-    file created in the previous step:
+-   In a terminal start the provider app passing to it the path to the bootable
+    image file created in the previous step:
 
            ./out/debug/chip-ota-provider-app -f chip-efr32-ota-requestor-example.gbl
 
@@ -105,5 +105,6 @@ where operationalDataset is obtained from the Open Thread Border Router.
 
             ./out/chip-tool otasoftwareupdaterequestor announce-ota-provider 1 0 0 0 2 0
 
--   The Requestor will connect to the Provider and start the image download. Once the image is downloaded
-    the Requestor will reboot into the downloaded image.
+-   The Requestor will connect to the Provider and start the image download.
+    Once the image is downloaded the Requestor will reboot into the downloaded
+    image.
diff --git a/examples/ota-requestor-app/linux/README.md b/examples/ota-requestor-app/linux/README.md
index 77afa80e099164..516fbad3e07855 100644
--- a/examples/ota-requestor-app/linux/README.md
+++ b/examples/ota-requestor-app/linux/README.md
@@ -63,16 +63,21 @@ In terminal 2:
 
 ## Note
 
-When the Provider, Requestor and chip-tool are run on the same Linux node the user must issue `rm -r /tmp/chip_*` before starting the Provider and `rm /tmp/chip_kvs` before starting the Requestor. These commands reset the shared Key Value Store to a consistent state. 
+When the Provider, Requestor and chip-tool are run on the same Linux node the
+user must issue `rm -r /tmp/chip_*` before starting the Provider and
+`rm /tmp/chip_kvs` before starting the Requestor. These commands reset the
+shared Key Value Store to a consistent state.
 
 ## Example
 
 Building:
+
 ```
 scripts/examples/gn_build_example.sh examples/chip-tool out/ chip_config_network_layer_ble=false && scripts/examples/gn_build_example.sh examples/ota-provider-app/linux out/debug chip_config_network_layer_ble=false  && scripts/examples/gn_build_example.sh examples/ota-requestor-app/linux out/debug chip_config_network_layer_ble=false
 ```
 
 Running (in separate terminals as described above):
+
 ```
 rm -r /tmp/chip_*
 ./out/debug/chip-ota-provider-app -f /tmp/ota.txt
@@ -82,6 +87,7 @@ rm /tmp/chip_kvs
 ./out/chip-tool pairing onnetwork-long 2 20202021 42
 ./out/chip-tool otasoftwareupdaterequestor announce-ota-provider 1 0 0 0 2 0
 ```
+
 ## Current Features / Limitations
 
 ### Features