anchor.diff:  of mesh networks actually using the DFU. You might still want to go with something more clever than
   0x12345678 though, someone else might have been just as lazy.
   
  -== 3. Generate a hex version of your device-page with the tool in /nRF51/bootloader/pc-util.
  +== 4. Generate a hex version of your device-page with the tool in /nRF51/bootloader/pc-util.
   In the same folder as the example device page file, there's a main.c file that you can compile
   to create the device page generator. See its respective README for instructions. Once you have
   a working generator, generate an example device page file:
  
positive.code: Note that only some of them apply to mesh-DFU, as the tool still supports the regular
  Nordic Semiconductor DFU transfer.
  
  == 11. Transfer the DFU-file over serial with the pc-nrfutil tool.
  
  WARNING: For this step, it is important that you close any running instance of nRFgo Studio,
  as it has been known to trip up the reset procedure for the nRF51.
  
negative.code: The bootloader verification script does not alter your setup in any way, and you may safely continue
  without it. It serves as a checkpoint and help utility in the process.
  
  == 11. Generate a DFU-file with the pc-nrfutil tool, giving arguments that match the device-page.
  To do a DFU, you need to create a DFU-file. The DFU file is really
  a .zip, which contains the application binary, along with some metadata. Matching the FWIDs in
  your device page file, call the nrfutil tool from /nRF51/bootloader/:
  