[Kernelbook-feedback] Comments on the PDF preivew release

[Matthew C. <ma...@ni...>]

On page 6 of chapter 6 (in the PDF format), it says "Bug reports are cruc=
ial=20
Linux developers"; that should probably be "are crucial _to_ Linux=20
developers".

On chapter 1, page 2 (PDF), I think it should be "hybrids begot" rather t=
han=20
"hybrids begot".

On page 3, there's "Unix was rapt with license wars an infighting".  Unle=
ss=20
you mean to say that the Unix world was deeply concerned with these thing=
s, I=20
think that you should use another word, like maybe "reft", though that's =
a=20
bit archaic.  Also on page 3, "one reason ... chose to implement Unix in =
a=20
high level language to achieve a level of abstraction...", I think that=20
should be "was to achieve" or "was in order to achieve".

The header "Planned features for Linux 2.5" is on page 9, while the conte=
nts=20
are on page 10; a header should always be followed by at least one paragr=
aph=20
of whatever it heads.

Since I haven't looked at the full RTF version of the book, I don't know =
how=20
you do the bibliography (or if there is one yet), but I think it might be=
 a=20
good idea to put a little bibliography (especially URLS) at the end of ea=
ch=20
chapter.

Finally, I like the sense of humor displayed in the first two paragraphs =
of=20
the first chapter; technical documentation with wit is a good thing, in m=
y=20
opinion. ;-)

--=20
Matthew Cline        | Suppose you were an idiot.  And suppose that
ma...@ni... | you were a member of Congress.  But I repeat
                     | myself.  -- Mark Twain