diff --git a/content/editing-sessions/working-with-regions/index.en.md b/content/editing-sessions/working-with-regions/index.en.md
index 5f0064d..6cb5236 100644
--- a/content/editing-sessions/working-with-regions/index.en.md
+++ b/content/editing-sessions/working-with-regions/index.en.md
@@ -67,7 +67,7 @@ different track.
 When a set of one or more regions is selected, you can move the whole set by
 dragging with the mouse.
 
-{{% notice note %}}
+{{% notice tip %}}
 Make sure to select the region in its waveform section, because selecting the
 bottom title bar area is used for a different action (see _Trimming Regions_
 below).
diff --git a/content/exporting-sessions/exporting-a-region/index.en.md b/content/exporting-sessions/exporting-a-region/index.en.md
index 1d13c9c..7b33eb6 100644
--- a/content/exporting-sessions/exporting-a-region/index.en.md
+++ b/content/exporting-sessions/exporting-a-region/index.en.md
@@ -70,13 +70,15 @@ ranges, not the whole session.
 
 Your regions have now been exported to single audio files.
 
-{{% notice info %}} This method exports *everything* that falls under each
-defined time range. In other words, if you have other regions in other tracks
-sounding simultaneously with the region(s) you want to export, they will be
-mixed together. Another way of looking at it is this: the export operation will
+{{% notice tip %}}
+This method exports *everything* that falls under each defined time range.
+In other words, if you have other regions in other tracks sounding
+simultaneously with the region(s) you want to export, they will be mixed 
+together. Another way of looking at it is this: the export operation will
 export everything that *plays* under the defined time ranges. If that is not
-what you want, you can use solo or mute buttons on select tracks to ensure you
-export only what you want. {{% /notice %}}
+what you want, you can use solo or mute buttons on select tracks to ensure 
+you export only what you want.
+{{% /notice %}}
 
 ## Continuing
 
diff --git a/content/getting-started/starting-ardour-on-ubuntu/index.en.md b/content/getting-started/starting-ardour-on-ubuntu/index.en.md
index 1495ff1..e045e4a 100644
--- a/content/getting-started/starting-ardour-on-ubuntu/index.en.md
+++ b/content/getting-started/starting-ardour-on-ubuntu/index.en.md
@@ -5,50 +5,73 @@ chapter = false
 weight = 1
 +++
 
-Ardour supports both Linux, Windows, and macOS. There is very little difference about how it works on all these operating systems. So while this tutorial assumes using Ubuntu Linux, you should expect it to work the same way on other operating systems and Linux flavors.
+Ardour supports both Linux, Windows, and macOS. There is very little
+difference about how it works on all these operating systems. So while this 
+tutorial assumes using Ubuntu Linux, you should expect it to work the same 
+way on other operating systems and Linux flavors.
 
 ## First-launch wizard
 
-When you first start Ardour, it will ask you a few questions to make a basic customization: user interface and font scale (if you have a HiDPI display), default folder where new sessions would be created, preferred way to monitor signal being recorded etc.
+When you first start Ardour, it will ask you a few questions to make a 
+basic customization: user interface and font scale (if you have a HiDPI 
+display), default folder where new sessions would be created, preferred way 
+to monitor signal being recorded etc.
 
 {{< figure src="en/ardour7-gui-and-font-scaling.png" alt="GUI and font scaling" >}}
 
-This dialog will never be shown again, unless you wipe all settings. You can change all the preferences you set there at any time later in the _Preferences_ dialog.
+This dialog will never be shown again, unless you wipe all settings. You 
+can change all the preferences you set there at any time later in the 
+_Preferences_ dialog.
 
 ## Create new session
 
-Once you get past the first-launch wizard, Ardour will suggest you create a new _session_ from one of a few available templates.
+Once you get past the first-launch wizard, Ardour will suggest you create a 
+new _session_ from one of a few available templates.
 
 {{< figure src="en/ardour7-new-session-templates.png" alt="New session templates" >}}
 
-A session encompasses all the material you have: tracks with audio and MIDI data, effects associated with tracks and busses etc. Thus, a session is essentially a project file from which you can render a mono or a stereo audio file to deliver to a client, use in a video, or upload to a streaming service.
+A session encompasses all the material you have: tracks with audio and MIDI 
+data, effects associated with tracks and busses etc. Thus, a session is 
+essentially a project file from which you can render a mono or a stereo 
+audio file to deliver to a client, use in a video, or upload to a streaming 
+service.
 
 For simplicity's sake let's go with an empty session as shown above.
 
-Ardour will always automatically suggest storing a new session in the default folder that you set at the previous step.
+Ardour will always automatically suggest storing a new session in the 
+default folder that you set at the previous step.
 
