Index: openacs-4/packages/acs-developer-support/www/doc/index.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-developer-support/www/doc/index.adp,v
diff -u -r1.2.2.6 -r1.2.2.7
--- openacs-4/packages/acs-developer-support/www/doc/index.adp	9 Jun 2016 13:03:12 -0000	1.2.2.6
+++ openacs-4/packages/acs-developer-support/www/doc/index.adp	5 Jul 2016 12:18:25 -0000	1.2.2.7
@@ -17,16 +17,16 @@
 <h2>The Big Picture</h2>
 <p>Software development is a big feedback loop: a developer writes
 something, tests it, and then repeats until the results are
-satisfactory. It's important to streamline this cycle by having a
-development environment which makes it easy to analyze what the
+satisfactory. It&#39;s important to streamline this cycle by having
+a development environment which makes it easy to analyze what the
 software is doing under the hood.</p>
 <h2>Peeking Under the Hood</h2>
 <p>Our development environment previously consisted largely of
 Emacs, and <tt>tail -f
 /web/servername/log/servername-error.log</tt>. Now this has been
 augmented: <tt>ad_footer</tt> and <tt>ad_admin_footer</tt> now
-display a link entitled <em>Developer Information</em>. (You can use
-the <tt>ds_link</tt> procedure to generate the link yourself.)
+display a link entitled <em>Developer Information</em>. (You can
+use the <tt>ds_link</tt> procedure to generate the link yourself.)
 Following the link displays a screenful of information
 including:</p>
 <ul>
@@ -47,8 +47,8 @@
 
 Tired of using <tt>ns_log</tt>
  to instrument your code, then
-grokking the error log to see what's wrong with your page? Use the
-<tt>ds_comment</tt>
+grokking the error log to see what&#39;s wrong with your page? Use
+the <tt>ds_comment</tt>
  routine instead:
 <blockquote><pre>
 ds_comment "Foo is $foo"