--- rxvt-unicode/doc/rxvtc.1.man.in	2006/07/22 05:35:16	1.5
+++ rxvt-unicode/doc/rxvtc.1.man.in	2007/12/14 06:05:40	1.8
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.09 (Pod::Simple 3.04)
+.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.35
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -129,7 +129,7 @@
 .\" ========================================================================
 .\"
 .IX Title "@@RXVT_NAME@@ 1"
-.TH @@RXVT_NAME@@ 1 "2006-07-22" "7.8" "RXVT-UNICODE"
+.TH @@RXVT_NAME@@ 1 "2007-12-14" "8.7" "RXVT-UNICODE"
 .SH "NAME"
 @@RXVT_NAME@@c \- control the @@RXVT_NAME@@d daemon
 .SH "SYNOPSIS"
@@ -147,7 +147,7 @@
 All options that are valid for \fB@@RXVT_NAME@@\fR are valid for
 \&\fB@@RXVT_NAME@@c\fR, too. Please note that options are interpreted in the
 context of the daemon process. However, as current working directory,
-process environment and any file handles (e.g. for \f(CW\*(C`\-pty\-fd\*(C'\fR) are
+process environment and any file descriptor (e.g. for \f(CW\*(C`\-pty\-fd\*(C'\fR) are
 preserved, this rarely makes a difference.
 .SH "EXIT STATUS"
 .IX Header "EXIT STATUS"
@@ -162,8 +162,8 @@
 .Vb 6
 \&   #!/bin/sh
 \&   @@RXVT_NAME@@c "$@"
-\&   if [ $? \-eq 2 ]; then
-\&      @@RXVT_NAME@@d \-q \-o \-f
+\&   if [ $? -eq 2 ]; then
+\&      @@RXVT_NAME@@d -q -o -f
 \&      @@RXVT_NAME@@c "$@"
 \&   fi
 .Ve
@@ -177,7 +177,7 @@
 Both @@RXVT_NAME@@c and @@RXVT_NAME@@d use the environment variable
 \&\fI\s-1RXVT_SOCKET\s0\fR to create a listening socket and to contact the
 @@RXVT_NAME@@d, respectively. If the variable is missing,
-\&\fI\f(CI$HOME\fI/.rxvt\-unicode\-\fI<nodename>\fI\fR is used.  The variable must
+\&\fI$HOME/.rxvt\-unicode\-\fI<nodename>\fI\fR is used.  The variable must
 specify the absolute path of the socket to create.
 .SH "SEE ALSO"
 .IX Header "SEE ALSO"