From 162c8f5f8ea71b871cb94dd45c7844c4bf2faf08 Mon Sep 17 00:00:00 2001
From: Henok Biadglign Ademtew <46082799+HenokB@users.noreply.github.com>
Date: Mon, 8 Aug 2022 19:08:29 +0300
Subject: [PATCH] Link 'load-balancer' and 'service' (#1177)

Signed-off-by: Henok Biadglign Ademtew <46082799+HenokB@users.noreply.github.com>
---
 content/en/blue-green-deployment.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/en/blue-green-deployment.md b/content/en/blue-green-deployment.md
index df93c29dce..b6433aa851 100644
--- a/content/en/blue-green-deployment.md
+++ b/content/en/blue-green-deployment.md
@@ -11,8 +11,8 @@ Blue-green deployment is a strategy for updating running computer systems with m
 The operator maintains two environments, dubbed “blue” and “green”. 
 One serves production traffic (the version all users are currently using), whilst the other is updated. 
 Once testing has concluded on the non-active (green) environment, 
-production traffic is switched over (often via the use of a load balancer). 
-Note that blue-green deployment usually means switching the entire environments, comprising many services, all at once. 
+production traffic is switched over (often via the use of a [load balancer](/load-balancer/)). 
+Note that blue-green deployment usually means switching the entire environments, comprising many [services](/service/), all at once. 
 Confusingly, sometimes the term is used with regard to individual services within a system. 
 To avoid this ambiguity, the term “zero-downtime deployment” is preferred when referring to individual components.