--- rxvt-unicode/doc/rxvt.1.pod	2006/04/02 17:07:32	1.113
+++ rxvt-unicode/doc/rxvt.1.pod	2006/07/06 19:43:21	1.114
@@ -44,17 +44,17 @@
 
 Therefore another design rationale was the use of multiple fonts to
 display characters: The idea of a single unicode font which many other
-programs force onto it's users never made sense to me: You should be able
+programs force onto its users never made sense to me: You should be able
 to choose any font for any script freely.
 
 Apart from that, rxvt-unicode is also much better internationalised than
-it's predecessor, supports things such as XFT and ISO 14755 that are handy
+its predecessor, supports things such as XFT and ISO 14755 that are handy
 in i18n-environments, is faster, and has a lot less bugs than the original
 rxvt. This all in addition to dozens of other small improvements.
 
 It is still faithfully following the original rxvt idea of being lean
 and nice on resources: for example, you can still configure rxvt-unicode
-without most of it's features to get a lean binary. It also comes with
+without most of its features to get a lean binary. It also comes with
 a client/daemon pair that lets you open any number of terminal windows
 from within a single process, which makes startup time very fast and
 drastically reduces memory usage. See @@RXVT_NAME@@d(1) (daemon) and
@@ -187,7 +187,7 @@
 smaller, but not (in general) larger. A (hopefully) reasonable default
 font list is always appended to it. See resource B<font> for more details.
 
-In short, to specify an X11 core font, just specify it's name or prefix it
+In short, to specify an X11 core font, just specify its name or prefix it
 with C<x:>. To specify an XFT-font, you need to prefix it with C<xft:>,
 e.g.:
 
@@ -425,7 +425,7 @@
 
 =item B<-embed> I<windowid>
 
-Tells @@RXVT_NAME@@ to embed it's windows into an already-existing window,
+Tells @@RXVT_NAME@@ to embed its windows into an already-existing window,
 which enables applications to easily embed a terminal.
 
 Right now, @@RXVT_NAME@@ will first unmap/map the specified window, so it
@@ -1030,7 +1030,7 @@
 can start or end with whitespace.
 
 Please note that you need to double the C<\> in resource files, as
-Xlib itself does it's own de-escaping (you can use C<\033> instead of
+Xlib itself does its own de-escaping (you can use C<\033> instead of
 C<\e> (and so on), which will work with both Xt and @@RXVT_NAME@@'s own
 processing).
 
@@ -1275,7 +1275,7 @@
 
 Start by pressing C<Control> and C<Shift> together, then releasing
 them. The next special key (cursor keys, home etc.) you enter will not
-invoke it's usual function but instead will insert the corresponding
+invoke its usual function but instead will insert the corresponding
 keycap symbol. The symbol will only be entered when the key has been
 released, otherwise pressing e.g. C<Shift> would enter the symbol for
 C<ISO Level 2 Switch>, although your intention might have been to enter a
@@ -1434,7 +1434,7 @@
 =item B<DISPLAY>
 
 Used by @@RXVT_NAME@@ to connect to the display and set to the correct
-display in it's child processes.
+display in its child processes.
 
 =item B<SHELL>