Updated readme files

CHANGES.txt

@@ -13,10 +13,11 @@ For future versions...
     TODO: Support for authenticated task termination
     TODO: Add support for feeding script output into status item view like Tapir did (cool feature)
     TODO: Refactor status menu item menu generation from output to share code between ScriptExec and Platypus.app
+    TODO: Move documentation to Markdown format instead of raw, old-school HTML
+    TODO: Don't save Status Menu image as base64 in every Profile
 
     http://stackoverflow.com/questions/13355363/nstask-requires-flush-when-reading-from-a-process-stdout-terminal-does-not
     http://stackoverflow.com/questions/1276029/non-blocking-stdio
-    TODO: Move documentation to Markdown format instead of raw, old-school HTML
 
 
 5.2
@@ -28,10 +29,10 @@ For future versions...
     * Platypus apps can now accept dragged URLs
     * Platypus apps that accept dropped files now have an Open Recent menu
     * New syntax to create submenus in Status Menu interface type
+    * Relative paths are now supported in Platypus Profiles, but only through manual editing. Platypus app and CLT still generate Profiles with absolute paths.
     * Platypus now warns about about identical file names in bundled files
     * Text in Platypus apps now has a minimum font size
     * The Platypus Profile format has changed slightly in this version, but old formats can still be read
-    * Relative paths are now supported in Platypus Profiles, but only through manual editing. Platypus app and CLT still generate Profiles with absolute paths.
     * Droplet apps now quit when their window is closed
     * Updated and improved example profiles
     * Fixed annoying issue where status menu would render before receiving all script output

Documentation/Readme.html

@@ -88,7 +88,7 @@ <h3>How do I use Platypus?</h3>
 
 <p>Using Platypus is simple enough.  You type in a name for the application in the <strong>App Name</strong> field and then locate your script via a navigation dialog by pressing the <strong>Select</strong> button (or alternatively, drag the script or type in the path manually).  You can then create an  application by pressing the <strong>Create</strong> button.</p>
 
-<p>Platypus has a number of features that are explained in detail in the <a href="http://sveinbjorn.org/files/software/platypus/documentation/Documentation.html">documentation</a>.  If you are offline, you can view documentation by opening Platypus and selecting <strong>Platypus Documentation</strong> from the <strong>Help</strong> menu.  The documentation is quite detailed and includes step by step tutorials, examples, an FAQ section, and in-depth explanations of advanced features.</p>
+<p>Platypus has a number of features that are explained in detail in the <a href="http://sveinbjorn.org/files/software/platypus/documentation/Documentation.html">documentation</a>.  If you are offline, you can view documentation by opening Platypus and selecting <strong>Platypus Documentation</strong> from the <strong>Help</strong> menu.  The documentation is quite detailed and includes step by step tutorials, examples, an FAQ section, and explanation of advanced features.</p>
 
 <p>Platypus has a command-line interface counterpart, <code>platypus</code>, which can be installed from the <strong>Preferences</strong> into <code>/usr/local/bin/platypus</code>.  The man page for the command line tool is available both from the terminal and as an HTML document accessible from the Help menu.</p>
 

README.md

@@ -14,6 +14,8 @@ applications can be created with a few clicks. It is very easy to
 create installers, administrative applications, login items, status menu items, 
 launchers, automations and droplets using Platypus.
 
+* [Download Platypus 5.1](http://sveinbjorn.org/files/software/platypus/platypus5.1.zip) (Intel 64-bit, 10.7 or later, ~3.7 MB)
+
 ## Documentation
 
 * [Platypus Documentation](http://sveinbjorn.org/platypus_documentation)