repo: rxvt-unicode-sixel
action: commit
revision: 
path_from: 
revision_from: 45a5461b61516336bc11d65d2898850e6d55b3b8:
path_to: 
revision_to: 
git.thebackupbox.net
rxvt-unicode-sixel
git clone git://git.thebackupbox.net/rxvt-unicode-sixel
commit 45a5461b61516336bc11d65d2898850e6d55b3b8
Author: Marc Lehmann 
Date:   Thu Nov 25 02:49:37 2010 +0000

    *** empty log message ***

diff --git a/doc/rxvt.7.pod b/doc/rxvt.7.pod
index b07673b91c62d4726e113886ff33dfbdb6f5212a..
index ..ecaf8a9839f191b644ec43eb8a9d0eac72a64d85 100644
--- a/doc/rxvt.7.pod
+++ b/doc/rxvt.7.pod
@@ -201,7 +201,7 @@ are defined by things like X11, pseudo terminals, locale support and unix
 domain sockets, which are all less portable than C++ itself.

 Regarding the bloat, see the above question: It's easy to write programs
-in C that use gobs of memory, an certainly possible to write programs in
+in C that use gobs of memory, and certainly possible to write programs in
 C++ that don't. C++ also often comes with large libraries, but this is
 not necessarily the case with GCC. Here is what rxvt links against on my
 system with a minimal config:

-----END OF PAGE-----