From 39596de19eb13291a33ac7b439b812e1ca3d0e89 Mon Sep 17 00:00:00 2001
From: divya-mohan0209 <divya.mohan0209@gmail.com>
Date: Tue, 8 Mar 2022 20:52:54 +0530
Subject: [PATCH] Update
 content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md

Co-authored-by: Jen Travinski <jennifer.travinski@suse.com>
---
 .../v2.5/en/installation/resources/update-ca-cert/_index.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md b/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md
index 5b8e5f7b256..751feae2d8c 100644
--- a/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md
+++ b/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md
@@ -154,4 +154,4 @@ Select 'Force Update' for the clusters within the [Continuous Delivery]({{<baseu
 
 ### Why is this step required?
 
-Fleet agents in Rancher managed clusters store kubeconfig that is used to connect to the Rancher proxied kube-api in the fleet-agent secret of the fleet-system namespace. The kubeconfig contains a certificate-authority-data block containing the Rancher CA. When changing the Rancher CA, this needs to be updated for a successful connection of the fleet-agent to Rancher.
+Fleet agents in Rancher managed clusters store kubeconfig that is used to connect to the Rancher proxied kube-api in the fleet-agent secret of the fleet-system namespace. The kubeconfig contains a certificate-authority-data block containing the Rancher CA. When changing the Rancher CA, this block needs to be updated for a successful connection of the fleet-agent to Rancher.