X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=_manual%2F19_synchronization%2F01_on-clock-and-time.html;h=e0bf469912f6d7c6d8441660d3066f0dc0d9c50c;hb=7a02ccdce1f9599b9ea5b1a08f53f913474eec25;hp=cf484addf9b859e4103d73516d09586032b4a160;hpb=e7b78767392c9f7d705799ff94724dd6d2a21a71;p=ardour-manual

diff --git a/_manual/19_synchronization/01_on-clock-and-time.html b/_manual/19_synchronization/01_on-clock-and-time.html
index cf484ad..e0bf469 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>
@@ -33,7 +31,7 @@ The concept of clock and timecode is reflected in JACK and Ardour:
 <p>
 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 harware side JACK uses the clock of the audio-interface. Synchronization of multiple interfaces requires hardware support to sync the clocks.
+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.
 </p>