Update note elements 14 (#253)

Author: network-charles

how-to/installation/netboot-the-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64.md

@@ -65,8 +65,9 @@ The GRUB binary helps us redirect the download path to the target files via `gru
 $ sudo wget http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/uefi/grub2-arm64/current/grubnetaa64.efi.signed -O /var/lib/tftpboot/grubnetaa64.efi.signed
 ```
 
-> **Note**:
-> You may need to change **the archive distribution's name** from `Focal` to your target distribution name.
+```{note}
+You may need to change **the archive distribution's name** from `Focal` to your target distribution name.
+```
 
 ### Download and serve more files
 

how-to/observability/install-munin.md

@@ -35,8 +35,9 @@ On `server01` edit the `/etc/munin/munin.conf` file, adding the IP address for `
        address 172.18.100.101
 ```
 
-> **Note**:
-> Replace `server02` and `172.18.100.101` with the actual hostname and IP address for your server.
+```{note}
+Replace `server02` and `172.18.100.101` with the actual hostname and IP address for your server.
+```
 
 ## Configure `munin-node`
 
@@ -46,8 +47,9 @@ Next, configure `munin-node` on `server02`. Edit `/etc/munin/munin-node.conf` to
 allow ^172\.18\.100\.100$
 ```
 
-> **Note**:
-> Replace `^172\.18\.100\.100$` with the IP address for your `munin` server.
+```{note}
+Replace `^172\.18\.100\.100$` with the IP address for your `munin` server.
+```
 
 Now restart `munin-node` on `server02` for the changes to take effect:
 

how-to/observability/install-nagios.md

@@ -1,8 +1,9 @@
 (install-nagios)=
 # How to install and configure Nagios Core 3
 
-> **Note**:
-> Nagios Core 3 has been deprecated and is now replaced by Nagios Core 4. The `nagios3` package was last supported in Bionic, so subsequent releases should use `nagios4` instead.
+```{note}
+Nagios Core 3 has been deprecated and is now replaced by Nagios Core 4. The `nagios3` package was last supported in Bionic, so subsequent releases should use `nagios4` instead.
+```
 
 The monitoring of essential servers and services is an important part of system administration. This guide walks through how to install and configure Nagios Core 3 for availability monitoring.
 
@@ -40,8 +41,9 @@ Next, on `server02` install the `nagios-nrpe-server` package. From a terminal on
 sudo apt install nagios-nrpe-server
 ```
 
-> **Note**:
-> NRPE allows you to execute local checks on remote hosts. There are other ways of accomplishing this through other Nagios plugins, as well as other checks.
+```{note}
+NRPE allows you to execute local checks on remote hosts. There are other ways of accomplishing this through other Nagios plugins, as well as other checks.
+```
 
 ## Configuration overview
 
@@ -57,8 +59,9 @@ There are a couple of directories containing Nagios configuration and check file
 
 There are multiple checks Nagios can be configured to execute for any given host. For this example, Nagios will be configured to check disk space, {term}`DNS`, and a MySQL {term}`hostgroup`. The DNS check will be on `server02`, and the MySQL hostgroup will include both `server01` and `server02`.
 
-> **Note**:
-> See these guides for details on [setting up Apache](https://discourse.ubuntu.com/t/web-servers-apache/11510), [Domain Name Service](https://discourse.ubuntu.com/t/service-domain-name-service-dns/11318), and [MySQL](https://discourse.ubuntu.com/t/databases-mysql/11515).
+```{note}
+See these guides for details on [setting up Apache](https://discourse.ubuntu.com/t/web-servers-apache/11510), [Domain Name Service](https://discourse.ubuntu.com/t/service-domain-name-service-dns/11318), and [MySQL](https://discourse.ubuntu.com/t/databases-mysql/11515).
+```
 
 Additionally, there are some terms that once explained will hopefully make understanding Nagios configuration easier:
 
@@ -85,9 +88,11 @@ First, create a **host** configuration file for `server02`. Unless otherwise spe
 ```bash
 sudo cp /etc/nagios3/conf.d/localhost_nagios2.cfg \
 /etc/nagios3/conf.d/server02.cfg
-    
-> **Note**:
-> In all command examples, replace "`server01`", "`server02`", `172.18.100.100`, and `172.18.100.101` with the host names and IP addresses of your servers.
+```
+
+```{note}
+In all command examples, replace "`server01`", "`server02`", `172.18.100.100`, and `172.18.100.101` with the host names and IP addresses of your servers.
+```
 
 ### Edit the host config file    
 
@@ -148,9 +153,10 @@ The Nagios check needs to authenticate to MySQL. To add a `nagios` user to MySQL
 mysql -u root -p -e "create user nagios identified by 'secret';"
 ```
 
-> **Note**:
-> The `nagios` user will need to be added to all hosts in the **mysql-servers** hostgroup.
-    
+```{note}
+The `nagios` user will need to be added to all hosts in the **mysql-servers** hostgroup.
+```
+
 Restart nagios to start checking the MySQL servers.
 
 sudo systemctl restart nagios3.service

how-to/observability/set-up-your-lma-stack.md

@@ -1,8 +1,11 @@
 (set-up-your-lma-stack)=
 # Set up your LMA stack
 
-> **LMA to COS**
-> The LMA stack is being succeeded by the Canonical Observability Stack (COS). While the current LMA still works, most users are recommended to consider COS instead. For more information, refer to [this COS topic](https://charmhub.io/topics/canonical-observability-stack/). In environments with more limited resources, there is also [COS lite](https://charmhub.io/topics/canonical-observability-stack/editions/lite).
+```{note}
+**LMA to COS**
+
+The LMA stack is being succeeded by the Canonical Observability Stack (COS). While the current LMA still works, most users are recommended to consider COS instead. For more information, refer to [this COS topic](https://charmhub.io/topics/canonical-observability-stack/). In environments with more limited resources, there is also [COS lite](https://charmhub.io/topics/canonical-observability-stack/editions/lite).
+```
 
 Logging, Monitoring, and Alerting (LMA) is a collection of tools that guarantee the availability of your running infrastructure. Your LMA stack will help point out issues in load, networking, and other resources before they become a failure point.
 

how-to/observability/use-nagios-with-munin.md

@@ -1,8 +1,9 @@
 (use-nagios-with-munin)=
 # How to use Nagios with Munin
 
-> **Note**:
-> Nagios Core 3 has been deprecated and is now replaced by Nagios Core 4. The `nagios3` package was last supported in Bionic, so subsequent releases should use `nagios4` instead.
+```{note}
+Nagios Core 3 has been deprecated and is now replaced by Nagios Core 4. The `nagios3` package was last supported in Bionic, so subsequent releases should use `nagios4` instead.
+```
 
 The monitoring of essential servers and services is an important part of system administration. Most network services are monitored for performance, availability, or both. This section will cover installation and configuration of Nagios 3 for availability monitoring alongside Munin for performance monitoring.
 
@@ -40,8 +41,9 @@ Next, on `server02` install the `nagios-nrpe-server` package. From a terminal on
 sudo apt install nagios-nrpe-server
 ```
 
-> **Note**:
-> NRPE allows you to run local checks on remote hosts. There are other ways of accomplishing this, including through other Nagios plugins.
+```{note}
+NRPE allows you to run local checks on remote hosts. There are other ways of accomplishing this, including through other Nagios plugins.
+```
 
 ### Configuration overview
 
@@ -59,8 +61,9 @@ There are a few directories containing Nagios configuration and check files.
 
 There are many checks Nagios can be configured to run for any particular host. In this example, Nagios will be configured to check disk space, {term}`DNS`, and a MySQL {term}`host group <hostgroup>`. The DNS check will be on `server02`, and the MySQL host group will include both `server01` and `server02`.
 
-> **Note**:
-> See these additional guides for details on setting up {ref}`Apache <install-apache2>`, {ref}`Domain Name Service (DNS) <install-dns>`, and {ref}`MySQL <install-mysql>`.
+```{note}
+See these additional guides for details on setting up {ref}`Apache <install-apache2>`, {ref}`Domain Name Service (DNS) <install-dns>`, and {ref}`MySQL <install-mysql>`.
+```
 
 Additionally, there are some terms that once explained will hopefully make understanding Nagios configuration easier:
 
@@ -87,8 +90,9 @@ sudo cp /etc/nagios3/conf.d/localhost_nagios2.cfg \
 /etc/nagios3/conf.d/server02.cfg
 ```
 
-> **Note**:
-> In the above and following command examples, replace "`server01`", "`server02`", `172.18.100.100`, and `172.18.100.101` with the host names and IP addresses of your servers.
+```{note}
+In the above and following command examples, replace "`server01`", "`server02`", `172.18.100.100`, and `172.18.100.101` with the host names and IP addresses of your servers.
+```
 
 Next, edit `/etc/nagios3/conf.d/server02.cfg`:
 
@@ -143,9 +147,10 @@ The Nagios check needs to authenticate to MySQL. To add a `nagios` user to MySQL
 ```bash
 mysql -u root -p -e "create user nagios identified by 'secret';"
     
-> **Note**:
-> The `nagios` user will need to be added all hosts in the `mysql-servers` host group.
-    
+```{note}
+The `nagios` user will need to be added all hosts in the `mysql-servers` host group.
+```
+
 Restart Nagios to start checking the MySQL servers.
 
 ```bash
@@ -220,8 +225,9 @@ On `server01` edit the `/etc/munin/munin.conf` to add the IP address for `server
        address 172.18.100.101
 ```
 
-> **Note**:
-> Replace `server02` and `172.18.100.101` with the actual hostname and IP address of your server.
+```{note}
+Replace `server02` and `172.18.100.101` with the actual hostname and IP address of your server.
+```
 
 ### Configure munin-node on server02
 
@@ -231,8 +237,9 @@ To configure `munin-node` on `server02`, edit `/etc/munin/munin-node.conf` to al
 allow ^172\.18\.100\.100$
 ```
 
-> **Note**:
-> Replace `^172\.18\.100\.100$` with IP address for your Munin server.
+```{note}
+Replace `^172\.18\.100\.100$` with IP address for your Munin server.
+```
 
 Now restart `munin-node` on `server02` for the changes to take effect:
 
@@ -242,8 +249,9 @@ sudo systemctl restart munin-node.service
 
 Finally, in a browser go to `http://server01/munin`, and you should see links to some graphs displaying information from the standard `munin-plugins` for disk, network, processes, and system.
 
-> **Note**:
-> Since this is a new install it may take some time for the graphs to display anything useful.
+```{note}
+Since this is a new install it may take some time for the graphs to display anything useful.
+```
 
 ### Additional plugins