Copy edits to session pages

diff --git a/_manual/07_working-with-sessions/04_session-templates.html b/_manual/07_working-with-sessions/04_session-templates.html
index e9582d440640551a21d371f1f3907e22ddc05d70..9aa6dde55f91b7abccedffb41d1122ec87cf543f 100644 (file)
--- a/_manual/07_working-with-sessions/04_session-templates.html
+++ b/_manual/07_working-with-sessions/04_session-templates.html
@@ -6,7 +6,7 @@ title: Session Templates
 
   
   
-<p>Session templates are a way to store the setup of a session for future (re)use. They do not store any <em>data</em> but do store (for example):</p>
+<p>Session templates are a way to store the setup of a session for future use. They do not store any <em>audio</em> data but can store:</p>
 <ul>
 <li>The number of tracks and busses, along with their names
 </li>
@@ -16,7 +16,7 @@ title: Session Templates
 </li>
 </ul>
 <h3>Creating a Session Template</h3>
-<p>Choose <code>Session &gt; Save Template</code>. A dialog will appear to ask you for the name of the new template.</p>
+<p>Choose <code>Session &gt; Save Template</code>. A dialog will ask you for the name of the new template.</p>
 <h3>Using a Session Template</h3>
 <p>In the New Session dialog, choose the desired template from the combo selector.</p>
 <p>Note that you can also use an existing session as a template, without saving it as one. This is available as an option in the New Session dialog. Doing this will not alter the existing session at all, but will use its track, bus and plugin configuration just like a template.</p>

diff --git a/_manual/07_working-with-sessions/05_snapshots.html b/_manual/07_working-with-sessions/05_snapshots.html
index efbc3fd46b4c52d194ad6de422e78ac457107a55..7cd807f73393e02356dcef9f22438bf0abc5a8de 100644 (file)
--- a/_manual/07_working-with-sessions/05_snapshots.html
+++ b/_manual/07_working-with-sessions/05_snapshots.html
@@ -10,10 +10,13 @@ title: Snapshots
 <p>This is easily accomplished using <code>Session &gt; Snapshot</code>. A small dialog will appear allowing you to enter a name for the snapshot. The default name is based on the current date and time.</p>
 <p>Creating a snapshot does <strong>not</strong> modify your session, nor does it save your session. Instead, it saves an "alternate" version of the session, within the session folder. The snapshot shares all data present in the session. You can create any number of snapshots. </p>
 <p>After creating a snapshot, you can continue working on the session and save it normally using <code>Session &gt; Save</code> and any existing snapshots will remain unchanged. </p>
+
 <h3>Switching to a Snapshot</h3>
-<p>If you are already working on a session and want to to switch to an existing snapshot, navigate the Snapshots tab of the <a href="/ardours-interface/introducing-the-editor-window/editor-lists">Editor Lists</a>. Find the name of the snapshot in the list and click it. Ardour will switch to the snapshot. If the session has not been saved, you will asked what you want to do.</p>
-<h3>Starting Ardour With A Snapshot</h3>
+<p>If you are already working on a session and want to to switch to an existing snapshot, navigate the Snapshots tab of the <a href="/ardours-interface/introducing-the-editor-window/editor-lists">Editor Lists</a>. Find the name of the snapshot in the list and click it. Ardour will switch to the snapshot. If the session has not been saved, Ardour will ask what you want to do.</p>
+
+<h3>Starting Ardour With a Snapshot</h3>
 <p>Since a snapshot is just another session file stored within the session folder, you can specify that "version" when loading an existing session. The browser in the "Open Session" dialog will show an expander arrow for sessions that have more than 1 session file (i.e. snapshots) present - click on it to see the list, and then click on the name of the snapshot you want to load.</p>
-<h3>Saving And Switching to a Snapshot</h3>
+
+<h3>Saving and Switching to a Snapshot</h3>
 <p>Sometimes you want to create a snapshot and then have all future edits and modifications saved to that snapshot rather than the main session. This is easily done using <code>Session &gt; Save As</code>. This does not create a new session folder,  but saves your session as a new snapshot and then switches the "current snapshot" to the newly created one. All subsequent saves of the session will be stored in this new snapshot, and existing snapshots (and the main session) will be left unaffected. </p>