-When giving a new session a name, please avoid using any characters other than letters and numbers, like white spaces, accented letters, `!@#$%*()+`, periods, commas, etc. Use dashes or underscores if you like. For example, instead of "My Great Session!", prefer "My_Great_Session", or "MyGreatSession", or "my-great-session". Instead of "Açaí", write "Acai" (without accented letters), etc.
+When giving a new session a name, please avoid using any characters other 
+than letters and numbers, like white spaces, accented letters, `!@#$%*()+`, 
+periods, commas, etc. Use dashes or underscores if you like. For example, 
+instead of "My Great Session!", prefer "My_Great_Session", or 
+"MyGreatSession", or "my-great-session". Instead of "Açaí", write "Acai" 
+(without accented letters), etc.
 
 Name your new project and click **Open** .
 
-Once you have created your Ardour session, do _not_ manually rename any folders or files that belong to the session. Otherwise, Ardour will fail to locate the files inside those folders and will ask you to point to them.
+Once you have created your Ardour session, do _not_ manually rename any 
+folders or files that belong to the session. Otherwise, Ardour will fail to 
+locate the files inside those folders and will ask you to point to them.
 
-{{% notice info %}}
-Once you saved at least one session, the _Session Setup_ dialog will look differently: there will be a list of recently opened sessions and a way to open an existing session that is not on that list.
+{{% notice tip %}}
+Once you saved at least one session, the _Session Setup_ dialog will look 
+differently: there will be a list of recently opened sessions and a way to 
+open an existing session that is not on that list.
 {{% /notice %}}
 
 ## Choosing an audio system and its settings
 
 At the next step, you will need to choose and configure the _audio system_.
 
-On Linux, you have multiple audio systems (or _backends_) available. _ALSA_ is
-suggested by default. It is currently the recommended way to use Ardour in
-production. With ALSA, there are no convenience wrappers or abstractions. You
-connect to physical audio and MIDI ports directly. This means Ardour will take
-over the audio interface of your choice and won't share it with any other
-applications. As long as Ardour is running, any other desktop applications you
-are running too won't be able to connect to the audio interface and play any
-sound.
+On Linux, you have multiple audio systems (or _backends_) available. _ALSA_
+is suggested by default. It is currently the recommended way to use Ardour
+in production. With ALSA, there are no convenience wrappers or
+abstractions. You connect to physical audio and MIDI ports directly. This
+means Ardour will take over the audio interface of your choice and won't
+share it with any other applications. As long as Ardour is running, any 
+other desktop applications you are running too won't be able to connect to 
+the audio interface and play any sound.
 
 {{< figure src="en/ardour7-alsa-backend-settings.png" alt="Audio/MIDI setup" >}}
 
@@ -94,6 +117,7 @@ window:
 
 ## Continuing
 
-In the next chapter you'll familiarize yourself with Ardour's user interface and its main windows: Editor, Mixer, Recorder, and Cue.
+In the next chapter you'll familiarize yourself with Ardour's user 
+interface and its main windows: Editor, Mixer, Recorder, and Cue.
 
 Next: [OVERVIEW OF THE INTERFACE](../overview-of-the-interface)
diff --git a/content/recording-audio/recording-audio/index.en.md b/content/recording-audio/recording-audio/index.en.md
index ac2d433..5be3c6d 100644
--- a/content/recording-audio/recording-audio/index.en.md
+++ b/content/recording-audio/recording-audio/index.en.md
@@ -34,7 +34,7 @@ above).
 allows you to edit the routing.
 5. Click on that button to investigate the routing.
 
-{{% notice note %}}
+{{% notice tip %}}
 If you don't see the _Editor Mixer_ strip, use the **Shift + E** shortcut to
 make it appear.
 {{% /notice %}}
@@ -66,7 +66,7 @@ you want to use so that we can do a test recording. If you don't see a green dot
 as in the screenshot above, click on the matrix to make the connection manually.
 You can now close this window.
 
-{{% notice note %}}
+{{% notice tip %}}
 The example above assumes you are recording a mono sound source onto a mono
 track. If you want to record in stereo, the instructions are pretty much the
 same, but you should create a stereo track. You should then see two green dots,
@@ -95,7 +95,7 @@ If you are using headphones, you should be able to hear ("monitor") the sounds
 being recorded. If you are using loudspeakers, be sure to turn their volume down
 to avoid feedback.
 
-{{% notice note %}}
+{{% notice tip %}}
 Unless you have told Ardour to do otherwise, the input being recorded will be
 monitored (in other words, heard) via the _Audition_ output. If you are not
 using headphones to monitor the recording process, you may get some loud