Updated license, version string, and project URLs. Also cleaned up whitespace.

Versioning now uses the format major.minor.revision, with revision
being the date of the edit in YYYMMDD format. Current version is
1.1.20111123

Author: pipwerks

readme.txt

@@ -1,27 +1,25 @@
-SCORM API wrappers
+pipwerks SCORM Wrapper for JavaScript     (v1.1.20111123)
+pipwerks SCORM Wrapper for ActionScript 2 (v1.1.20111123)
+pipwerks SCORM Wrapper for ActionScript 3 (v1.1.20111123)
 
-Copyright (c) 2008 Philip Hutchison
-MIT-style license. Full license text can be found at 
-http://www.opensource.org/licenses/mit-license.php
+Created by Philip Hutchison, January 2008
+https://github.com/pipwerks/scorm-api-wrapper
+
+Copyright (c) Philip Hutchison
+MIT-style license: http://pipwerks.mit-license.org/
 
 Inspired by APIWrapper.js, which was a demo file created by the ADL and Concurrent Technologies Corporation.
 
 The SCORM.API.find() and SCORM.API.get() functions are based on ADL code, which was modified by Mike Rustici (http://www.scorm.com), then further modified by Philip Hutchison.
 
-WARNING: Use at your own risk! This class is provided as-is with no implied warranties or guarantees.
-
-----------
+WARNING: Use at your own risk! These files are provided as-is with no implied warranties or guarantees.
 
-Some background: 
+##Background 
 
 These wrappers are intended to make your life easier so you don't need to be a SCORM expert to add SCORM support to your e-learning course.
 
 The SCORM API wrappers are an abstraction layer that makes adding SCORM code to your course a much simpler, less confusing task. They provide simple logic and error-checking for your course's SCORM code, and include some auto-handling, such as setting cmi.exit (aka cmi.core.exit) when exiting a course.
 
-These wrappers have gone largely unedited since 2008. I'm hoping that placing them on GitHub will spur myself and others to make improvements.
-
-----------
-
 The SCORM API Wrappers come in three varieties:
 
 * JavaScript
@@ -32,5 +30,4 @@ All three wrappers are SCORM version-agnostic, and will work with both SCORM 1.2
 
 Both of the ActionScript wrappers require the JavaScript wrapper; the AS wrappers use ExternalInterface to invoke functions contained in the JavaScript wrapper. If the JS wrapper is not present, the ActionScript wrappers will not work.
 
-When testing locally, the ActionScript wrappers also require you to change your Flash Player settings to allow local SWFs to execute ExternalInterface commands. Change your security settings using this link:
-http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager04.html
+The ActionScript wrappers use ExternalInterface to communicate with JavaScript. ExternalInterface will not work in a local environment unless you change your Flash Player security settings.