Index: openacs-4/packages/acs-content-repository/www/doc/requirements.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/requirements.html,v
diff -u -N -r1.3 -r1.3.2.1
--- openacs-4/packages/acs-content-repository/www/doc/requirements.html	7 Aug 2017 23:47:47 -0000	1.3
+++ openacs-4/packages/acs-content-repository/www/doc/requirements.html	5 Apr 2021 19:49:48 -0000	1.3.2.1
@@ -166,8 +166,7 @@
 <blockquote>
 
 <p><strong>40.10</strong>. The data model must support the hierarchical
-organization of content items in a manner similar to a file
-system.</p>
+organization of content items in a manner similar to a filesystem.</p>
 
 <p><strong>40.20</strong>. The URL of a content item should reflect its location
 in the hierarchy.  For example, a press release with the URL
@@ -176,8 +175,7 @@
 
 <p><a name=folder><strong>40.20.5 Content Folder</strong></a>.</p>
 
-<p>A <em>folder</em> is analogous to a folder or directory in a file
-system.  It represents a level in the content item hierarchy.  In the
+<p>A <em>folder</em> is analogous to a folder or directory in a filesystem.  It represents a level in the content item hierarchy.  In the
 previous example, <kbd>press-releases</kbd> is a folder under the
 repository root, and <kbd>products</kbd> is folder within that.  The
 description of a folder may include the following information:</p>
@@ -204,7 +202,7 @@
 <p><a name=folder><strong>40.30.5 Content Symbolic Link</strong>.</p>
 
 <p>A <em>symbolic link</em> is analogous to a symlink, alias or
-shortcut in a file system.  The description of a symbolic link must include
+shortcut in a filesystem.  The description of a symbolic link must include
 the following information:</p>
 
 <p><strong>40.30.5.10</strong>. A URL-encoded name for the symbolic link.  As
@@ -394,7 +392,7 @@
 <p><strong>100.50 Content Folders</strong></p>
 
 <p>The repository should allow for hierarchical arrangement of content
-items in a manner similar to a file system.  The API to meet this
+items in a manner similar to a filesystem.  The API to meet this
 general requirement focuses primarily on <a href="#folder">content
 folders</a>:</p>