diff --git a/content/mixing-sessions/_index.en.md b/content/mixing-sessions/_index.en.md
index 34be7c0..212a779 100644
--- a/content/mixing-sessions/_index.en.md
+++ b/content/mixing-sessions/_index.en.md
@@ -1,5 +1,6 @@
 +++
 title = "Mixing sessions"
+description = "How to mix a session in Ardour"
 chapter = true
 weight = 5
 pre = "<b>5. </b>"
diff --git a/content/mixing-sessions/dynamics/index.en.md b/content/mixing-sessions/dynamics/index.en.md
index bfa046b..6ee9c82 100644
--- a/content/mixing-sessions/dynamics/index.en.md
+++ b/content/mixing-sessions/dynamics/index.en.md
@@ -1,5 +1,6 @@
 +++
 title = "Dynamics"
+description = "Applying limiters, compressors, and a gate in Ardour"
 chapter = false
 weight = 6
 +++
@@ -31,7 +32,7 @@ slider. The _Fast Lookahead Limiter_ literally looks ahead in the signal by a
 few milliseconds, and when it sees that the signal is about to go over the limit
 you have set, it automatically turns the levels down.
 
-![limiter](en/ardour7-fast-lookahead-lmiter.png)
+{{< figure alt="limiter" src="en/ardour7-fast-lookahead-lmiter.png" >}}
 
 The _Input Gain (dB)_ slider determines how much the levels are increased before
 they reach the limiter, and the _Attenuation (dB)_ meter on the right-hand side
@@ -64,7 +65,7 @@ A typical compressor will have these obligatory controls:
 **Attack** and **Release**
 : Control how quickly the compressor affects the sound.
 
-![ACE Compressor](en/ardour7-ace-compressor.png)
+{{< figure alt="ACE Compressor" src="en/ardour7-ace-compressor.png" >}}
 
 The _ACE Compressor_ plugin on the screenshot above has two additional controls:
 
