From f7d1d0f4960925086364e65030dbbf9b1a26be19 Mon Sep 17 00:00:00 2001
From: YRollHid <34071152+YRollHid@users.noreply.github.com>
Date: Tue, 27 Jul 2021 20:25:37 +0200
Subject: [PATCH] Update multicluster.md

Fix broken link to single cluster infrastructure walkthrough
---
 docs/multicluster.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/multicluster.md b/docs/multicluster.md
index 28359b6..5282fad 100644
--- a/docs/multicluster.md
+++ b/docs/multicluster.md
@@ -6,7 +6,7 @@ The scale at which many of these organizations work also compounds this problem.
 
 They also need the ability to manage configuration across all of these clusters: centralizing config where possible such that it can be updated in one place while still being able to have per cluster config where it isn’t.
 
-If you followed our [single cluster infrastructure walkthrough](./singleKeyVault/README.md) you saw how Bedrock enables you to scaffold and generate Terraform deployment scripts. We will expand on that here to describe how Bedrock makes maintaining multiple Kubernetes clusters at scale easier.
+If you followed our [single cluster infrastructure walkthrough](./single-cluster.md) you saw how Bedrock enables you to scaffold and generate Terraform deployment scripts. We will expand on that here to describe how Bedrock makes maintaining multiple Kubernetes clusters at scale easier.
 
 Bedrock leverages Terraform for infrastructure deployment and the project itself maintains a number of base environment templates for common cluster deployment scenarios. These are just Terraform scripts and can be used directly (or even independently) from the rest of Bedrock’s automation.