emacs-jabber jabber.texi,1.100,1.101

[Magnus H. <leg...@us...>]

Update of /cvsroot/emacs-jabber/emacs-jabber
In directory sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv22252

Modified Files:
	jabber.texi 
Log Message:
Revision: ma...@fr...--2005/emacs-jabber--cvs-head--0--patch-518
Creator:  Magnus Henoch <ma...@fr...>

Documentation: file transfer

Unfortunately, not much to change here...


Index: jabber.texi
===================================================================
RCS file: /cvsroot/emacs-jabber/emacs-jabber/jabber.texi,v
retrieving revision 1.100
retrieving revision 1.101
diff -u -d -r1.100 -r1.101
--- jabber.texi	21 May 2008 15:06:58 -0000	1.100
+++ jabber.texi	31 May 2008 05:49:27 -0000	1.101
@@ -675,14 +675,14 @@
 limit is that files sent and received are kept in buffers, so Emacs must
 be able to allocate enough memory for the entire file, and the file size
 must be smaller than the maximum buffer size.@footnote{The maximum
-buffer size is kept in the variable @code{most-positive-fixnum}.  On
-most 32-bit systems, this is 128 or 256 megabytes, depending on your
+buffer size depends on in the variable @code{most-positive-fixnum}.  On
+32-bit systems, this is 128 or 256 megabytes, depending on your
 Emacs version.}
 
 jabber.el is able to exchange files with most Jabber clients (and also
 some MSN transports), but notably not with the official Google Talk
 client.  The Google Talk client uses a different file transfer protocol
-that, at the time of this release, has not been published.
+which, at the time of this release, has not been published.
 
 @menu
 * Receiving files::             
@@ -705,6 +705,7 @@
 is done, the message ``@var{file} downloaded'' appears in the echo area,
 and the buffer is killed.
 
+@c This truly sucks...
 If this doesn't happen, it is most likely the sender's fault.  The
 sender needs to have a public IP address, either directly, through port
 forwarding (in which case the client needs to be configured with the