From: Robin Gareus <robin@gareus.org>
Date: Fri, 15 Feb 2013 22:20:27 +0000 (+0100)
Subject: fix headline capitalization
X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c8c2a5efaecf4bda0fe18e0758697e6af345fa6f;p=ardour-manual

fix headline capitalization
---

diff --git a/_manual/19_synchronization/01_on-clock-and-time.html b/_manual/19_synchronization/01_on-clock-and-time.html
index cf484ad..9a5bbae 100644
--- a/_manual/19_synchronization/01_on-clock-and-time.html
+++ b/_manual/19_synchronization/01_on-clock-and-time.html
@@ -3,8 +3,6 @@ layout: default
 title: On Clock and Time
 ---
 
-<h2>On Clock and Time</h2>
-
 <p>
 Synchronisation in multimedia involves two concepts which are often confused: <strong>clock</strong> (or speed) and <strong>time</strong> (location in time).
 </p>
diff --git a/_manual/19_synchronization/02_latency-and-latency-compensation.html b/_manual/19_synchronization/02_latency-and-latency-compensation.html
index a014d43..1aa7859 100644
--- a/_manual/19_synchronization/02_latency-and-latency-compensation.html
+++ b/_manual/19_synchronization/02_latency-and-latency-compensation.html
@@ -100,7 +100,7 @@ NB. this is also one of the reasons why many projects start at timecode <code>01
 </p>
 
 
-<h2>Latency compensation and clock sync</h2>
+<h2>Latency Compensation And Clock Sync</h2>
 
 <p>
 To achieve sample accurate timecode synchronization, the latency introduced by the audio-setup needs to be known and compensated for.
@@ -126,7 +126,7 @@ JACK includes an <acronym title="Application Programming Interface">API</acronym
 </p>
 
 
-<h2>Calibrating JACK latency</h2>
+<h2>Calibrating JACK Latency</h2>
 
 <p>
 Linux DSP guru Fons Adriaensen wrote a tool called <code>jack_delay</code> to accurately measure the roundtrip latency of a closed loop audio chain, with sub-sample accuracy. JACK itself includes a variant of this called <code>jack_iodelay</code>.
diff --git a/_manual/19_synchronization/03_timecode-generators-and-slaves.html b/_manual/19_synchronization/03_timecode-generators-and-slaves.html
index c2cdbe2..362ad2d 100644
--- a/_manual/19_synchronization/03_timecode-generators-and-slaves.html
+++ b/_manual/19_synchronization/03_timecode-generators-and-slaves.html
@@ -64,7 +64,7 @@ In <code>session &gt; properties</code> it is possible to define an offset betwe
 
 
 
-<h3>MTC generator</h3>
+<h3>MTC Generator</h3>
 
 <p>
 There are no options. Ardour sends full MTC frames whenever the transport is relocated or changes state (start/stop). MTC quarter frames are sent when the transport is rolling and the transport speed is within 93% and 107%.
@@ -72,7 +72,7 @@ There are no options. Ardour sends full MTC frames whenever the transport is rel
 
 
 
-<h3>LTC generator</h3>
+<h3>LTC Generator</h3>
 
 <p>
 The volume of the LTC signal can be conigured in in the <code>Preferences &gt; Transport</code> dialog. By default it is set to -18dBFS which corresponds to 0dBu in an EBU calibrated system.
@@ -215,7 +215,7 @@ A global offset between incoming timecode and ardour&#039;s transport can be con
 
 
 
-<h3>JACK transport</h3>
+<h3>JACK Transport</h3>
 
 <p>
 When slaved to jack, Ardour&#039;s transport will be identical to JACK-transport. As opposed to other slaves, Ardour can be used to control the JACK transport states (stopped/rolling). No port-connections need to be made for jack-transport to work.