Updating *Starting Ardour*

diff --git a/_manual/04_ardours-interface/01_starting-ardour.html b/_manual/04_ardours-interface/01_starting-ardour.html
index e610c2c5771414afa55bd297483dd5286cddf611..3beb5edfcd4b7a2ba71cb9fb03e61a3a6ba89983 100644 (file)
--- a/_manual/04_ardours-interface/01_starting-ardour.html
+++ b/_manual/04_ardours-interface/01_starting-ardour.html
@@ -22,19 +22,15 @@ title: Starting Ardour
   <kbd class="menu">Edit &gt; Preferences</kbd> dialog.
 </p>
 <p>
-  In general, it is sensible to start JACK before you run Ardour. This is not
-  necessary, but will provide you with more control and options over JACK's
-  operation.
+  If you want to use JACK, in general, it is sensible to start it <em>before</em> you run Ardour. This is not
+  necessary, but will provide you with more control and options over JACK's operation.
+  You can start JACK through its <abbr title="Command Line Interface">CLI</abbr>, or using a <abbr title="Graphical User Interface">GUI</abbr>
+  program, like <a href="https://qjackctl.sourceforge.io/">QjackCtl</a> or <a href="http://kxstudio.linuxaudio.org/Applications:Cadence">Cadence</a>.
 </p>
 <p>
   If you open Ardour without specifying an existing session it will display 
-  the <kbd class="menu">Session &gt; New...</kbd> dialog. If JACK is not already
-  running, there will be an extra <kbd class="menu">Audio Engine</kbd> tab in
-  that dialog to configure JACK, which Ardour will then start automatically.
-</p>
-<p>
-  If you did specify an existing session but JACK is not already running, the
-  <kbd class="menu">New Session</kbd> dialog will contain just the Audio Engine tab. 
+  the <kbd class="menu">Session &gt; New...</kbd> dialog and the <kbd class="menu">Audio/MIDI Setup</kbd> dialog.
+  See <a href="/working-with-sessions/new-session-dialog/">New/Open Session Dialog</a> for a description of those dialogs. 
 </p>
   
 

diff --git a/_manual/04_ardours-interface/01_starting-ardour/01_starting-ardour-from-the-command-line.html b/_manual/04_ardours-interface/01_starting-ardour/01_starting-ardour-from-the-command-line.html
index eb186206607850e1d48eaa46483bb3d1415ce039..b8d5d56a1b379ccac09750d2f7251b619a9cb66e 100644 (file)
--- a/_manual/04_ardours-interface/01_starting-ardour/01_starting-ardour-from-the-command-line.html
+++ b/_manual/04_ardours-interface/01_starting-ardour/01_starting-ardour-from-the-command-line.html
@@ -4,17 +4,15 @@ title: Starting Ardour From the Command Line (Linux)
 menu_title: Starting from Linux Cmdline
 ---                        
 
-
-  
 <p>
   Like (almost) any other program on Linux, Ardour can be started on the
   command line. Type the following command in a terminal window:
 </p>
-<kbd class="cmd lin">ardour3</kbd>
+<kbd class="cmd lin">Ardour5</kbd>
 <p>
   To start Ardour with an existing session:
 </p>
-<kbd class="cmd lin">ardour3 <em>/path/to/session</em></kbd>
+<kbd class="cmd lin">Ardour5 <em>/path/to/session</em></kbd>
 <p>
   replacing /path/to/session with the actual path to your session. You can
   specify either the session folder or any session file inside the folder,
@@ -23,6 +21,6 @@ menu_title: Starting from Linux Cmdline
 <p>
   To start Ardour with a new, named session:
 </p>
-<kbd class="cmd lin">ardour3 -N <em>/path/to/session</em></kbd>
+<kbd class="cmd lin">Ardour5 -N <em>/path/to/session</em></kbd>
 
 <h3>Other Command Line Options</h3>

diff --git a/_manual/10_working-with-tracks/02_busses-and-vcas.html b/_manual/10_working-with-tracks/02_busses-and-vcas.html
index 0c27d58cf63753d5d27a4cd824f6fb59288688db..8bd23707771c304df424f61f2ca81aebb9a62fcc 100644 (file)
--- a/_manual/10_working-with-tracks/02_busses-and-vcas.html
+++ b/_manual/10_working-with-tracks/02_busses-and-vcas.html
@@ -4,7 +4,7 @@ title: Busses and VCAs
 ---                        
 
 <p>
-  In order to use the process of mixing, Ardour offers two tools traditionally found on hardware mixing consoles : <dfn>Busses</dfn> and <dfn><abbr title="Voltage-Controlled Amplifier">VCA</abbr></dfn>s.
+  In order to ease the process of mixing, Ardour offers two tools traditionally found on hardware mixing consoles : <dfn>Busses</dfn> and <dfn><abbr title="Voltage-Controlled Amplifier">VCA</abbr></dfn>s.
 </p>
 
 <h2>Busses</h2>
@@ -30,7 +30,7 @@ title: Busses and VCAs
 </p>
 
 <p>
-  MIDI bus are provide a particularly efficient workflow for virtual drumkits where the arrangement uses different MIDI tracks. Moreover, busses with both Audio and MIDI inputs are well suited for vocoders and similar plugins.
+  MIDI busses provide a particularly efficient workflow for virtual drumkits where the arrangement uses different MIDI tracks. Moreover, busses with both Audio and MIDI inputs are well suited for vocoders and similar plugins.
 </p>
 
 <p>
@@ -46,7 +46,7 @@ title: Busses and VCAs
 </p>
 
 <p>
-       Obviously, doing so will (by default) disconnect the output from the Master's input, which means all the        audio/MIDI will be routed to the bus. For more complex routing, the OUTPUT button allows to show the <kbd class="menu">Routing Grid</kbd> that allows to plug the output of the track to multiple outputs at once, be   it busses, tracks, Master... The button will then reflect these multiple connections by showing a <em>*number*</em>, number being the number of connections made in the routing grid.
+       Obviously, doing so will (by default) disconnect the output from the Master's input, which means all the audio/MIDI will be routed to the bus. For more complex routing, the OUTPUT button allows to show the <kbd class="menu">Routing Grid</kbd> that allows to plug the output of the track to multiple outputs at once, be it busses, tracks, Master... The button will then reflect these multiple connections by showing a <em>*number*</em>, number being the number of connections made in the routing grid.
 </p>
 
 <h3>Connecting a track to a bus via Sends</h3>