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 -N -r1.5.2.2 -r1.5.2.3
--- openacs-4/packages/acs-content-repository/www/doc/tutorial.html	14 Aug 2019 07:34:35 -0000	1.5.2.2
+++ openacs-4/packages/acs-content-repository/www/doc/tutorial.html	5 Apr 2021 19:49:49 -0000	1.5.2.3
@@ -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>
@@ -733,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>