=== modified file 'protocols/ft.h'
--- protocols/ft.h	2007-12-04 00:48:57 +0000
+++ protocols/ft.h	2008-02-15 19:00:12 +0000
@@ -47,7 +47,7 @@
  * imcb_file_send_start() method, which will initialize most of the fields. The data field and the various
  * methods are zero-initialized. Instances will automatically be deleted once the transfer is completed,
  * canceled, or the connection to the irc client has been lost (note that also if only the irc connection
- * and not the dcc connection is lost, the file transfer will still be canceled and freed).
+ * and not the file transfer connection is lost, the file transfer will still be canceled and freed).
  *
  * The following (poor ascii-art) diagram illustrates what methods are called for which status-changes:
  *
@@ -159,7 +159,7 @@
 } file_transfer_t;
 
 /*
- * This starts a file transfer from bitlbee to the user (currently via DCC).
+ * This starts a file transfer from bitlbee to the user.
  */
 file_transfer_t *imcb_file_send_start( struct im_connection *ic, char *user_nick, char *file_name, size_t file_size );
 

=== modified file 'protocols/jabber/si.c'
--- protocols/jabber/si.c	2007-12-18 02:07:59 +0000
+++ protocols/jabber/si.c	2008-02-15 19:00:12 +0000
@@ -211,7 +211,7 @@
 
 	imcb_log( ic, "File transfer request from %s for %s (%zd kb). ", xt_find_attr( node, "from" ), name, size/1024 );
 
-	imcb_log( ic, "Accept the DCC transfer if you'd like the file. If you don't, issue the 'transfers reject' command.");
+	imcb_log( ic, "Accept the file transfer if you'd like the file. If you don't, issue the 'transfers reject' command.");
 
 	tf = g_new0( struct jabber_transfer, 1 );