update READMEs

README.md

@@ -22,10 +22,6 @@ This open source server is in beta status. Use at your own risk.
 ### Current issues:
 - Mis-configuring wtv-disk:/sync DiskMaps may cause units to delete contents of partitions (need more info)
 
-### Won't fix:
-- wtv-encryption stream breaks when two different sessions have the same SSID (eg spoofing, won't fix (production did it too))
-- ~~No intentions to support user accounts, registration, or any form of database system~~ *(I guess this was a lie, but we still don't use a database!)*
-
 ### Feature Todo:
 - TellyScript generation and/or manipulation without external dependancies
 - ~~wtv-setup and bgm support~~ ***Done [v0.9.23](https://github.com/zefie/zefie_wtvp_minisrv/releases/tag/v0.9.23)***

README_bf0app_flashrom.txt

@@ -1,5 +1,12 @@
 The bf0app flashing system requires a two things that you must be aware of, that are different from a typical setup:
+
 1) Your PPP system MUST accept auth, a noauth setup will not work for the 2nd dialing phase
+
 2) You must have a clean dialup. DreamPi voltage-hacked lines, and unstable VoIP systems are known
    to cause errors, leaving the box in a 'braindead' state with no flash. MiniSrv can help recover
-   from this but you will need to provide a stable dialup connection. This was tested with my Cisco 3825 setup.
+   from this but you will need to provide a stable dialup connection. This was tested with my Cisco 3825 setup.
+   
+3) bf0app systems flash right away, as soon as a part is received and validated.
+   This means if your bf0app box fails mid-flash, you could design a custom page to send the flashrom
+   from where it left off (for example, if your box failed on part 3 of 16, you could start again at
+   part 3 (with a specially set up page, minisrv won't do this by default)