Initial cleanup of manual content.

[ardour-manual] / include / overview-of-all-timecode-related-settings.html

diff --git a/include/overview-of-all-timecode-related-settings.html b/include/overview-of-all-timecode-related-settings.html
index 231914857f444b24345cbaa9641a688c054b00c2..b0994c01364ce38a57c48ece8c708b67adec4c6a 100644 (file)
--- a/include/overview-of-all-timecode-related-settings.html
+++ b/include/overview-of-all-timecode-related-settings.html
@@ -69,8 +69,8 @@
     further mentions that drop-frame timecode has an accumulated error of -86ms 
     over a 24-hour period. Drop-frame timecode would compensate exactly for a 
     NTSC color frame rate of 30 * 0.9990 (ie 29.970000). That is not the actual 
-    rate. However, some vendors use that rate — despite it being against 
-    the specs — because the variant of using exactly 29.97 fps has zero 
+    rate. However, some vendors use that rate—despite it being against 
+    the specs—because the variant of using exactly 29.97 fps has zero 
     timecode drift.
   </dd>
   <dt><kbd class="menu">LTC incoming port</kbd></dt>
@@ -101,4 +101,3 @@
 </dl>
 <p>These settings are also common to all sessions.</p>
 
-