Index: openacs-4/packages/acs-content-repository/www/doc/guide/file-system.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/guide/file-system.html,v
diff -u -r1.2 -r1.3
--- openacs-4/packages/acs-content-repository/www/doc/guide/file-system.html	7 Aug 2017 23:47:47 -0000	1.2
+++ openacs-4/packages/acs-content-repository/www/doc/guide/file-system.html	28 Sep 2018 08:37:58 -0000	1.3
@@ -17,7 +17,7 @@
 <ul>
   <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).
+      empty partition in Windows or macOS).
 
   <li>You organize items by creating subfolders under the root.
 
@@ -83,7 +83,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.).
+      tools (Windows Explorer, macOS Finder, etc.).
 
   <li>You can use the content repository API to constraint the type of
       content that a folder may contain (except for the index page).
@@ -101,7 +101,7 @@
       might wish to store the content for each instance in its own content
       root. Creating your own content (and template) root also has the
       advantage that you will not accidentally access another package's
-      content nor will another package access your content. Not that that
+      content nor will another package access your content. Not that
       could do any harm, because you have secured all your content through
       appropriate permissions.
     </p>