Index: openacs-4/packages/acs-content-repository/www/doc/tutorial.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/tutorial.html,v
diff -u -r1.5 -r1.6
--- openacs-4/packages/acs-content-repository/www/doc/tutorial.html	28 Sep 2018 08:37:58 -0000	1.5
+++ openacs-4/packages/acs-content-repository/www/doc/tutorial.html	3 Sep 2024 15:37:31 -0000	1.6
@@ -9,7 +9,7 @@
       
       <h2>How to use the content repository</h2>
       
-      by <a href="http://rubick.com">Jade Rubick</a>
+      by <a href="http://web.archive.org/web/20180809082906/http://www.rubick.com/">Jade Rubick</a>
       
       <h3>Why use the content repository?</h3>
       
@@ -557,7 +557,7 @@
 
 <h3>Structuring your data into a hierarchy</h3>
 
-The content repository also has a very useful facility for organizing your data into a hierarchy, very similar to a file-system. Just like a file system, you can have folders to store items inside of, and organize your information. The main difference is that every item can also contain other items. So in our case, we can have tasks that contain other tasks. This is a useful way for us to specify sub-tasks, and sub-sub-tasks. In my case, building project-management software, this also allows my tasks to be stored underneath their given project.
+The content repository also has a very useful facility for organizing your data into a hierarchy, very similar to a file-system. Just like a filesystem, you can have folders to store items inside of, and organize your information. The main difference is that every item can also contain other items. So in our case, we can have tasks that contain other tasks. This is a useful way for us to specify sub-tasks, and sub-sub-tasks. In my case, building project-management software, this also allows my tasks to be stored underneath their given project.
 <P>
 Using this structure is optional, but useful in many circumstances.
 <P>
@@ -645,7 +645,10 @@
 </pre></blockquote>
 
 
-Note that this example is for projects rather than tasks. This is because for the application I'm writing, projects are what tasks are stored inside of. A project has many component tasks. If you were writing another application, or if I wasn't doing anything with projects, then this would be creating a folder for just tasks.
+Note that this example is for projects rather than tasks. This is
+because for the application I'm writing, projects are what tasks are
+stored inside of. A project has many component tasks. If you were
+writing another application, or if I was not doing anything with projects, then this would be creating a folder for just tasks.
 
 <P>
 Typically, this definition would go in your <code>sql/postgresql/project-manager-create.sql</code> file. If this file is broken in several parts, this would go in the project-manager-create-functions.sql portion.
@@ -730,9 +733,9 @@
 
 <DL><DT>Content Revision<DD>A revision consists of the complete state of the item as it existed at a certain point in time.  This includes the main text or binary object associated with the item, as well as all attributes.</DL>
 
-<DL><DT>Content Folder<DD>A folder is analogous to a folder or directory in a file system.  It represents a level in the content item hierarchy.  In the previous example, press-releases is a folder under the repository root, and products is folder within that.  </DL>
+<DL><DT>Content Folder<DD>A folder is analogous to a folder or directory in a filesystem.  It represents a level in the content item hierarchy.  In the previous example, press-releases is a folder under the repository root, and products is folder within that.  </DL>
 
-<DL><DT>Symbolic Link<DD>Analogous to a symlink, alias or shortcut in a file system. Allows an item to be accessed from multiple folders.</DL>
+<DL><DT>Symbolic Link<DD>Analogous to a symlink, alias or shortcut in a filesystem. Allows an item to be accessed from multiple folders.</DL>
 
 <DL><DT>Templates<DD>Templates are merged with content items to render output in HTML or other formats. Templates are assumed to be text files containing static markup with embedded tags or code to incorporate dynamic content in appropriate places.</DL>
 
@@ -742,7 +745,9 @@
 
 <h3>Troubleshooting</h3>
 
-One problem I ran into while trying to get my SQL create and drop scripts working was that sometimes I wasn't able to delete a content type because I would get errors like these:
+One problem I ran into while trying to get my SQL create and drop
+scripts working was that sometimes I was not able to delete a content
+type because I would get errors like these:
 
 <blockquote><pre>
 Referential Integrity: attempting to delete live_revision: 658