diff --git a/blog/2014/06/26/README.md b/blog/2014/06/26/README.md
index 55d9a198d..0bbfe3ff6 100644
--- a/blog/2014/06/26/README.md
+++ b/blog/2014/06/26/README.md
@@ -6,8 +6,7 @@ and "document manifests."
To that end, there's a new [/pubs/]() directory for old documents, and [/disks/pc/]() contains more disk images,
with more on the way. I have a TON of old diskette images, and it has taken more time to organize them and create
-manifests than I would like. I have managed to streamline the process somewhat, however, as discussed in
-[/disks/pc/personal/]().
+manifests than I would like.
*[@jeffpar](http://twitter.com/jeffpar)*
*June 26, 2014*
\ No newline at end of file
diff --git a/devices/pc/bios/5170/README.md b/devices/pc/bios/5170/README.md
index aff6b9646..687f2b546 100644
--- a/devices/pc/bios/5170/README.md
+++ b/devices/pc/bios/5170/README.md
@@ -21,10 +21,10 @@ The JSON-encoded ROM image that PCjs uses ([1984-01-10.json]()) was created usin
filedump --file=BIOS_5170_10JAN84_U27_6181028_27256_6MHZ.BIN --merge=BIOS_5170_10JAN84_U47_6181029_27256_6MHZ.BIN --output=1984-01-10.json
-Similarly, to create a binary ROM image ([1984-01-10.rom]()), add *--format=rom* to the command-line. These operations can
+Similarly, to create a binary ROM image (1984-01-10.rom), add *--format=rom* to the command-line. These operations can
only be performed using the *FileDump* command-line interface; the *FileDump* API does not support the *merge* option.
A MAP file [1984-01-10.map]() exists as well, which is automatically appended to the JSON file when using a ROM input
file (or JSON output file) with a matching filename. For example:
-> [http://www.pcjs:org/api/v1/dump/?file=/devices/pc/bios/5170/1984-01-10.rom](/api/v1/dump/?file=/devices/pc/bios/5170/1984-01-10.rom)
+ http://www.pcjs.org/api/v1/dump/?file=/devices/pc/bios/5170/1984-01-10.rom
diff --git a/docs/c1pjs/embed/README.md b/docs/c1pjs/embed/README.md
index 4fd671f23..19e4c4fa8 100644
--- a/docs/c1pjs/embed/README.md
+++ b/docs/c1pjs/embed/README.md
@@ -6,13 +6,13 @@ If you want to read as little as possible, then just paste the following code on
@@ -28,7 +28,7 @@ The order of the XML elements also determines the layout of the associated HTML
**<keyboard>** element appears before the **<video>** 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.12.1/components.xsl).
+there's no documentation beyond the sample XML files and the default [XML stylesheet](/versions/c1pjs/1.15.3/components.xsl).
The example at the top of this page uses an [XML file](/configs/c1p/machines/8kb/embed/machine.xml) that looks like:
@@ -62,7 +62,7 @@ The example at the top of this page uses an [XML file](/configs/c1p/machines/8kb
Machine configuration files can also be "self-starting" if they contain the following XML stylesheet reference at the
top of the file:
-
+
For example, here's a self-starting [machine.xml](/configs/c1p/machines/8kb/large/machine.xml) configuration.
After it loads, use your browser's "View Source" command and you'll see that it's very similar to the
@@ -107,10 +107,10 @@ Step 3: Add the C1Pjs Simulator to your web page
---
Somewhere on your page, you need to add the following **<script>** element:
-
+
-To include the C1Pjs Debugger, use [c1p-dbg.js](/versions/c1pjs/1.12.1/c1p-dbg.js) instead of
-[c1p.js](/versions/c1pjs/1.12.1/c1p.js), and include some additional definitions in your machine
+To include the C1Pjs Debugger, use [c1p-dbg.js](/versions/c1pjs/1.15.3/c1p-dbg.js) instead of
+[c1p.js](/versions/c1pjs/1.15.3/c1p.js), and include some additional definitions in your machine
definition XML file:
@@ -143,13 +143,13 @@ 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.12.1/components.xsl).
+parameter and use the default [XML stylesheet](/versions/c1pjs/1.15.3/components.xsl).
Step 5: Enjoy!
---
All I ask is that any page that embeds the simulator also includes the following attribution: a link to this
website ([pcjs.org](http://www.pcjs.org/)) and my contact info ([@jeffpar](http://twitter.com/jeffpar)).
-If you use the default [XML stylesheet](/versions/c1pjs/1.12.1/components.xsl), attribution is automatically inserted,
+If you use the default [XML stylesheet](/versions/c1pjs/1.15.3/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