document errors

 
 


__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/

The following are grammatical and spelling
errors that I've found in some of the
documents in the libwww CVS repository. 

The words "in diff" mean that the changes
have already been made by me and are in
the context diff that I'll post in another
message. 

Document: libwww/Library/User/Start.html
Problem: The Robot profile initializes a large set
  of features often used in client applications. 
Words: in client applications
Change: in robot applications


Document: libwww/src/HTProfil.html
Problem: hence only one reques can be performed
Word: reques
Change: request


Document: libwww/src/HTProfil.html
Problem: superseeds the termination function for teh 
  Library core
Word: teh
Change: the


Document: libwww/Library/src/HTLib.html
Problem: These two functions initiates memory and settings
Word: initiates
Change: initialize


Document: libwww/Library/src/HTLib.html
Problem: is not desired and we can therefore turn it off
Word: and
Change: , and
 (place a comma before the `and' to separate the clauses)


Document: libwww/Library/src/HTReq.html
Problem: It should be use with care as application
Word: use
Change: used
  (in diff)

Document: libwww/Library/src/HTReq.html
Problem: client version but libwww can in fact also deal
Word: but
Change: , but
   (place a comma before `but')
Words: in fact
Change: , in fact,
   (set off `in fact' with commas)
e.g.: client version, but libwww can, in fact, also deal
   (in diff)


Document: libwww/Library/src/HTReq.html
Problem: If the anchor that we have requested
  is infact a child anchor then we always load
  the parent anchor and then after the load 
  jump to the location.
Change: If the anchor that we have requested
  is, in fact, a child anchor, then we always
  load the parent anchor first; after the load,
  we jump to the location. 

  [The first version was a run-on sentence.
  "Infact" is not a word.]
  (in diff)


Document: libwww/Library/src/HTReq.html
Problem: Errors are like almost anything kept in
  lists and a error list can be associated with
  a request using the following functions. 
Change: Errors are, like almost anything, kept in
  lists, and an error list can be associated with
  a request using the following functions. 

  [`Like almost anything' should be set off with commas.
  A comma should appear befor `and.'
  `A error' is incorrect; use `an error.']
  (in diff)


Document: libwww/Library/src/HTReq.html
Problem: In order to avoid the Library going
  into an infinite loop, 
Word: Library
Change: Library's
  (in diff)


Document: libwww/Library/src/HTReq.html
Problem: preemptive (blocking I/O) or non-premitve
  (non-blocking I/O)
Word: premitve
Change: preemptive
  (in diff)


Document: libwww/Library/src/HTReq.html
Problem: For example when loading the first 
  document (the home page) then blocking can
  be used instead of non-blocking. 
Changes: For example, when loading the first
  document (the home page), blocking mode
  can be used instead of non-blocking. 
  (in diff)


Document: libwww/Library/src/HTReq.html
Problem: A access scheme is defined with
Word: A
Change: An
  (in diff)


Document: libwww/Library/src/HTReq.html
Problem: That it, it can add any header
   it likes. 
Words: That it
Change: That is
  (in diff)


Document: libwww/Library/src/HTReq.html
Problem: The mempory buffer is considered
Word: mempory
Change: memory
  (in diff)


Document: libwww/Library/User/Guide/Overview.html
Problem: Persistent Cacing Packages
Word: Cacing
Change: Caching


Document: libwww/Library/BeforeCommitting.html
Problem: Other peopel must be
Word: peopel
Change: people