From 7c40372a780591998e312d50ac811fa7faad643f Mon Sep 17 00:00:00 2001 From: hniksic Date: Mon, 15 Sep 2003 16:23:55 -0700 Subject: [PATCH] [svn] Fix misspelling. --- doc/ChangeLog | 4 ++++ doc/wget.texi | 8 +++----- 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/doc/ChangeLog b/doc/ChangeLog index 07cd1edf..5ceab908 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,7 @@ +2003-09-16 Noel Kothe + + * wget.texi (Download Options): Fix misspelling. + 2003-09-15 Nicolas Schodet * wget.texi (Download Options): Add link to Proxies. diff --git a/doc/wget.texi b/doc/wget.texi index f32bdf93..578e6fd8 100644 --- a/doc/wget.texi +++ b/doc/wget.texi @@ -695,17 +695,15 @@ Limit the download speed to @var{amount} bytes per second. Amount may be expressed in bytes, kilobytes with the @samp{k} suffix, or megabytes with the @samp{m} suffix. For example, @samp{--limit-rate=20k} will limit the retrieval rate to 20KB/s. This kind of thing is useful when, -for whatever reason, you don't want Wget to consume the entire evailable +for whatever reason, you don't want Wget to consume the entire available bandwidth. -Note that Wget implementeds the limiting by sleeping the appropriate +Note that Wget implements the limiting by sleeping the appropriate amount of time after a network read that took less time than specified by the rate. Eventually this strategy causes the TCP transfer to slow down to approximately the specified rate. However, it takes some time for this balance to be achieved, so don't be surprised if limiting the -rate doesn't work with very small files. Also, the "sleeping" strategy -will misfire when an extremely small bandwidth, say less than 1.5KB/s, -is specified. +rate doesn't work well with very small files. @cindex pause @cindex wait