Fixed a few broken links

_posts/2014-04-12-whats-new-in-1.13.0.md

@@ -11,7 +11,7 @@ are simple XML files that describe a piece of software (an application, an opera
 link to a PCjs machine configuration capable of running the software, along with a "ready-to-run" machine state file.
 Conversely, a PCjs machine XML file can refer back to the manifest, to obtain a list of disk images.
 
-Here are some [Demos](/apps/pc/) of "ready-to-run" apps on [PCjs](/docs/about/). 
+Here are some [Demos](/apps/pcx86/) of "ready-to-run" apps on [PCjs](/docs/about/). 
 
 There have been lots of server-side changes recently, including API improvements that make it easy (well, *easier*)
 to dynamically create diskette images from a list of files, or even an entire folder (including all subfolders),

_posts/2015-06-01-debugging-the-ibm-vga-rom.md

@@ -135,7 +135,7 @@ modes commonly used on the IBM VGA.  Here's that table:
 	 ATC[0x12]: PLANES          0x0F 0x0F 0x0F 0x0F 0x03 0x03 0x01 0x0F 0x0F 0x0F 0x0F 0x0F
 	 ATC[0x13]: HPAN            0x08 0x08 0x08 0x08 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
 
-In addition, I've created a [VGA Tests](/tests/pc/vga/) directory to hold VGA test and sample code that PCjs can 
+In addition, I've created a [VGA Tests](/tests/pcx86/vga/) directory to hold VGA test and sample code that PCjs can 
 now successfully run (for the most part).  See that directory for more details.
 
 *[@jeffpar](http://twitter.com/jeffpar)*  

_posts/2017-07-09-magware.md

@@ -13,7 +13,7 @@ It turned out that that archive was a rabbit hole I could not *not* go down.
 
 First, I collected all the other PC Tech Journal ZIP archives there (from December 1985 through January 1989),
 recreated them as a set of [PC Tech Journal Disks](/disks/pcx86/shareware/pctj/), and added them to the
-[PCjs Disk Library](/disks/pcx86/), so now you can "Load" and "Save" them in any [PCjs Machine](devices/pcx86/machine/).
+[PCjs Disk Library](/disks/pcx86/), so now you can "Load" and "Save" them in any [PCjs Machine](/devices/pcx86/machine/).
 
 Next, since I was also a fan of PC Magazine back in the day, I decided to do the same for all the PC Magazine ZIP
 archives.  So now there's a set of [PC Magazine Disks](/disks/pcx86/shareware/pcmag/) you can play with as well.

_posts/2017-07-15-flicker-fakery.md

@@ -86,7 +86,7 @@ starts reading from the top of video memory after it reaches the bottom.  So all
 new lines at the top of the video memory again.  If IBM had thought of that trick 5 years earlier, back in 1981,
 think of all the years of shared flicker-grief that could have been avoided!
 
-Today, in honor of all that flickering, I'm pleased to announce that [PCx86](devices/pcx86/machine/), one of the
+Today, in honor of all that flickering, I'm pleased to announce that [PCx86](/devices/pcx86/machine/), one of the
 PCjs emulators I'm always trying to improve, now offers **FLICKERING** on all IBM PC Color Graphics configurations.
 If you feel the need to override it, you can add *flicker=0* to the URL of your favorite machine; e.g.:
 

api/v1/dump/README.md

@@ -15,11 +15,11 @@ scripts: # the following list of scripts should mirror what /modules/diskdump/li
 ---
 
 PCjs DiskDump and FileDump API
-===
+------------------------------
 
-The PCjs [DiskDump](/modules/diskdump/) and [FileDump](/modules/filedump/) API are not fully supported
+The PCjs [DiskDump](/modules/diskdump/) and [FileDump](/modules/filedump/) API are not fully supported by the
-by the current PCjs web server.  When [pcjs.org](http://www.pcjs.org/) switched from a Node-based web server running on
+current PCjs web server.  When [pcjs.org](http://www.pcjs.org/) switched from a Node-based web server running
-[Amazon Web Services](https://aws.amazon.com/elasticbeanstalk/) to [GitHub Pages](https://pages.github.com/),
+on [Amazon Web Services](https://aws.amazon.com/elasticbeanstalk/) to [GitHub Pages](https://pages.github.com/),
 the original server-side API had to be abandoned.
 
 However, we're working on a client-side replacement of the API that will run

devices/pdp10/README.md

@@ -11,4 +11,4 @@ PDP-10 Device Configurations
  
 * [Control Panels](panel/)
 
-Test machines include a [PDP-10 (Model KA10) with Debugger](/devices/pdp11/machine/ka10/panel/debugger/).
+Test machines include a [PDP-10 (Model KA10) with Debugger](/devices/pdp10/machine/ka10/test/debugger/).

disks/README.md

@@ -9,17 +9,20 @@ permalink: /disks/
 Disk Libraries
 --------------
 
-Browse these PCjs Disk Libraries:
+Browse the following PCjs Disk Libraries.
 
-* [IBM PC](pcx86/)
+### [IBM PC](pcx86/)
-* [Challenger 1P](c1p/)
+
-* [DEC](dec/)
+### [Challenger 1P](c1p/)
+
+### [DEC](dec/)
 
 Additional software is available in the [Application Archives](/apps/).
 
 ---
 
-### PCx86 Disk Image Formats
+PCx86 Disk Image Formats
+------------------------
 
 PCx86 works best with disk images in a **JSON** format, so that's the only disk format you'll
 find in the [PCjs Project](https://github.com/jeffpar/pcjs).
@@ -27,7 +30,8 @@ find in the [PCjs Project](https://github.com/jeffpar/pcjs).
 There are several ways you can convert a PCjs **JSON** disk image back into a binary **IMG** file:
 
 - Load the disk into a PCjs machine and click the **Save** button
-- Use the [DiskDump API](/api/v1/dump) (available only in the [PCjs Node Web Server](/server.js))
+- Use the [DiskDump API](/api/v1/dump) (available only with the
+[PCjs Node Web Server](https://github.com/jeffpar/pcjs/blob/master/server.js))
 
 Note that whenever you **Save** a disk inside a PCjs machine, it is saved exactly as it exists
 at that point in time.  So, if you made any changes to the disk, those changes will be preserved
@@ -38,7 +42,8 @@ For example:
 
 	{{ site.url }}/api/v1/dump?disk=/disks/pcx86/dos/ibm/2.00/PCDOS200-DISK1.json&format=img
 
-The [PCjs Node Web Server](/server.js) also generates "onclick" handlers for links to **JSON** disk
+The [HTMLOut Component](https://github.com/jeffpar/pcjs/blob/master/modules/htmlout/lib/htmlout.js)
+of the PCjs Node Web Server also generates "onclick" handlers for links to **JSON** disk
 images that automatically invoke the API for you.
 
 See [Creating PCx86-Compatible Disk Images](/docs/pcx86/#creating-pcx86-compatible-disk-images)

modules/diskdump/README.md

@@ -5,13 +5,13 @@ permalink: /modules/diskdump/
 ---
 
 DiskDump Module
-===
+---------------
 
-**DiskDump** is a Node module with both a command-line interface and a web server API for converting disk images
+DiskDump is a Node [module](lib/diskdump.js) with both a command-line [utility](bin/diskdump) and a web server API
-to/from various formats (eg, JSON files, JSON files with comments, IMG disk images, etc). 
+for converting disk images to/from various formats (eg, JSON files, JSON files with comments, IMG disk images, etc). 
+
+### Building Disk Images from Folders/Files
 
-Building Disk Images from Folders/Files
----
 In addition to converting disk images to/from JSON, DiskDump can also create disk images from the contents of local
 files/folders.
 
@@ -28,7 +28,8 @@ into that folder as well, so that you could then run:
 	node modules/diskdump/bin/diskdump --path="apps/pcx86/1981/visicalc/vc.com;README.md" --format=img --output=disk.img
 
 to produce a `disk.img` containing both "VC.COM" and "README.md".  In fact, this is exactly how the
-[disk.json](/apps/pcx86/1981/visicalc/disk.json) stored in the [VisiCalc](/apps/pcx86/1981/visicalc/) folder was generated.
+[VisiCalc Disk](/apps/pcx86/1981/visicalc/VISICALC1981.json) stored in the [VisiCalc](/apps/pcx86/1981/visicalc/)
+folder was generated.
 
 The equivalent web server API request would look like:
 

modules/filedump/README.md

@@ -5,6 +5,7 @@ permalink: /modules/filedump/
 ---
 
 FileDump Module
-===
+---------------
 
-This module (and command-line utility) is used to convert the contents of binary files to JSON.
+FileDump is a Node [module](lib/filedump.js) with both a command-line [utility](bin/filedump) and a web server API
+for converting the contents of binary files to JSON.

pubs/docs/c1pjs/embed/README.md

@@ -21,13 +21,13 @@ If you want to read as little as possible, then just paste the following code on
 ```html
 <div id="myC1P"/></div><div style="clear:both"></div>
 <script type="text/javascript"
-    src="http://www.pcjs.org/versions/c1pjs/1.34.0/c1p.js">
+    src="http://www.pcjs.org/versions/c1pjs/1.37.0/c1p.js">
 </script>
 <script type="text/javascript">
     window.embedC1P(
         "myC1P",
         "http://www.pcjs.org/devices/c1p/machine/8kb/embed/machine.xml",
-        "http://www.pcjs.org/versions/c1pjs/1.34.0/components.xsl"
+        "http://www.pcjs.org/versions/c1pjs/1.37.0/components.xsl"
     );
 </script>
 ```
@@ -45,7 +45,7 @@ The order of the XML elements also determines the layout of the associated HTML
 **&lt;keyboard&gt;** element appears before the **&lt;video&gt;** element, then the keyboard controls will be
 displayed *above* the video display instead of *below*. There's an extensive set of attributes that you can add
 to any of the elements below to style and position them, including the usual *style* attribute, but at present,
-there's no documentation beyond the sample XML files and the default [XML stylesheet](/versions/c1pjs/1.34.0/components.xsl).
+there's no documentation beyond the sample XML files and the default [XML stylesheet](/versions/c1pjs/1.37.0/components.xsl).
 
 The example at the top of this page uses an [XML file](/devices/c1p/machine/8kb/embed/machine.xml) that looks like:
 
@@ -82,7 +82,7 @@ Machine configuration files can also be "self-starting" if they contain the foll
 top of the file:
 
 ```xml
-<?xml-stylesheet type="text/xsl" href="http://www.pcjs.org/versions/c1pjs/1.34.0/machine.xsl"?>
+<?xml-stylesheet type="text/xsl" href="http://www.pcjs.org/versions/c1pjs/1.37.0/machine.xsl"?>
 ```
 
 For example, here's a self-starting [machine.xml](/devices/c1p/machine/8kb/large/machine.xml) configuration.
@@ -133,11 +133,11 @@ Step 3: Add the C1Pjs Simulator to your web page
 Somewhere on your page, you need to add the following **&lt;script&gt;** element:
 
 ```html
-<script type="text/javascript" src="http://www.pcjs.org/versions/c1pjs/1.34.0/c1p.js"></script>
+<script type="text/javascript" src="http://www.pcjs.org/versions/c1pjs/1.37.0/c1p.js"></script>
 ```
 
-To include the C1Pjs Debugger, use [c1p-dbg.js](/versions/c1pjs/1.34.0/c1p-dbg.js) instead of
+To include the C1Pjs Debugger, use [c1p-dbg.js](/versions/c1pjs/1.37.0/c1p-dbg.js) instead of
-[c1p.js](/versions/c1pjs/1.34.0/c1p.js), and include some additional definitions in your machine
+[c1p.js](/versions/c1pjs/1.37.0/c1p.js), and include some additional definitions in your machine
 definition XML file:
 
 ```xml
@@ -175,7 +175,7 @@ The **embedC1P()** function accepts three parameters:
 - the *id* attribute of the HTML element that will contain the simulator (eg, 'myC1P');
 - the URL of your machine definition XML file (eg, 'embed.xml', since it's on the same server);
 - the URL of an XML stylesheet; unless you've created your own stylesheet, it's recommended you omit this
-parameter and use the default [XML stylesheet](/versions/c1pjs/1.34.0/components.xsl).
+parameter and use the default [XML stylesheet](/versions/c1pjs/1.37.0/components.xsl).
 
 Step 5: Enjoy!
 --------------
@@ -184,7 +184,7 @@ All I ask is that any page that embeds the simulator also includes attribution,
 
 > [PCjs](http://pcjs.org) © 2012-2017 by [Jeff Parsons](mailto:Jeff@pcjs.org) ([@jeffpar](http://twitter.com/jeffpar))
 
-If you use the default [XML stylesheet](/versions/c1pjs/1.34.0/components.xsl), attribution is automatically inserted,
+If you use the default [XML stylesheet](/versions/c1pjs/1.37.0/components.xsl), attribution is automatically inserted,
 which relieves you from including it yourself.
 
 Feel free to copy any or all of the files listed above to your own server (it's probably better to share the server