Index: openacs-4/packages/acs-content-repository/www/doc/guide/file-system.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/guide/file-system.adp,v
diff -u -N -r1.4 -r1.5
--- openacs-4/packages/acs-content-repository/www/doc/guide/file-system.adp	30 Apr 2018 08:15:07 -0000	1.4
+++ openacs-4/packages/acs-content-repository/www/doc/guide/file-system.adp	1 Nov 2018 08:46:40 -0000	1.5
@@ -14,7 +14,7 @@
 <li>A freshly installed content repository consists of a single
 "root" folder (analogous to the root directory
 <kbd>/</kbd> in UNIX or an empty partition in Windows or
-MacOS).</li><li>You organize items by creating subfolders under the root.</li><li>You can move or copy items from one folder to another.</li><li>You can create "links" or "shortcuts" for
+macOS).</li><li>You organize items by creating subfolders under the root.</li><li>You can move or copy items from one folder to another.</li><li>You can create "links" or "shortcuts" for
 items to make them accessible from within other directories.</li><li>Each item has a "file name" and an absolute
 "path" that is determined by its location on a particular
 branch of the repository tree. For example, the path to an item
@@ -62,7 +62,7 @@
 <ul>
 <li>Content management systems can take advantage of the folder
 structure to implement an intuitive user interface analogous to
-familiar desktop tools (Windows Explorer, MacOS Finder, etc.).</li><li>You can use the content repository API to constraint the type
+familiar desktop tools (Windows Explorer, macOS Finder, etc.).</li><li>You can use the content repository API to constraint the type
 of content that a folder may contain (except for the index page).
 For example, it is possible to limit the contents of the
 "Press" folder to items of type "Press
@@ -77,7 +77,7 @@
 content root. Creating your own content (and template) root also
 has the advantage that you will not accidentally access another
 package&#39;s content nor will another package access your content.
-Not that that could do any harm, because you have secured all your
+Note that could do any harm, because you have secured all your
 content through appropriate permissions.</p>
 <p>We only talk about creating content roots from here on —
 creating template roots is completely analogous. You create your