more tweaks to the Sync manual

[ardour-manual] / _manual / 19_synchronization / 01_on-clock-and-time.html

diff --git a/_manual/19_synchronization/01_on-clock-and-time.html b/_manual/19_synchronization/01_on-clock-and-time.html
index a87682445b8279f09f11e091e77cb594a78ae191..64ed04b94c42e2f4203c8e814adc4921f2bac3c7 100644 (file)
--- a/_manual/19_synchronization/01_on-clock-and-time.html
+++ b/_manual/19_synchronization/01_on-clock-and-time.html
@@ -9,15 +9,15 @@ Synchronisation in multimedia involves two concepts which are often confused: <s
 
 <p>
 A <em>clock</em> is the mechanism by which two systems <em>tick</em> simultaneously.
-In the audio world this is generally referred to as <a href="http://en.wikipedia.org/wiki/Word_clock" title="http://en.wikipedia.org/wiki/Word_clock">Word_clock</a>.
+In the audio world this is generally referred to as <a href="http://en.wikipedia.org/wiki/Word_clock" title="http://en.wikipedia.org/wiki/Word_clock">Word Clock</a>.
 It does not carry any absolute reference to a point in time: A clock is used to keep a systems sample rate constant, regular and accurate.
-Word clock is usually at the frequency of the sample-rate - ie at 48KHz, its period is about 20μs. Word Clock is the most common &#039;sample rate&#039; based clock but other clocks do exist such as Black and Burst, Tri-Level and DARS. Sample rates can also be derived from these clocks as well.
+Word clock is usually at the frequency of the sample rate - ie at 48KHz, its period is about 20μs. Word Clock is the most common &#039;sample rate&#039; based clock but other clocks do exist such as Black and Burst, Tri-Level and DARS. Sample rates can also be derived from these clocks as well.
 </p>
 
 <p>
-Time – or <em>timecode</em> – on the other hand specifies an absolute relationship or position on a timeline e.g. <code>01:02:03:04</code> (expressed as Hours:Mins:Secs:Frames). It is actual data and not a clock-signal per se.
-The granularity of timecode is <strong>Video Frames</strong> and is an order of magnitude lower than, say, Word Clock which is counted in <strong>samples</strong>. A typical frame-rate is 25 fps with a period of 40ms.
-In the case of 48kHz and 25fps, there are 1920 samples per video frame.
+Time – or <em>timecode</em> – on the other hand specifies an absolute relationship or position on a timeline e.g. <code>01:02:03:04</code> (expressed as Hours:Mins:Secs:Frames). It is actual <em>data</em> and not a clock <em>signal</em> per se.
+The granularity of timecode is <strong>Video Frames</strong> and is an order of magnitude lower than, say, Word Clock which is counted in <strong>samples</strong>. A typical frame rate is 25 fps with a period of 40ms.
+In the case of 48KHz and 25fps, there are 1920 audio samples per video frame.
 </p>
 
 <p>
@@ -25,7 +25,7 @@ The concept of clock and timecode is reflected in JACK and Ardour:
 </p>
 
 <p>
-JACK provides clock-synchronization and is not concerned with time-code (this is not entirely true, more on jack-transport later).
+JACK provides clock synchronization and is not concerned with time code (this is not entirely true, more on jack-transport later).
 Within software, jackd provides sample-accurate synchronization between all JACK applications.
 On the hardware side JACK uses the clock of the audio-interface. Synchronization of multiple interfaces requires hardware support to sync the clocks.
 If two interfaces run at different clocks the only way to align the signals is via re-sampling (SRC - Sample Rate Conversion) - which decreases fidelity.