From a140a6bad74bcf34e62e13b6efa63a17741eb5b1 Mon Sep 17 00:00:00 2001 From: Spencer Smith Date: Wed, 30 Mar 2022 20:53:26 -0400 Subject: [PATCH] docs: update releases shortcode in upgrade guide This PR moves to using % instead of < for the release shortcode. As far as I understand it, doing so tells hugo it's not raw html and thus the headers get rendered to the sidebar properly. We may want to switch the other uses as well, but I'm not sure it would make any difference one way or another. Signed-off-by: Spencer Smith --- website/content/v1.0/guides/upgrading-talos.md | 4 ++-- website/content/v1.1/guides/upgrading-talos.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/website/content/v1.0/guides/upgrading-talos.md b/website/content/v1.0/guides/upgrading-talos.md index e0d0d4018d..d8f671dbf0 100644 --- a/website/content/v1.0/guides/upgrading-talos.md +++ b/website/content/v1.0/guides/upgrading-talos.md @@ -26,7 +26,7 @@ To see a live demo of an upgrade of Talos Linux, see the video below: -### After Upgrade to {{< release >}} +## After Upgrade to {{% release %}} There are no specific actions to be taken after an upgrade. @@ -108,7 +108,7 @@ We set the bootloader to boot _once_ with the new kernel and OS image, then we r After the node comes back up and Talos verifies itself, it will make the bootloader change permanent, rejoin the cluster, and finally uncordon itself to receive new workloads. -### FAQs +## FAQs **Q.** What happens if an upgrade fails? diff --git a/website/content/v1.1/guides/upgrading-talos.md b/website/content/v1.1/guides/upgrading-talos.md index d5f570a14f..15a1a8a142 100644 --- a/website/content/v1.1/guides/upgrading-talos.md +++ b/website/content/v1.1/guides/upgrading-talos.md @@ -26,7 +26,7 @@ To see a live demo of an upgrade of Talos Linux, see the video below: -### After Upgrade to {{< release >}} +## After Upgrade to {{% release %}} There are no specific actions to be taken after an upgrade. @@ -100,7 +100,7 @@ We set the bootloader to boot _once_ with the new kernel and OS image, then we r After the node comes back up and Talos verifies itself, it will make the bootloader change permanent, rejoin the cluster, and finally uncordon itself to receive new workloads. -### FAQs +## FAQs **Q.** What happens if an upgrade fails?