Errata

"...-n and phonelist are arguments..."
should read:
"...-n is an option, phonelist is an argument..."

I'm no expert so I hope I'm not wasting your time....

The commands cd book/wonderland and cd ~/book/wonderland do not appear to
be valid for you example. I.e. in figure 1-2 (that the commands refer to)
wonderland is a file not a directory.

In Fig 4-1, the scripts source alice in example b, and c should, according to the text on page 82, be only alice, without the word 'source'

The text says that if you define the function:

function alice
{
echo "alice: $*"
echo "$0: $1 $2 $3 $4"
echo "$# arguments"
}

in .bash_profile you will get the same output as if you defined it in a shell script.
However, this is not true. When you type "alice in wonderland" the 2nd echo statement
produces: "/bin/bash: in wonderland" whereas when you run the corresponding shell
script you get "alice: in wonderland"

The bash construct ${variable##*/} is not quite equivalent to the unix utility
basename.

Example using basename
computer% cd / && basename $PWD
/
computer%

Example ${variable##*/}
computer% cd / && echo ${PWD##*/}

computer%

the "highest" script: The elif branch has the statement

print 'usage: highest [-N] filename'

which should read

echo 'usage: highest [-N] filename'

The script, as written hangs if it is invoked without any arguments, at all (i.e.
highest), because we wind up calling sort without any arguments, so it waits for
input from stdin. This is easily corrected by modifying the elif to:
elif [ -n "echo $1 | grep '^-' ] || [ -z $1 ]; then

I am using a copy with print date 2/01.
I am in the "Options with Arguments" section.

The tests for the while loop performs correctly if the arguments start with
a dash. Suppose that one argument contains a dash elsewhere, like a family
name, then the call to grep '-' succeeds, which is not the intention.

The correction is simple: add a caret to force the discovery of dash as the
first character in the string (grep '^-').

In the preceding pages discussing about argument detection, the caret appears.

The example has a typo in the variable name val1.

$ result1=val*val2
should read:
$ result1=val1*val2

The ! operator is described as being a Bitwise not. In fact, I believe it operates as a *logical* not
operator.

Demonstration: GNU bash, version 2.05.0(8)-release (i686-pc-cygwin):
$ echo $(( ! 1 ))
(displays 0)

$ echo $(( ! 100 ))
(displays 0)

$ echo $(( ! 0 ))
(displays 1)

As in C, the ! (bang) is a Boolean or Logical not, and should be listed below && and ||
as such, instead of in table 6-2 Arithmetic Operators.

The book shows

$ ls -l $(type -path vi)
++ type -path vi
+ ls -F -l /usr/bin/vi

Where did the "-F" come from? This should not appear.

The appendix table does not quite match Table 7-1. There are discrepencies
on lines 7 (n : even if noclobber set) and 13 (>> file : Direct file
descriptor n to file; append to file if it already exists).

The word "list" should have appeared as "<list>" in this line

The index entry for ! (bang) says:

bitwise not operator, 152

it should say:

logical not operator, 153