Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial.xml,v
diff -u -r1.21 -r1.21.2.1
--- openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial.xml	27 Oct 2014 16:39:31 -0000	1.21
+++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial.xml	23 Jun 2016 08:32:46 -0000	1.21.2.1
@@ -37,8 +37,8 @@
       <para>
         This tutorial uses the content repository package.  This
         radically simplifies the database work, but forces us to work
-        around the content repository's limitations, including an
-        incomplete Tcl API.  So the tutorial is messier than we'd like
+        around the content repository&#39;s limitations, including an
+        incomplete Tcl API.  So the tutorial is messier than we&#39;d like
         right now.  Code that is temporary hackage is clearly marked.
       </para>
       
@@ -51,7 +51,7 @@
     <para>You will need:</para>
     <itemizedlist>
       <listitem><para>A computer with a working installation of
-	  OpenACS.  If you don't have this, see <xref linkend="install-overview"/>.
+	  OpenACS.  If you don&#39;t have this, see <xref linkend="install-overview"/>.
 	  </para></listitem>
       <listitem><para>Example files, which are included in the
 standard OpenACS &version; distribution.
@@ -107,7 +107,7 @@
       <listitem>
         <para>Click <computeroutput>Create a New Package</computeroutput>.</para>
         <para>Fill in the fields listed below.   <emphasis role="strong">Ignore the rest (and leave the check boxes alone).</emphasis>
-        (Some will change automatically.  Don't mess with those.)
+        (Some will change automatically.  Don&#39;t mess with those.)
 </para>
         <itemizedlist>
           <listitem><para>
@@ -156,7 +156,7 @@
       <para>You can have instances of a package on one site, each with a
       different URL and different permissions, all sharing the same
       code and tables.  This requires that a package be developed
-      <emphasis>package-aware</emphasis>.  You'll see how to do that
+      <emphasis>package-aware</emphasis>.  You&#39;ll see how to do that
       in this tutorial.</para>
       <orderedlist>
         <listitem><para>Browse to
@@ -167,7 +167,7 @@
           <para>Choose "My First Package" from the list and click OK (the other fields are optional).</para>
         </listitem>
       </orderedlist>
-      <para>By mounting the package, we've caused all requests to
+      <para>By mounting the package, we&#39;ve caused all requests to
       <computeroutput>http://yourserver.test:8000/myfirstpackage</computeroutput>
       to be satisfied from the files at <computeroutput>/var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/www</computeroutput>.</para>
     </sect2>