Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/rp.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/rp.xml,v
diff -u -r1.12.6.1 -r1.12.6.2
--- openacs-4/packages/acs-core-docs/www/xml/developers-guide/rp.xml	23 Jun 2016 08:32:46 -0000	1.12.6.1
+++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/rp.xml	3 Oct 2016 09:17:51 -0000	1.12.6.2
@@ -105,7 +105,7 @@
 in the <computeroutput>.vuh</computeroutput> file to act like a registered procedure for
 an entire subtree of the URL namespace.  Thus a <computeroutput>.vuh</computeroutput> file
 can be thought of as a replacement for filters and registered procs,
-except that they integrate cleanly and correctly with the RP's URL
+except that they integrate cleanly and correctly with the RP&#39;s URL
 mapping mechanisms.  The details of how to use these files are
 described in <xref linkend="rp-design"/>.
 </para>
@@ -128,7 +128,7 @@
 <para>
 Once the flow of control reaches a dynamic page, the Request Processor
 has populated the environment of the request with several pieces of
-useful information. The RP's environment is accessible through the
+useful information. The RP&#39;s environment is accessible through the
 <computeroutput>ad_conn</computeroutput> interface, and the following calls should be
 useful to you when developing dynamic pages:
 </para>