transfered => transferred

5 files changed, 7 insertions, 7 deletions

diff --git a/html/faq.html b/html/faq.html
index 64aca51..d301459 100644
--- a/html/faq.html
+++ b/html/faq.html
@@ -736,7 +736,7 @@ files and pages from www.someweb.com.<br>
 </em></a><a NAME="Q6">Q: <strong>I have forgotten some URLs of files during a long
 mirror.. Should I redo all?</strong><br>
 A: <em>No, if you have kept the 'cache' files (in hts-cache), cached files will not be
-retransfered.</em><br>
+retransferred.</em><br>
 <br>
 </a><a NAME="Q7">Q: <strong>I just want to retrieve all ZIP files or other files in a web
 site/in a page. How do I do it?</strong><br>
@@ -819,7 +819,7 @@ A: <em>You can't! For security reasons, web servers do not allow that.</em>
 A: <em>Use the footer option (-%F, or see the WinHTTrack options)</em>
 
 <br><br><a NAME="QM3">Q: <strong>Do I have to select between ascii/binary transfer mode?</strong></a><br>
-A: <em>No, http files are always transfered as binary files. Ftp files, too (even if ascii mode could be selected)</em>
+A: <em>No, http files are always transferred as binary files. Ftp files, too (even if ascii mode could be selected)</em>
 
 <br><br><a NAME="QM4">Q: <strong>Can HTTrack perform form-based authentication?</strong></a><br>
 A: <em>Yes. See the URL capture abilities (--catchurl for command-line release, or in the WinHTTrack interface)</em>
diff --git a/html/fcguide.html b/html/fcguide.html
index f86702f..7cb0d08 100644
--- a/html/fcguide.html
+++ b/html/fcguide.html
@@ -2527,7 +2527,7 @@ files and pages from www.all.net.
 mirror..  Should I redo all? </b>
 
 <p align=justify> A: No, if you have kept the 'cache' files (in
-hts-cache), cached files will not be retransfered. 
+hts-cache), cached files will not be retransferred. 
 
 <p align=justify><b>Q: I just want to retrieve all ZIP files or other
 files in a web site/in a page.  How do I do it? </b>
@@ -2636,7 +2636,7 @@ options)
 <p align=justify><b>Q: Do I have to select between ascii/binary transfer
 mode? </b>
 
-<p align=justify> A: No, http files are always transfered as binary
+<p align=justify> A: No, http files are always transferred as binary
 files.  Ftp files, too (even if ascii mode could be selected)
 
 <p align=justify><b>Q: Can HTTrack perform form-based authentication?
diff --git a/html/httrack.man.html b/html/httrack.man.html
index efceee6..42fec1f 100644
--- a/html/httrack.man.html
+++ b/html/httrack.man.html
@@ -1663,7 +1663,7 @@ doing)</b></p>
 
 
 <p style="margin-top: 1em">bypass built&minus;in security
