X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Ffiles-and-directories-ardour-knows-about.html;h=4daf1ce5aa20d8283402d70066c9436b2344a219;hb=a61fbacdfcb7a76fe425fada61f49fc85751e47a;hp=57b72379d4d724dd3beede750c4d017338d68e53;hpb=0f52306465e67143a3a7928cf4b8ecdbfa42569f;p=ardour-manual

diff --git a/include/files-and-directories-ardour-knows-about.html b/include/files-and-directories-ardour-knows-about.html
index 57b7237..4daf1ce 100644
--- a/include/files-and-directories-ardour-knows-about.html
+++ b/include/files-and-directories-ardour-knows-about.html
@@ -29,7 +29,7 @@
   For example, <code>ardour5</code> where the Ardour version is 5.6.
 </p>
 <p class="note">
-  In Linux, all path names are lower case and case matters.
+  In Linux, all path names are lowercase and case-sensitive.
 </p>
 
 <h3>macOS</h3>
@@ -59,13 +59,13 @@
   a real path.
 </p>
 <p>
-  An example of a configuration path in Window (from xp) would be:
-  <code>C:\Documents and Settings\&lt;User&gt;\Application Data\Local Settings\Ardour5\</code>
+  An example of a configuration path in Window 10 would be:
+  <code>C:\&lt;User&gt;\AppData\Local\Ardour5\</code>
   The user in the path would be the user's account name.
 </p>
 <p class="note">
   The above is only an example and may not even be true for all installations
-  of Windows XP.
+  of Windows 10.
 </p>
 
 <h2>Plugins</h2>
@@ -95,13 +95,14 @@
 
 <h4>LV2</h4>
 <p>
-  LADSPA plugins should be found in  <code>/usr/lib/lv2/</code>,
+  LV2 plugins should be found in  <code>/usr/lib/lv2/</code>,
   <code>/usr/local/lib/lv2/</code>
   or in a directory mentioned in your LV2_PATH environment variable.
   The most common mistake made by distro packagers, is to use a path
-  like <code>/usr/lib/$ARCH/lv2/</code> and find that Ardour will not find that by
-  default. The user can either add a link from this actual directory to
-  the standard directory or add this path to LV2_PATH.
+  like <code>/usr/lib/$ARCH/lv2/</code>, <code>/usr/lib64/lv2</code>
+  or <code>/usr/local/lib64/lv2</code> and find that Ardour will not find
+  that by default. The user can either add a link from this actual directory
+  to the standard directory or add this path to LV2_PATH.
 </p>
 
 <h4>Linux VST or lxvst</h4>
@@ -132,8 +133,8 @@
 <h3>Windows</h3>
 <p>
  The most common plugins on Windows are VSTs. However, LADSPA and LV2
- plugins are available for windows as well. In fact Ardours built in
- plugins are LV2s. The biggest advanatage of LV2 plugins is that they are
+ plugins are available for windows as well. In fact Ardour's built in
+ plugins are LV2s. The biggest advantage of LV2 plugins is that they are
  the most likely to be cross platform and therefore allow the same Ardour
  project to be worked on in Windows, OSX and Linux.
 </p>
@@ -147,7 +148,7 @@
 <h4>LV2</h4>
 <p>
   The LV2 standard for Windows is <code>%APPDATA%/LV2/</code> or
-  <code>%COMMONPROGRAMFILES%/LV2/</code>
+  <code>%COMMONPROGRAMFILES%/LV2/</code> (On Windows 10: <code>C:\&lt;User&gt;\AppData\Roaming\LV2\</code> or <code>C:\Program Files\Common Files\LV2\</code>).
 </p>
 
 <h2>Project Directory</h2>
@@ -155,10 +156,10 @@
   Ardour places a project directory where the user tells it to. This
   directory is chosen when creating a project. In most cases the user
   does not need to know about the files inside of the project directory.
-  However there are a few subdirectories worth noting.
+  However there are a few sub-directories worth noting.
 </p>
 <h3>export</h3>
 <p>
-  This is the subdirectory where exported files end up.
+  This is the sub-directory where exported files end up.
 </p>