Bump TFA to 2.2.0, improve meta descriptinos

Signed-off-by: David Young <davidy@funkypenguin.co.nz>

manuscript/recipes/autopirate/index.md

@@ -6,7 +6,7 @@ description: A fully-featured recipe to automate finding, downloading, and organ
 
 Once the cutting edge of the "internet" (_pre-world-wide-web and mosiac days_), Usenet is now a murky, geeky alternative to torrents for file-sharing. However, it's **cool** geeky, especially if you're into having a fully automated media platform.
 
-A good starter for the usenet scene is <https://www.reddit.com/r/usenet/>. Because it's so damn complicated, a host of automated tools exist to automate the process of finding, downloading, and managing content. The tools included in this recipe are as follows:
+A good starter for the usenet scene is <https://www.reddit.com/r/usenet/>. Because it's so damn complicated, a host of automated tools exist to automate the process of finding, downloading, and managing content. The tools included in this recipe are as per the following example:
 
 ![Autopirate Screenshot](../../images/autopirate.png)
 

manuscript/recipes/collabora-online.md

@@ -69,7 +69,7 @@ termination=true
 
 ### Create docker-compose.yml
 
-Create ```/var/data/config/collabora/docker-compose.yml``` as follows:
+Create ```/var/data/config/collabora/docker-compose.yml``` as per the following example:
 
 ```yaml
 version: "3.0"
@@ -91,7 +91,7 @@ services:
 
 ### Create nginx.conf
 
-Create ```/var/data/config/collabora/nginx.conf``` as follows, changing the ```server_name``` value to match the environment variable you established above:
+Create ```/var/data/config/collabora/nginx.conf``` as per the following example, changing the ```server_name``` value to match the environment variable you established above:
 
 ```ini
 upstream collabora-upstream {
@@ -155,7 +155,7 @@ Create an empty `/var/data/collabora/loolwsd.xml` by running `touch /var/data/co
 
 ### Setup Docker Swarm
 
-Create `/var/data/config/collabora/collabora.yml` as follows, changing the traefik frontend_rule as necessary:
+Create `/var/data/config/collabora/collabora.yml` as per the following example, changing the traefik frontend_rule as necessary:
 
 --8<-- "premix-cta.md"
 

manuscript/recipes/duplicati.md

@@ -30,7 +30,7 @@ Similar to the other backup options in the Cookbook, we can use Duplicati to bac
 
 ### Setup data locations
 
-We'll need a folder to store a docker-compose configuration file and an associated environment file. If you're following my filesystem layout, create `/var/data/config/duplicati` (*for the config*), and `/var/data/duplicati` (*for the metadata*) as follows:
+We'll need a folder to store a docker-compose configuration file and an associated environment file. If you're following my filesystem layout, create `/var/data/config/duplicati` (*for the config*), and `/var/data/duplicati` (*for the metadata*) as per the following example:
 
 ```bash
 mkdir /var/data/config/duplicati

manuscript/recipes/duplicity.md

@@ -35,7 +35,7 @@ So what does this mean for our stack? It means we can leverage Duplicity to back
 
 ### Setup data locations
 
-We'll need a folder to store a docker-compose .yml file, and an associated .env file. If you're following my filesystem layout, create `/var/data/config/duplicity` (_for the config_), and `/var/data/duplicity` (_for the metadata_) as follows:
+We'll need a folder to store a docker-compose .yml file, and an associated .env file. If you're following my filesystem layout, create `/var/data/config/duplicity` (_for the config_), and `/var/data/duplicity` (_for the metadata_) as per the following example:
 
 ```bash
 mkdir /var/data/config/duplicity
@@ -72,7 +72,7 @@ See the [data layout reference](/reference/data_layout/) for an explanation of t
 
 ### Run a test backup
 
-Before we launch the automated daily backups, let's run a test backup, as follows:
+Before we launch the automated daily backups, let's run a test backup, as per the following example:
 
 ```bash
 docker run --env-file duplicity.env -it --rm -v \

manuscript/recipes/keycloak/index.md

@@ -16,7 +16,7 @@ KeyCloak's OpenID provider can also be used in combination with [Traefik Forward
 
 ### Setup data locations
 
-We'll need several directories to bind-mount into our container for both runtime and backup data, so create them as follows
+We'll need several directories to bind-mount into our container for both runtime and backup data, so create them as per the following example
 
 ```bash
 mkdir -p /var/data/runtime/keycloak/database

manuscript/recipes/minio.md

@@ -184,7 +184,7 @@ Having setup your buckets, users, and policies - you can give out your minio ext
 
 I tested the S3 mount using [goofys](https://github.com/kahing/goofys), "a high-performance, POSIX-ish Amazon S3 file system written in Go".
 
-First, I created ~/.aws/credentials, as follows:
+First, I created ~/.aws/credentials, as per the following example:
 
 ```ini
 [default]

manuscript/recipes/openldap.md

@@ -53,7 +53,7 @@ LDAP_TLS=false
 
 The Dockerized version of LDAP Account Manager is a little fiddly. In order to maintain a config file which persists across container restarts, we need to present the container with a copy of /var/www/html/config/lam.conf, tweaked for our own requirements.
 
-Create ```/var/data/openldap/lam/config/config.cfg``` as follows:
+Create ```/var/data/openldap/lam/config/config.cfg``` as per the following example:
 
 ???+ note "Much scroll, very text. Click here to collapse it for better readability"
 
@@ -123,7 +123,7 @@ Create ```/var/data/openldap/lam/config/config.cfg``` as follows:
 
 While config.cfg (_above_) defines application-level configuration, <profile\>.cfg is used to configure "domain-specific" configuration. You probably only need a single profile, but LAM could theoretically be used to administer several totally unrelated LDAP servers, ergo the concept of "profiles".
 
-Create yours profile (_you chose a default profile in config.cfg above, remember?_) by creating ```/var/data/openldap/lam/config/<profile>.conf```, as follows:
+Create yours profile (_you chose a default profile in config.cfg above, remember?_) by creating ```/var/data/openldap/lam/config/<profile>.conf```, as per the following example:
 
 ???+ note "Much scroll, very text. Click here to collapse it for better readability"
 

manuscript/recipes/restic.md

@@ -173,7 +173,7 @@ Of note above is =="Repository successfully initialized"== - this indicates that
 
 Repeat after me : "**It's not a backup unless you've tested a restore**"
 
-The simplest way to test your restore is to run the container once, using the variables you're already prepared, with custom arguments, as follows:
+The simplest way to test your restore is to run the container once, using the variables you're already prepared, with custom arguments, as per the following example:
 
 ```bash
 docker run --rm -it --name restic-restore --env-file /var/data/config/restic/restic-backup.env \