Package: bittornado Version: 0.3.11-4 Severity: minor Tags: patch
Found some typos in '/usr/share/man/man1/bittorrent-downloader.bittornado.1.gz', see attached '.diff'. Hope this helps... -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.11-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages bittornado depends on: ii python 2.3.5-2 An interactive high-level object-o -- no debconf information
--- - 2005-05-23 02:44:35.796936000 -0400 +++ /tmp/bittorrentdownloader.bittornado.1.gz.10174 2005-05-23 02:44:35.000000000 -0400 @@ -27,7 +27,7 @@ A summary of options is included below. .TP .B \-\-responsefile \fIfilename\fP -treat \fIfilename\fP as a file which the server reponse was stored in. If this +treat \fIfilename\fP as a file which the server response was stored in. If this option is used, no filename or URL should be present on the command line. .TP .B \-\-url \fIurl\fP @@ -69,7 +69,7 @@ set \fIbytes\fP to the maximum length prefix encoding you'll accept over the wire - larger values get the connection dropped (default 8388608) .TP .B \-\-timeout \fIsecs\fP -wait \fIsecs\fP before closing sockets which nothing has been recieved on (default 300.0) +wait \fIsecs\fP before closing sockets which nothing has been received on (default 300.0) .TP .B \-\-timeout_check_interval \fIsecs\fP check whether connections have timed out every \fIsecs\fP seconds (default 60.0) @@ -111,7 +111,7 @@ whether to check hashes on disk (defaults to 1) .TP .B \-\-report_hash_failures \fI 1 | 0 \fP -whether to report to the user that hash failuers occur (non-fatal, common error) (default 0) +whether to report to the user that hash failures occur (non-fatal, common error) (default 0) .TP .B \-\-rarest_first_priority_cutoff \fInum\fP the number of peers which need to have a piece before other partials take
