Update README.md

README.md

@@ -96,8 +96,8 @@ You should have a better enviroment now with some drivers, and -fingers crossed-
 Due to the command line options, BOCHS will ignore .lock files remaining when BOCHS is killed, so it can start again the next time without lock errors.<br>  
 Note: you can leave it running, it will not impact on your device performance, plus, once you tap again on the FreeDOS icon the same istance will come back, without running a new one. I usually leave it open once rM starts, and use it throughout the day.
   <h2>Just to be clear</h2>
-I could simply upload the BOCHS c: drive image of my full system, and let you run it without any fuss on your reMarkable, but... no? I just can't spread copyrighted software. Anyway, you can of course backup the c.img file to restore it in case of an update or else, or just to put it into another rM of your own. To backup your setup, just use scp: <code>scp "root@your-remarkable-ip:/home/root/freedos-img/*" .</code> (don't forget the last dot).<br><br>
-<br><br>Other DOS software I managed to run on reMarkable:<br>
+I could simply upload the BOCHS c: drive image of my full system, and let you run it without any fuss on your reMarkable, but... no? I just can't spread copyrighted software. Anyway, you can of course backup the c.img file to restore it in case of an update or else, or just to put it into another rM of your own. To backup your setup, just use scp: <code>scp "root@your-remarkable-ip:/home/root/freedos-img/*" .</code> (don't forget the last dot).
+<h2>Other DOS software I managed to run on reMarkable:</h2>
 <li>Wordstar Professional 4:
 <br>https://www.dropbox.com/s/6evvrcgn3e6s5kw/ws1.jpg?dl=0
 <br>https://www.dropbox.com/s/i16kbc7x19qr9gw/ws2.jpg?dl=0