Index: openacs-4/packages/acs-core-docs/www/tutorial-categories.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-categories.html,v
diff -u -r1.14.2.5 -r1.14.2.6
--- openacs-4/packages/acs-core-docs/www/tutorial-categories.html	10 Jun 2016 07:35:08 -0000	1.14.2.5
+++ openacs-4/packages/acs-core-docs/www/tutorial-categories.html	23 Jun 2016 08:32:46 -0000	1.14.2.6
@@ -3,18 +3,18 @@
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
         </div><p>You can associate any ACS Object with one or more categories.
-    In this tutorial we'll show how to equip your application with user
+    In this tutorial we&#39;ll show how to equip your application with user
     interface to take advantage of the Categories service.
     </p><p>
-    We'll start by installing the Categories service.  Go to
+    We&#39;ll start by installing the Categories service.  Go to
     <code class="computeroutput">/acs/admin</code> and install it.  This step
-    won't be necessary for the users of your applications because you'll create
+    won&#39;t be necessary for the users of your applications because you&#39;ll create
     a dependency with the Package Manager which will take care that the
     Categories service always gets installed when your application gets
     installed.
     </p><p>
     Now that we have installed the Categories service we can proceed to
-    modifying our application so that it can take advantage of it.  We'll do it
+    modifying our application so that it can take advantage of it.  We&#39;ll do it
     in three steps:
     </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
           The Categories service provides a mechanism to associate one or
@@ -59,8 +59,8 @@
           to categorize items.  The easiest way to do this is by adding the
           <code class="computeroutput">category</code> widget type of the
           form builder to <code class="computeroutput">note-edit.tcl</code>.
-          To achieve this we'll need to use the <code class="computeroutput">-extend</code>
-          switch to the <code class="computeroutput">ad_form</code> command. Here's the "meat" of the
+          To achieve this we&#39;ll need to use the <code class="computeroutput">-extend</code>
+          switch to the <code class="computeroutput">ad_form</code> command. Here&#39;s the "meat" of the
           <code class="computeroutput">note-edit.tcl</code> page:</p><pre class="programlisting">
 			# extend the form to support categories
 			set package_id [ad_conn package_id]
@@ -95,7 +95,7 @@
 should initially be absert.  If it is absent, we create a form to
 allow the user to confirm the deletion.  Note that in
 <code class="computeroutput">entry-edit.tcl</code> we used <code class="computeroutput">ad_form</code> to access the Form Template
-commands; here, we call them directly because we don't need the extra
+commands; here, we call them directly because we don&#39;t need the extra
 features of ad_form.  The form calls itself, but
 with hidden variables carrying both
 <code class="computeroutput">note_id</code> and
@@ -226,7 +226,7 @@
         		set category_name [category::get_name $category_id]
         		if { $category_name eq "" } {
             		ad_return_exception_page 404 "No such category" "Site-wide \
-          			Category with ID $category_id doesn't exist"
+          			Category with ID $category_id doesn&#39;t exist"
             		return
         		}
         		# Show Category in context bar