fix some typos

diff --git a/_manual/19_synchronization/01_on-clock-and-time.html b/_manual/19_synchronization/01_on-clock-and-time.html
index 9a5bbae96b03023973caddfd10816d56283e7546..e0bf469912f6d7c6d8441660d3066f0dc0d9c50c 100644 (file)
--- a/_manual/19_synchronization/01_on-clock-and-time.html
+++ b/_manual/19_synchronization/01_on-clock-and-time.html
@@ -31,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>
 

diff --git a/_manual/19_synchronization/02_latency-and-latency-compensation.html b/_manual/19_synchronization/02_latency-and-latency-compensation.html
index 1aa78592db41c4873954c7b3c18110a1e664b7fa..4e049d084e89cff28d742b980e57183f621fbcb5 100644 (file)
--- a/_manual/19_synchronization/02_latency-and-latency-compensation.html
+++ b/_manual/19_synchronization/02_latency-and-latency-compensation.html
@@ -61,7 +61,7 @@ Low-latency is not always a feature you want to have. It comes with a couple of
 </p>
 
 <p>
-Reliable low-latency (≤10ms) on GNU/Linux can usually only be achieved by running <a href="https://rt.wiki.kernel.org/" title="https://rt.wiki.kernel.org/">realtime-kernel</a>.
+Reliable low-latency (≤10ms) on GNU/Linux can usually only be achieved by running a <a href="https://rt.wiki.kernel.org/" title="https://rt.wiki.kernel.org/">realtime-kernel</a>.
 </p>
 
 <p>