@@ -92,7 +93,7 @@ dynamics between the beginning and end of the drum hit similar.
 Below is a screenshot of a similar compressor from the [LSP plugins
 suite](https://lsp-plug.in/):
 
-![LSP Compressor Mono](en/ardour7-lsp-compressor-mono.png)
+{{< figure alt="LSP Compressor Mono" src="en/ardour7-lsp-compressor-mono.png" >}}
 
 If you want to speed up learning how to use a compressor, a generally good idea
 is to insert one scope visualization plugin before the compressor and one right
@@ -114,14 +115,14 @@ Here, the _Hard Gate_ plugin (from a suite of LADSPA plugins called
 parameter, the _Threshold_ at which the gate will open and let the signal
 through.
 
-![Hard Gate](en/ardour7-hard-gate.png)
+{{< figure alt="Hard Gate" src="en/ardour7-hard-gate.png" >}}
 
 Other kinds of gates, such as the _LSP Gate_ plugin on the screenshot below, are
 more complex. They have independent control over how quickly the gate opens
 (_Attack_) and closes (_Release_), as well as other parameters quite similar to
 those described for the SC Compressor above.
 
-![LSP Gate](en/ardour7-lsp-gate-mono.png)
+{{< figure alt="LSP Gate" src="en/ardour7-lsp-gate-mono.png" >}}
 
 ## Continuing
 
diff --git a/content/mixing-sessions/equalizing/index.en.md b/content/mixing-sessions/equalizing/index.en.md
index bdc217d..f1bc303 100644
--- a/content/mixing-sessions/equalizing/index.en.md
+++ b/content/mixing-sessions/equalizing/index.en.md
@@ -1,5 +1,6 @@
 +++
 title = "Equalizing"
+description = "Applying equalization to audio in Ardour"
 chapter = false
 weight = 7
 +++
@@ -26,7 +27,7 @@ the screenshot below is just such an EQ. If you don't have this particular
 plugin on your computer, explore the ones you have that have "EQ" in the name;
 you will likely find something similar.
 
-![DJ EQ](en/ardour7-dj-eq.png)
+{{< figure alt="DJ EQ" src="en/ardour7-dj-eq.png" >}}
 
 ## Multi-Band (or Graphic) Equalizer
 
@@ -37,7 +38,7 @@ Equalizer_ plugin shown below, the center frequency of each band can be defined
 by the user. This allows you to either attenuate (or remove) an unwanted
 frequency, or to reinforce (boost) a desired one.
 
-![tap eq](en/ardour7-lsp-graphic-16-band-eq.png)
+{{< figure alt="tap eq" src="en/ardour7-lsp-graphic-16-band-eq.png" >}}
 
 The overall "curve" of the bands can also be used to determine the general tone
 of your track or mix. In the example above, the lower part of the mid-range
@@ -51,14 +52,14 @@ The _parametric equalizer_ is the most versatile type of EQ used for mixing
 because of its extensive control over all types of EQ parameters. Ardour ships
 with a parametric equalizer plug-in called the _ACE EQ_. It looks like this:
 
-![a-eq](en/ardour7-ace-eq.png)
+{{< figure alt="a-eq" src="en/ardour7-ace-eq.png" >}}
 
 Others may have shinier graphical interfaces like the _x42 EQ_ by Robin Gareus,
 but they all essentially do the exact same thing. You may have EQ plugins on
 your computer that look a bit different than these screenshots, but the
 parameters you can control are likely very similar.
 
-![x42 eq](en/ardour7-x42-eq.png)
+{{< figure alt="x42 eq" src="en/ardour7-x42-eq.png" >}}
 
 In both screenshots above (_a-EQ_ and _x42 EQ_), there are options you can
 adjust for each frequency band. Each of the three bands has a _level_ (dB)
diff --git a/content/mixing-sessions/mixing-levels/index.en.md b/content/mixing-sessions/mixing-levels/index.en.md
index 4ba0639..8d76b68 100644
--- a/content/mixing-sessions/mixing-levels/index.en.md
+++ b/content/mixing-sessions/mixing-levels/index.en.md
@@ -26,7 +26,7 @@ not changed. In the screenshot below, the fader for the track named "kick" is
 set to -0.0, and the peak meter indicates that the highest peak so far was
 -5.1dB.
 
-![levels1](en/Ardour4_Mixing_Levels_1.png) 
+{{< figure alt="levels1" src="en/Ardour4_Mixing_Levels_1.png" >}} 
 
 ## Avoiding Clipping
 
@@ -38,7 +38,7 @@ In the screenshot below, the synth track has just clipped to +5.9. You can also
 see little red edges on the waveform itself, indicating the exact locations
 where the recorded sound clipped. 
 
-![levels2](en/Ardour4_Mixing_Levels_2.png)
+{{< figure alt="levels2" src="en/Ardour4_Mixing_Levels_2.png" >}}
 
 Click on the red number in the peak meter to reset it.
 
diff --git a/content/mixing-sessions/panning/index.en.md b/content/mixing-sessions/panning/index.en.md
index e33c26c..b04296f 100644
--- a/content/mixing-sessions/panning/index.en.md
+++ b/content/mixing-sessions/panning/index.en.md
@@ -1,5 +1,6 @@
 +++
 title = "Panning"
+description = "How to pan signal in Ardour"
 chapter = false
 weight = 3
 +++
diff --git a/content/mixing-sessions/the-mixer-strip/index.en.md b/content/mixing-sessions/the-mixer-strip/index.en.md
index 4258cea..fca08d0 100644
--- a/content/mixing-sessions/the-mixer-strip/index.en.md
+++ b/content/mixing-sessions/the-mixer-strip/index.en.md
@@ -1,5 +1,6 @@
 +++
 title = "The mixer strip"
+description = "Elements of the mixer strip in Ardour"
 chapter = false
 weight = 1
 +++
@@ -41,7 +42,7 @@ display the Editor's mixer strip.
 Here we see the entire mixer strip, as it would appear in either the _Editor_
 window or the _Mixer_ window. 
 
-![strip1](en/Ardour4_Mixer_Strip_1.png) 
+{{< figure alt="strip1" src="en/Ardour4_Mixer_Strip_1.png" >}} 
 
 ### Regular & Narrow Modes
 
@@ -50,7 +51,7 @@ width to conserve space. The very top part of the mixer strip, pictured below,
 switches between regular and narrow modes using the left button. The button with
 an eye icon hides the mixer strip entirely (you can re-enable it later).
  
-![strip top](en/ardour7-narrow-wide-strip.png)
+{{< figure alt="strip top" src="en/ardour7-narrow-wide-strip.png" >}}
 
 You can easily spot differences between narrow and regular modes: shorter
 captions on buttons, no legend for the peak meter etc.
@@ -65,7 +66,7 @@ see the _Understanding Routing_ and _Recording Audio_ chapters for more
 information on input routing. The last narrow region controls phase reversing
 (we won't go into details on this topic in this tutorial). 
 
-![strip 2](en/Ardour4_Mixer_Strip_2.png) 
+{{< figure alt="strip 2" src="en/Ardour4_Mixer_Strip_2.png" >}} 
 
 ### Processor Box 
 
@@ -168,7 +169,7 @@ mono track, and two bar graphs in case of a stereo track. The small rectangular
 field above the meters shows the highest peak value that has been played on that
 track so far.
 
-![strip 7](en/Ardour4_Mixer_Strip_5.png) 
+{{< figure alt="strip 7" src="en/Ardour4_Mixer_Strip_5.png" >}} 
 
 By clicking the right-hand button at the bottom of the mixer strip (it reads
 "post" in the image above), you will be able to select the _metering point_, for
@@ -180,7 +181,7 @@ in each track, called the _track mixer_, which contains a horizontal fader, a
 vertical peak meter, as well as miniature buttons for arm record, mute, and
 solo. They all mirror those found in the mixer strip for that track.
 
-![strip 6](en/Ardour4_Mixer_Strip_6.png) 
+{{< figure alt="strip 6" src="en/Ardour4_Mixer_Strip_6.png" >}} 
 
 Please refer to the chapter on _Mixing Levels_ for more detailed instruction
 about using the fader and peak meters.
diff --git a/content/mixing-sessions/using-automation/index.en.md b/content/mixing-sessions/using-automation/index.en.md
index e1540ab..6f9141c 100644
--- a/content/mixing-sessions/using-automation/index.en.md
+++ b/content/mixing-sessions/using-automation/index.en.md
@@ -1,5 +1,6 @@
 +++
 title = "Using automation"
+description = "How to create and edit automation in Ardour"
 chapter = false
 weight = 8
 +++
@@ -23,7 +24,7 @@ track_. Automation data is visually represented as an _automation line_, made
 up of a number of _automation points_. Here's how a track with automation
 looks like:
 
-![Typical automation lane](en/Ardour4_Automation_Fader_1.png)
+{{< figure alt="Typical automation lane" src="en/Ardour4_Automation_Fader_1.png" >}}
 
 In the image above, the automation lane called _Fader_ is associated to the
 parent track called _Audio 1_. The automation line controls fader (volume)
@@ -35,25 +36,25 @@ Let's create a simple fader automation. Click the **A** button of a chosen
 track. A menu will appear, where you can select the parameter you would like to
 automate. Choose _Fader_.
 
-![Choose Fader](en/Ardour4_Automation_Button.png)
+{{< figure alt="Choose Fader" src="en/Ardour4_Automation_Button.png" >}}
 
 An automation lane will then appear. Select the _Draw_ mode (**D** shortcut):
 
-![Draw mode](en/Ardour4_EditModes_D.png)
+{{< figure alt="Draw mode" src="en/Ardour4_EditModes_D.png" >}}
 
 Now you can create automation points by clicking anywhere in the automation
 lane. An automation line joins the automation points you add. The yellow number
 (-15.3dB in the image below) indicates the gain level for the selected
 automation point.
 
-![Automation point value indication](en/Ardour4_Automation_Fader_2.png)
+{{< figure alt="Automation point value indication" src="en/Ardour4_Automation_Fader_2.png" >}}
 
 ### Automation States
 
 The automation curve will not play, however, until you set the automation state
 to _Play_.
 
-![automation state](en/Ardour4_Automation_Fader_3.png)
+{{< figure alt="automation state" src="en/Ardour4_Automation_Fader_3.png" >}}
 
 **Manual**
 : When set to _Manual_, the track will ignore any automation data. It will just
@@ -87,13 +88,13 @@ curves by hand.
 You may add automation to any plugin which has already been added to a track. In
 the example below, we have the _AM pitchshifter_ plugin added to a track.
 
-![pluginautomation1](en/Ardour4_Automation_Plugin1.png)
+{{< figure alt="pluginautomation1" src="en/Ardour4_Automation_Plugin1.png" >}}
 
 In order to select a plugin parameter for automation, click the button on the
 track marked _a_. The menu will appear. Under _Processor Automation_ you will
 find a listing of the plugins you have added for that track.
 
-![pluginautomation2](en/Ardour4_Automation_Plugin2.png)
+{{< figure alt="pluginautomation2" src="en/Ardour4_Automation_Plugin2.png" >}}
 
 Within each listed plugin, you may choose which parameter you want to automate
 from a list. In the example, we chose the _Pitch shift_ parameter of the _AM
@@ -104,7 +105,7 @@ below the main parent track.
 Draw an automation curve for that parameter. Don't forget to set the automation
 state to _Play_.
 
-![pluginautomation3](en/Ardour4_Automation_Plugin3.png)
+{{< figure alt="pluginautomation3" src="en/Ardour4_Automation_Plugin3.png" >}}
 
 In the image above, the pitch shift of the sound is now changing over time,
 controlled by the curve.
@@ -124,7 +125,7 @@ the height of the automation lane. Notice that the parent track and the
 automation lane heights are independent, so while working in your automation
 curves you might set them up like this:
 
-![pluginautomation5](en/Ardour4_Automation_Plugin4.png)
+{{< figure alt="pluginautomation5" src="en/Ardour4_Automation_Plugin4.png" >}}
 
 {{% notice tip %}}
 Remember that you can also zoom in and out to increase resolution in the
@@ -153,7 +154,7 @@ background around the points. Then the selected points may be deleted by hitting
 After an automation curve ends, its value will stay at that level for all
 subsequent regions, whether or not you have drawn a continuation of the curve.
 
-![end point](en/Ardour4_Automation_Fader_End.png)
+{{< figure alt="end point" src="en/Ardour4_Automation_Fader_End.png" >}}
 
 In the example above, the last point of the curve is at -23dB. That same level
 will be kept for the remainder of the track, even though the line is not drawn
@@ -166,11 +167,11 @@ that might be aligned with it, as we can see in the following screen shots.
 
 Before moving:
 
-![mv1](en/Ardour4_Automation_Moving_1.png)
+{{< figure alt="mv1" src="en/Ardour4_Automation_Moving_1.png" >}}
 
 After moving:
 
-![mv2](en/Ardour4_Automation_Moving_2.png)
+{{< figure alt="mv2" src="en/Ardour4_Automation_Moving_2.png" >}}
 
 You can change this behavior if you like. In other words, if you want automation
 curves to stay where they are even when you move regions around, go to `Edit >
@@ -183,14 +184,14 @@ There is a way to create a gain automation directly bound to a region. When you
 select the _Draw_ mode, you should see a flat line on the top half of each
 region rectangle:
 
-![gain-automation](en/Ardour4_Automation_Region_Specific_1.png)
+{{< figure alt="gain-automation" src="en/Ardour4_Automation_Region_Specific_1.png" >}}
 
 Click directly on that line to create automation points. These will be drawn
 directly on the region itself, unlike fader automation which is drawn or
 recorded in the automation lane. Region gain automation is separate from, and
 in addition to, fader automation.
 
-![gain-automation2](en/Ardour4_Automation_Region_Specific_2.png)
+{{< figure alt="gain-automation2" src="en/Ardour4_Automation_Region_Specific_2.png" >}}
 
 As with the automation lanes, a _gain automation point_ can be dragged in any
 direction with the mouse. To remove a gain automation point, hold down the
@@ -201,7 +202,7 @@ direction with the mouse. To remove a gain automation point, hold down the
 Gain automation can be reset or deactivated from the region context menu, which
 is reached by right-clicking on the region.
 
-![gain-automation3](en/Ardour4_Automation_Gain_Tool_Reset.png)
+{{< figure alt="gain-automation3" src="en/Ardour4_Automation_Gain_Tool_Reset.png" >}}
 
 Here, the gain automation is referred to as the _envelope_:
 
@@ -218,13 +219,13 @@ in which one is more convenient than the other. Here are two examples:
 portion of a region, and you are otherwise happy with the level for the rest of
 the passage or entire track, use the region-specific automation.
 
-![gain-example1](en/Ardour4_Automation_Region_Specific_2.png)
+{{< figure alt="gain-example1" src="en/Ardour4_Automation_Region_Specific_2.png" >}}
 
 * If you have a more complex track with crossfades over regions, and/or need to
 shape a longer dynamic curve across several regions on the same track, use fader
 automation.
 
-![gain-automation2](en/Ardour4_Automation_Gain_Comparison.png)
+{{< figure alt="gain-automation2" src="en/Ardour4_Automation_Gain_Comparison.png" >}}
 
 The screenshot above shows a simple gradual fade starting from the first region
 in the track, and ending at the last region. It's very straightforward to do
diff --git a/content/mixing-sessions/using-plugins/index.en.md b/content/mixing-sessions/using-plugins/index.en.md
index c683cf6..4f1ba89 100644
--- a/content/mixing-sessions/using-plugins/index.en.md
+++ b/content/mixing-sessions/using-plugins/index.en.md
@@ -1,5 +1,6 @@
 +++
 title = "Using plugins"
+description = "How to use plugins in Ardour"
 chapter = false
 weight = 4
 +++
diff --git a/content/mixing-sessions/using-sends/index.en.md b/content/mixing-sessions/using-sends/index.en.md
index d059d4e..89ef2f2 100644
--- a/content/mixing-sessions/using-sends/index.en.md
+++ b/content/mixing-sessions/using-sends/index.en.md
@@ -1,5 +1,6 @@
 +++
 title = "Using sends"
+description = "Using sends in Ardour"
 chapter = false
 weight = 5
 +++
@@ -25,19 +26,19 @@ the amount of work. Every time you want to change a reverb setting across the
 board for all drums, you'd have to open all four reverb plugins and change
 them in the same way.
 
-*This is where sends come in handy: you can use them to add a particular
+This is where sends come in handy: you can use them to add a particular
 effect to a set of tracks without creating multiple instances of the same
-plugin.*
+plugin.
 
 Here's the overview of how we will do this:
 
-* Create a single bus with the desired plugin.
-* Add a send to each drum track to which you want to apply the effect.
-* Route these sends to the bus.
+1. Create a single bus with the desired plugin.
+2. Add a send to each drum track to which you want to apply the effect.
+3. Route these sends to the bus.
 
 ## Creating the Bus and adding a Plugin
 
-Create a bus (menu *Track > Add Track, Bus, or VCA...*), name it
+Create a bus (`Track > Add Track, Bus, or VCA...` in the menu), name it
 appropriately, and add a plugin in the pre-fader region (right-click just
 above the fader's blue rectangle in the processor box), as discussed in the
 previous chapter, _Using Plugins_.
@@ -108,13 +109,13 @@ You can drag the send rectangle up and down the processor box to make it pre-
 or post-fader as needed.
 
 {{% notice tip %}}
-The choice of pre- or post-fader depending on the type of effect plugin
-used and the desired result. For this exercise, either one will work.
+The choice of pre- or post-fader depending on the type of effect plugin used and
+the desired result. For this exercise, either one will work.
 {{% /notice %}}
 
 A send behaves just like any other plugin in the processor box. You can
-deactivate it temporarily by clicking on the small LED, and you can right
-click on the rectangle to access other options, including _Delete_.
+deactivate it temporarily by clicking on the small LED, and you can right click
+on the rectangle to access other options, including _Delete_.
 
 ### Send Fader
 
@@ -124,10 +125,9 @@ increase or decrease its volume.
 {{< figure alt="sendfader" src="en/Ardour4_Send_Fader.png" >}} 
 
 The _Drums_ bus is now receiving the sum of all tracks, and applying the effect
-to it. A single plugin applied to the bus controls the effect for the mix of
-all drum sounds routed there. This way, you have independent control over the
-"dry" sound of the original tracks, and the "wet" sound of coming out of the
-Bus. 
+to it. A single plugin applied to the bus controls the effect for the mix of all
+drum sounds routed there. This way, you have independent control over the "dry"
+sound of the original tracks, and the "wet" sound of coming out of the bus. 
 
 Because sends are very useful for this kind of work with effect plugins, they
 are also commonly called "Effect Sends".