W3C home > Mailing lists > Public > www-lib@w3.org > July to September 2000

document errors 1

From: Fox One <rockman66_1999@yahoo.com>
Date: Tue, 4 Jul 2000 15:12:25 -0700 (PDT)
Message-ID: <20000704221225.2714.qmail@web4306.mail.yahoo.com>
To: www-lib@w3.org
Attached is a list of grammatical
and spelling errors in the libwww cvs

I thought that I had posted this before, 
but the message seems to have been lost. 

Do You Yahoo!?
Kick off your party with Yahoo! Invites.

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
Word: superseeds
Change: supersedes

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

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

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.]

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 before `and.'
  `A error' is incorrect; use `an error.']

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

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

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. 

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

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

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

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
Received on Tuesday, 4 July 2000 18:12:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:33:53 UTC