X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Flatency-considerations.html;h=7dd06ee60b27b77c9f02eaec56f866f69c1ee350;hb=9b9f871806fd9066acd0e7cf415a8423abe43c8f;hp=a18846f1b1d30593edba9287b0ecfdc9dd845585;hpb=2098e011e638b5c86c56e68df7757975fc4d728f;p=ardour-manual

diff --git a/include/latency-considerations.html b/include/latency-considerations.html
index a18846f..7dd06ee 100644
--- a/include/latency-considerations.html
+++ b/include/latency-considerations.html
@@ -19,7 +19,7 @@
   2 ms are already used in the A/D/A process, you must use extremely low 
   <dfn>buffer sizes</dfn> in your workstation <abbr title="Input/Output">I/O</abbr> 
   setup to keep the overall latency below 5ms. Not all 
-  <a href="/setting-up-your-system/the-right-computer-system-for-digital-audio/">computer audio systems</a> 
+  <a href="@@the-right-computer-system-for-digital-audio">computer audio systems</a> 
   are able to work reliably at such low buffer sizes.
 </p>
 <p>
@@ -27,11 +27,9 @@
   through an external mixing console while recording, an approach taken by
   most if not all professional recording studios. Many computer I/O devices 
   have a hardware mixer built in which can route the monitor signal "around"
-  the computer, avoiding the systemlatency.<br />
+  the computer, avoiding the systemlatency.<br>
   In either case, the monitoring hardware may be digital or analog.  And in 
   the digital case you will still have the A-D-A conversion latency of
   1&ndash;2&nbsp;ms.
 </p>
 
-{% children %}
-