-limits aimed to avoid bandwidth abuses (bandwidth,
+limits aimed to avoid bandwith abuses (bandwidth,
 simultaneous connections)
 (&minus;&minus;disable&minus;security&minus;limits)</p> </td></tr>
 </table>
diff --git a/html/options.html b/html/options.html
index f59b941..bdf86aa 100644
--- a/html/options.html
+++ b/html/options.html
@@ -259,7 +259,7 @@ This option define the maximum transfer rate
 Example: -A2000
 
 GN pause transfer if N bytes reached, and wait until lock file is deleted
-This option asks the engine to pause every time N bytes have been transfered, and restarts when the lock file "hts-pause.lock" is being deleted
+This option asks the engine to pause every time N bytes have been transferred, and restarts when the lock file "hts-pause.lock" is being deleted
 Example: -G20000000
 
 u check document type if unknown (cgi,asp..)
diff --git a/html/plug.html b/html/plug.html
index 1b82c46..93baccd 100755
--- a/html/plug.html
+++ b/html/plug.html
@@ -197,7 +197,7 @@ Below the list of callbacks, and associated external wrappers.
 <tr><td background="img/fade.gif"><i>check_mime</i></td><td background="img/fade.gif">Called when a link download has begun, and needs to be tested against its MIME type. The <tt>adr</tt> and <tt>fil</tt> are the address and URI of the link being tested, and the <tt>mime</tt> string contains the link type being processed. The passed <tt>status</tt> value has the following meaning: 0 if the link is to be accepted by default, 1 if the link is to be refused by default, and -1 if no decision has yet been taken by the engine<br>return value: same meaning as the passed <tt>status</tt> value ; you may generally return -1 to let the engine take the decision by itself</td><td background="img/fade.gif"><tt>int   mycallback(t_hts_callbackarg *carg, httrackp* opt, const char* adr, const char* fil, const char* mime, int status);</tt></td></tr>

 <tr><td background="img/fade.gif"><i>pause</i></td><td background="img/fade.gif">Called when the engine must pause. When the <tt>lockfile</tt> passed is deleted, the function can return<br>return value: none</td><td background="img/fade.gif"><tt>void  mycallback(t_hts_callbackarg *carg, httrackp* opt, const char* lockfile);</tt></td></tr>

 <tr><td background="img/fade.gif"><i>filesave</i></td><td background="img/fade.gif">Called when a file is to be saved on disk<br>return value: none</td><td background="img/fade.gif"><tt>void  mycallback(t_hts_callbackarg *carg, httrackp* opt, const char* file);</tt></td></tr>

-<tr><td background="img/fade.gif"><i>filesave2</i></td><td background="img/fade.gif">Called when a file is to be saved or checked on disk<br>The hostname, filename and local filename are given. Two additional flags tells if the local file is new (is_new), if the local file is to be modified (is_modified), and if the file was not updated remotely (not_updated).<br>(!is_new && !is_modified): the file is up-to-date, and will not be modified<br>(is_new && is_modified): a new file will be written (or an updated file is being written)<br>(!is_new && is_modified): a file is being updated (append)<br>(is_new && !is_modified): an empty file will be written ("do not recatch locally erased files")<br>not_updated: the file was not re-downloaded because it was up-to-date (no data transfered again)<br><br>return value: none</td><td background="img/fade.gif"><tt>void  mycallback(t_hts_callbackarg *carg, httrackp* opt, const char* hostname, const char* filename, const char* localfile, int is_new, int is_modified, int not_updated);</tt></td></tr>

+<tr><td background="img/fade.gif"><i>filesave2</i></td><td background="img/fade.gif">Called when a file is to be saved or checked on disk<br>The hostname, filename and local filename are given. Two additional flags tells if the local file is new (is_new), if the local file is to be modified (is_modified), and if the file was not updated remotely (not_updated).<br>(!is_new && !is_modified): the file is up-to-date, and will not be modified<br>(is_new && is_modified): a new file will be written (or an updated file is being written)<br>(!is_new && is_modified): a file is being updated (append)<br>(is_new && !is_modified): an empty file will be written ("do not recatch locally erased files")<br>not_updated: the file was not re-downloaded because it was up-to-date (no data transferred again)<br><br>return value: none</td><td background="img/fade.gif"><tt>void  mycallback(t_hts_callbackarg *carg, httrackp* opt, const char* hostname, const char* filename, const char* localfile, int is_new, int is_modified, int not_updated);</tt></td></tr>

 

 <tr><td background="img/fade.gif"><i>linkdetected</i></td><td background="img/fade.gif">Called when a link has been detected<br>return value: 1 if the link can be analyzed, 0 if the link must not even be considered</td><td background="img/fade.gif"><tt>int   mycallback(t_hts_callbackarg *carg, httrackp* opt, char* link);</tt></td></tr>

 <tr><td background="img/fade.gif"><i>linkdetected2</i></td><td background="img/fade.gif">Called when a link has been detected<br>return value: 1 if the link can be analyzed, 0 if the link must not even be considered</td><td background="img/fade.gif"><tt>int   mycallback(t_hts_callbackarg *carg, httrackp* opt, char* link, const const char* tag_start);</tt></td></tr>