diff --git a/website/content/docs/v0.6/Guides/configuring-pull-through-cache.md b/website/content/docs/v0.6/Guides/configuring-pull-through-cache.md
index 0f4115570..e30a727e8 100644
--- a/website/content/docs/v0.6/Guides/configuring-pull-through-cache.md
+++ b/website/content/docs/v0.6/Guides/configuring-pull-through-cache.md
@@ -9,6 +9,12 @@ We spin up local caching pass-through registries to cache images and configure a
A similar approach might be used to run Talos in production in air-gapped environments.
It can be also used to verify that all the images are available in local registries.
+## Video Walkthrough
+
+To see a live demo of this writeup, see the video below:
+
+
+
## Requirements
The follow are requirements for creating the set of caching proxies:
diff --git a/website/content/docs/v0.6/Guides/upgrading-kubernetes.md b/website/content/docs/v0.6/Guides/upgrading-kubernetes.md
index 1bb7fa589..400d2762a 100644
--- a/website/content/docs/v0.6/Guides/upgrading-kubernetes.md
+++ b/website/content/docs/v0.6/Guides/upgrading-kubernetes.md
@@ -2,13 +2,21 @@
title: Upgrading Kubernetes
---
-## Kubernetes
+## Video Walkthrough
+
+To see a live demo of this writeup, see the video below:
+
+
+
+## Kubelet Image
In Kubernetes 1.19, the official `hyperkube` image was removed.
This means that in order to upgrade Kubernetes, Talos users will have to change the `command`, and `image` fields of each control plane component.
The `kubelet` image will also have to be updated, if you wish to specify the `kubelet` image explicitly.
The default used by Talos is sufficient in most cases.
+## Kubeconfig
+
In order to edit the control plane, we will need a working `kubectl` config.
If you don't already have one, you can get one by running:
diff --git a/website/content/docs/v0.6/Guides/upgrading-talos.md b/website/content/docs/v0.6/Guides/upgrading-talos.md
index 5561dd9ee..377e55938 100644
--- a/website/content/docs/v0.6/Guides/upgrading-talos.md
+++ b/website/content/docs/v0.6/Guides/upgrading-talos.md
@@ -2,6 +2,12 @@
title: Upgrading Talos
---
+## Video Walkthrough
+
+To see a live demo of this writeup, see the video below:
+
+
+
## Talos
In an effort to create more production ready clusters, Talos will now taint control plane nodes as unschedulable.
diff --git a/website/content/docs/v0.7/Guides/configuring-pull-through-cache.md b/website/content/docs/v0.7/Guides/configuring-pull-through-cache.md
index 6a3e7992a..08dd2dddb 100644
--- a/website/content/docs/v0.7/Guides/configuring-pull-through-cache.md
+++ b/website/content/docs/v0.7/Guides/configuring-pull-through-cache.md
@@ -9,6 +9,12 @@ We spin up local caching pass-through registries to cache images and configure a
A similar approach might be used to run Talos in production in air-gapped environments.
It can be also used to verify that all the images are available in local registries.
+## Video Walkthrough
+
+To see a live demo of this writeup, see the video below:
+
+
+
## Requirements
The follow are requirements for creating the set of caching proxies:
diff --git a/website/content/docs/v0.7/Guides/upgrading-kubernetes.md b/website/content/docs/v0.7/Guides/upgrading-kubernetes.md
index 2eb7f10c4..4df642291 100644
--- a/website/content/docs/v0.7/Guides/upgrading-kubernetes.md
+++ b/website/content/docs/v0.7/Guides/upgrading-kubernetes.md
@@ -2,7 +2,13 @@
title: Upgrading Kubernetes
---
-## Kubernetes
+## Video Walkthrough
+
+To see a live demo of this writeup, see the video below:
+
+
+
+## Kubeconfig
In order to edit the control plane, we will need a working `kubectl` config.
If you don't already have one, you can get one by running:
diff --git a/website/content/docs/v0.7/Guides/upgrading-talos.md b/website/content/docs/v0.7/Guides/upgrading-talos.md
index 7ab39556d..a7ff6e2c0 100644
--- a/website/content/docs/v0.7/Guides/upgrading-talos.md
+++ b/website/content/docs/v0.7/Guides/upgrading-talos.md
@@ -5,7 +5,13 @@ title: Upgrading Talos
Talos upgrades are effected by an API call.
The `talosctl` CLI utility will facilitate this, or you can use the automatic upgrade features provided by the [talos controller manager](https://github.com/talos-systems/talos-controller-manager).
-## talosctl upgrade
+## Video Walkthrough
+
+To see a live demo of this writeup, see the video below:
+
+
+
+## `talosctl` Upgrade
To manually upgrade a Talos node, you will specify the node's IP address and the
installer container image for the version of Talos to which you wish to upgrade.
@@ -23,7 +29,7 @@ There is an option to this command: `--preserve`, which can be used to explicitl
In most cases, it is correct to just let Talos perform its default action.
However, if you are running a single-node control-plane, you will want to make sure that `--preserve=true`.
-## Talos controller manager
+## Talos Controller Manager
The Talos Controller Manager can coordinate upgrades of your nodes
automatically.
diff --git a/website/content/docs/v0.7/Learn More/talosctl.md b/website/content/docs/v0.7/Learn More/talosctl.md
index dbf686a92..a4f2bd6e3 100644
--- a/website/content/docs/v0.7/Learn More/talosctl.md
+++ b/website/content/docs/v0.7/Learn More/talosctl.md
@@ -7,6 +7,12 @@ The `talosctl` tool packs a lot of power into a small package.
It acts as a reference implementation for the Talos API, but it also handles a lot of
conveniences for the use of Talos and its clusters.
+### Video Walkthrough
+
+To see some live examples of talosctl usage, view the following video:
+
+
+
## Client Configuration
Talosctl configuration is located in `$XDG_CONFIG_HOME/talos/config.yaml` if `$XDG_CONFIG_HOME` is defined.