minor typo fixes here and there.

[ardour-manual] / _manual / 12_adding-pre-existing-material / 02_copying-versus-linking.html

diff --git a/_manual/12_adding-pre-existing-material/02_copying-versus-linking.html b/_manual/12_adding-pre-existing-material/02_copying-versus-linking.html
index 3167c252ab6b265a0b160fc1fe649d0bb2ff53b9..359c9b26753fc5229c965779571fa12ba018dae9 100644 (file)
--- a/_manual/12_adding-pre-existing-material/02_copying-versus-linking.html
+++ b/_manual/12_adding-pre-existing-material/02_copying-versus-linking.html
@@ -6,11 +6,13 @@ title: Copying versus Linking
 <p>
   <dfn>Copying</dfn> and <dfn>linking</dfn> are two different methods of 
   using existing audio files on your computer (or network file system) 
-  within a session. They differ in one key aspect:</p>
+  within a session. They differ in one key aspect:
+</p>
+
 <h2>Copying</h2>
 <p>
   An existing media file is copied to the session's audio folder, and 
-  if necessary is converted into the session's native format.<br />
+  if necessary converted into the session's native format.<br />
   For audio files, you can control the choice of this format (eg. WAVE 
   or Broadcast WAVE). Audio files will also be converted to the session 
   sample rate if necessary (which can take several minutes for larger 
@@ -20,10 +22,11 @@ title: Copying versus Linking
   MIDI files will already be in SMF format, and are simply copied into 
   the session's MIDI folder.
 </p>
+
 <h2>Linking</h2>
 <p>
   A link to an existing media file somewhere on the disk is used as a the
-  source for a region, but the data is<strong>not copied or modified</strong> 
+  source for a region, but the data is <strong>not copied or modified</strong> 
   in any way.
 </p>
 <p class="warning">