Updated all machine 'video' elements to use new 'menu' element ('name' element is now deprecated)

blog/2014/10/17/README.md

@@ -8,24 +8,28 @@ v1.15.5 of PCjs now, which includes the following fixes:
 of the refresh bit in port 0x61 to bit 6 of the CPU cycle count (see *in8042RWReg()* in [chipset.js](/modules/pcjs/lib/chipset.js));
 the original AT BIOS was satisfied with a refresh bit that merely alternated, whereas the new AT BIOS
 is much more particular about the rate at which that bit changes, since many hard-coded delay-loops have
-now been replaced with code that waits for a specific number of refresh cycles. 
+now been replaced with code that waits for a specific number of refresh cycles.
+
 + The 8042 Keyboard Controller emulation needed a few more tweaks, mainly with respect to what happens
 when the keyboard's "clock" line is toggled (see *set8042CmdData()* in [chipset.js](/modules/pcjs/lib/chipset.js)).
+
 + The Floppy Disk Controller needed to add support for the "READ ID" command, in order for the BIOS
 "double-stepping" test to work (double-stepping is required on an 80-track drive when attempting to read
 a 40-track diskette).
+
 + The BIOS Diskette Reset function does something odd after resetting the Floppy Disk Controller: it
 issues not one but *four* "SENSE INTERRUPT STATUS" commands to the FDC, and expects each response to
 return an incrementally larger drive number.  I found this a bit mystifying, considering that IBM's
-own FDC/HDC "combo card" supports a maximum of *two* diskette drives.  But, there's no point in arguing
+own FDC/HDC "combo card" supports a maximum of *two* diskette drives.  But, there's no point arguing
 with a BIOS that's almost 30 years old.
-+ The BIOS attempts to detect what its authors must have considered a common problem: failure to run SETUP
-after installing a second hard drive.  So, when the CMOS reports only one hard drive installed, the BIOS
-probes for a second hard drive anyway, and it does so by simply writing the drive number to the ATC's "DRVHD"
-register and then immediately reading the "STATUS" register, without issuing any intervening command.
+
++ The BIOS attempts to detect what its authors must have considered a common problem: the user's failure
+to run SETUP after installing a second hard drive.  So, when the CMOS reports only one hard drive installed,
+the BIOS probes for a second hard drive anyway, and it does so by simply writing the drive number to the ATC's
+"DRVHD" register and then immediately reading the "STATUS" register, without issuing any intervening command.
 It was an easy fix to *outATCDrvHd()* in [hdc.js](/modules/pcjs/lib/hdc.js), but I was surprised
-to discover that the ATC had this behavior, and now I'm wondering how many other I/O operations require
-immediate "STATUS" register updates.
+to discover that the ATC had this behavior, and now I'm wondering if there are any other I/O operations
+that must immediately update the "STATUS" register.
 
 This PCjs release also fixes a problem reported by a user: if you disable **localStorage** support in your
 browser, previous versions of PCjs would fault.  While every browser that supports PCjs also supports
@@ -41,7 +45,7 @@ and a little annoying, because **localStorage** is *not* a **cookie**.
 
 PCjs *never* sets any cookies.  Cookies are bits of data that your browser saves and then automatically sends
 off to the server every time you make a request.  **localStorage** is nothing more than local storage; it is
-*not* automatically sent anywhere.  Granted, a JavaScript application could abuse it and send it around like a
+*not* automatically sent anywhere.  Granted, a JavaScript application could abuse it and send it out just like a
 cookie, but PCjs does *not* do that; the only exception is when PCjs detects a problem, and even then, you must
 first agree to submit your machine's state as part of the bug report.