Apply suggestions from code review

Co-authored-by: Andrew Scheller <lurch@durge.org>
Co-authored-by: will-v-pi <108662275+will-v-pi@users.noreply.github.com>

Author: will-v-pi

universal/README.md

@@ -11,8 +11,8 @@ for the purposes of these examples:
 allowing RP2040 and RP2350 (Arm & RISC-V) to run from identical flash contents.
 - A **Universal UF2** is multiple individual `.uf2` files with different family IDs
 concatenated together to create a single `.uf2` file. When dragged & dropped onto a device, 
-only the file with a family ID corresponding to that device will be loaded onto it, and the
-rest of the files will be ignored.
+only the portion of the file with a family ID corresponding to that device will be processed, and the
+rest of the file will be ignored.
 
 A **Universal Binary** can be packaged into a UF2 file for loading onto a device. However,
 as there isn't a common family ID between RP2040 and RP2350, you would have to package it into a **Universal UF2** with two copies (using `rp2040` and `absolute` family IDs), thus creating a **Universal UF2** of a **Universal Binary**.
@@ -29,7 +29,7 @@ Universal binaries must be recognised by both the RP2040 and RP2350 bootroms. Th
   - In addition to the RP2350 `IMAGE_DEF` item, this embedded block contains a
   `ROLLING_WINDOW_DELTA` item to translate this binary to the start of flash for execution
 - RP2350 RISC-V binary containing an embedded block
-  - Same as the Arm one
+  - Ditto
 
 All of the embedded blocks are linked into one big block loop.
 
@@ -38,18 +38,18 @@ These are then booted by the respective bootroms:
 RP2040 has no support for embedded blocks.
 - **RP2350** - sees the block loop and parses it to find the correct embedded block to boot
 from (Arm vs RISC-V). It then translates the flash address according to the
-`ROLLING_WINDOW_DELTA` so that the binary containing that embedded block is at the start of the
+`ROLLING_WINDOW_DELTA` so that the binary containing that embedded block appears at the start of the
 flash address space, and executes from there.
 
-For no_flash binaries the RP2040 boot2 is omitted as the bootrom just executes from the start
+For no_flash binaries the RP2040 boot2 is omitted as the RP2040 bootrom just executes from the start
 of SRAM, and instead of `ROLLING_WINDOW_DELTA` items the RP2350 binaries use `LOAD_MAP` items,
 to copy the code in SRAM to the correct location for execution rather than using address
 translation.
 
 ## How you should use them
 
-For most use cases, **Universal UF2s** are the best option to use. They will only load into
-flash the code that runs on that device. The [blink_universal](blink_universal) example uses a
+For most use cases, **Universal UF2s** are the best option to use. They will only load the
+code that runs on that device into flash. The [blink_universal](blink_universal) example uses a
 Universal UF2 for that reason, as the Wi-Fi firmware is quite large. **Universal Binaries**
 are only currently useful when the commonality of having a single `.bin` file for programming
 outweighs the disadvantage of the extra flash usage.

universal/blink_universal/blink_universal.c

@@ -13,8 +13,8 @@
 #endif
 
 enum BOARD_TYPE {
-    BOARD_TYPE_PICO,
-    BOARD_TYPE_PICO_W,
+    BOARD_TYPE_PICO,    // Pico-series board
+    BOARD_TYPE_PICO_W,  // Pico W-series board
     BOARD_TYPE_UNKNOWN,
 };