Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml,v
diff -u -r1.9 -r1.9.14.1
--- openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml	17 Jul 2006 05:38:37 -0000	1.9
+++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml	23 Jun 2016 08:32:46 -0000	1.9.14.1
@@ -75,14 +75,14 @@
       packages that have been installed in the server, where those packages
       have been installed, and a standard way to map URLs that a client
       sends to our server to the right page in the appropriate
-      package. While we're at it, this tool should also automate
+      package. While we're at it, this tool should also automate
       package installation, dependency checking, upgrades, and package
       removal. In OpenACS &majorversion;, this tool is called the <link linkend="packages-apm">APM</link>.
     </para>
 
     <para>
       <indexterm id="baby"><primary>OpenACS Package</primary></indexterm>
-      To illustrate the general structure of a package, let's see what the
+      To illustrate the general structure of a package, let&#39;s see what the
       package for the "notes" application should look like.
     </para>
 
@@ -452,7 +452,7 @@
 
 
       <listitem><para>Fill out the form for adding a new package. The form explains what
-      everything means, but we'll repeat the important bits here for easy
+      everything means, but we&#39;ll repeat the important bits here for easy
       reference:
 
       <variablelist>
@@ -486,8 +486,8 @@
           <listitem><para>
           If your package name is a nice singular noun, this should be the
           plural form of it. I assume the plural form is used when multiple
-          instances of the package are used by a single service. We'll talk more
-          about package instances later. Our example apllication doesn't really
+          instances of the package are used by a single service. We&#39;ll talk more
+          about package instances later. Our example apllication doesn&#39;t really
           have a good plural name. So just make it also be "Notes".
         </para></listitem>
         </varlistentry>
@@ -558,7 +558,7 @@
           The directory that APM created will be empty except for the
           <computeroutput>notes.info</computeroutput> file. Create a file
           called
-          <computeroutput>ROOT/packages/notes/sql/oracle/notes-create.sql</computeroutput>. We'll
+          <computeroutput>ROOT/packages/notes/sql/oracle/notes-create.sql</computeroutput>. We&#39;ll
           fill this file with our <link linkend="objects">data model</link>
           very soon. Create a file called
           <computeroutput>ROOT/packages/notes/sql/oracle/notes-drop.sql</computeroutput>. This
@@ -637,11 +637,11 @@
 
     <para>
       At this point, you are probably excited to see your new package in
-      action. But, we haven't added any user visible pages yet. By
+      action. But, we haven&#39;t added any user visible pages yet. By
       convention, user visible pages go in the
       <computeroutput>ROOT/packages/notes/www</computeroutput> directory. So go there and add a
       file called <computeroutput>hello.html</computeroutput> with some text in it. Now we have
-      to make the user pages visible in the site. Since we didn't put the
+      to make the user pages visible in the site. Since we didn&#39;t put the
       pages underneath <computeroutput>ROOT/www</computeroutput> they will not appear on their
       own.  What we have to do is <emphasis>mount</emphasis> the application into the site
       map. That is, we have to define the URL from which the application
@@ -690,7 +690,7 @@
       <computeroutput>ROOT/packages/notes/www</computeroutput>. At this point, you can
       experiment with the site map by mounting multiple instances of the not
       yet written Notes application at various places in the site. In a
-      later document, we'll see how to write your application so that the
+      later document, we&#39;ll see how to write your application so that the
       code can detect from what URL it was invoked. This is the key
       to supporting <link linkend="subsites">subsites</link>.
     </para>
@@ -721,7 +721,7 @@
     </para></listitem>
       <listitem><para>
       Writes out package distribution files for other people to download and
-      install. We'll cover this later.
+      install. We&#39;ll cover this later.
     </para></listitem>
     </itemizedlist>