From d0ca35f06c58ba0ee455d52e21b2355ae0598302 Mon Sep 17 00:00:00 2001
From: mbookham7 <34167192+mbookham7@users.noreply.github.com>
Date: Mon, 21 Sep 2020 09:44:26 +0100
Subject: [PATCH] Update _index.md

Updated formatting to fall in line with rest of the page.
---
 .../v2.x/en/cluster-admin/upgrading-kubernetes/_index.md        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/rancher/v2.x/en/cluster-admin/upgrading-kubernetes/_index.md b/content/rancher/v2.x/en/cluster-admin/upgrading-kubernetes/_index.md
index e7d4186006b..991ea4c7b50 100644
--- a/content/rancher/v2.x/en/cluster-admin/upgrading-kubernetes/_index.md
+++ b/content/rancher/v2.x/en/cluster-admin/upgrading-kubernetes/_index.md
@@ -50,7 +50,7 @@ When upgrading the Kubernetes version of a cluster, we recommend that you:
 
 1. Take a snapshot.
 1. Initiate a Kubernetes upgrade.
-1. If the upgrade fails, revert the cluster to the pre-upgrade Kubernetes version. This is achieved by selecting the *Restore etcd and Kubernetes version* option. This will return your cluster to the pre-upgrade kubernetes version before restoring the etcd snapshot.
+1. If the upgrade fails, revert the cluster to the pre-upgrade Kubernetes version. This is achieved by selecting the **Restore etcd and Kubernetes version** option. This will return your cluster to the pre-upgrade kubernetes version before restoring the etcd snapshot.
 
 The restore operation will work on a cluster that is not in a healthy or active state.
 {{% /tab %}}