A semicolon has been added after the gotoAndStop ("init") statement.
The code now reads:

on (release) {
gotoAndStop ("init");
}

The comment used to read:

// Sets the finalGreeting to "Hello, Karsten?"

It has been changed to read:

// Sets the finalGreeting to "Hello Karsten?"

In the example code, the word "Pain" has been changed to start with a lowercase "p" rather than a capital "P". The code now reads:

paradox = "pain is pleasure, pleasure is pain";

In the code sample that calculates the volume of a cylinder, the variable
"circleArea" is defined on line 3, but the variable "area" was subsequently
used on line 4. line 4's variable "area" was changed to "circleArea",
so it reads:

var cylinderVolume = circleArea * height;

In the code sample that checks for a zero divisor, line 3 is missing curly braces
around the else statement. Line 3 should read:
} else {

In the second code sample on the page, the diameter variable is incorrectly set to
ball.radius instead of ball.radius * 2. Line 1 of the code should read:
diameter = ball.radius * 2;

In the second code sample on the page, the value of Math.PI is missing a "1". Line 3
of the code should read:
trace("pi is: " + PI); // Displays: 3.14159... (PI is a property of Math)

The second-last sentence used to read:

"by invoking our generic movieClip() function"

It has been changed to read:

"by invoking our generic moveClip() function"

In the makeClip function example, the code used to read:

theClip.duplicateMovieClip(the clip._name...)

It has been changed to read:

theClip.duplicateMovieClip(theClip._name...)

"Unlike the keyPress button event, keyDownclip events occur when any
key--not just a specific key--is pressed."

has been changed to:

"Unlike the keyPress button event, keyDown clip events occur when any
key--not just the specific key--is pressed."

The words "keyPress" and "keyDown" are italicized. The word "clip"
is not italicized.

The sentence used to read: "Like the letters in the alphabet or the amino acid
sequences in a strand of DNA..."

It now reads: "Like the letters in the alphabet or the sequence of
base-pairs in a strand of DNA..."

The MIME type in the tip text (marked by an owl graphic), is incorrectly listed as:
"application/x-www-urlform-encoded". The correct MIME type is: "application/x-www-
form-urlencoded" (as specified by the W3C). This error also appears under
loadVariables() (p.489), XML.contentType() (p.610), and XML.send() (p.626).

"exec", "C:/WINDOWS/NOTEPAD.EXE")

has been changed to:

fscommand("exec", "C:/WINDOWS/NOTEPAD.EXE");

In the example for #include showing syntax differences between Macintosh
and Windows file paths, the example for Macintosh used a slash character
("/") to delimit folders:
#include "Mac HD/Desktop folder/working/myScript.as"

It was changed so that a colon (":") is used instead. It now reads:
#include "Mac HD:Desktop folder:working:myScript.as"

When passed a below-range frame number, the MovieClip.gotoAndPlay() method actually
behaves differently than the global gotoAndPlay() function. The second line of the
frameNumber argument for MovieClip.gotoAndPlay() should, hence, be replaced with:
"If frameNumber is less than 1, the call to MovieClip.gotoAndPlay() is ignored. If
frameNumber is greater than the number of frames in mc's timeline, the playhead is
sent to the last frame. Note that this behavior differs from the global version of
gotoAndPlay(), where a value less than 1 is treated as 1."

When passed a below-range frame number, the MovieClip.gotoAndStop() method actually
behaves differently than the global gotoAndStop() function. The second line of the
frameNumber argument for MovieClip.gotoAndStop() should, hence, be replaced with:

"If frameNumber is less than 1, the call to MovieClip.gotoAndStop() is ignored. If
frameNumber is greater than the number of frames in mc's timeline, the playhead is
sent to the last frame. Note that this behavior differs from the global version of
gotoAndStop(), where a value less than 1 is treated as 1."