From 0d2a5e794af36be51774859341075df1234ae2f4 Mon Sep 17 00:00:00 2001
From: Roshan Goswami <csengineer23@gmail.com>
Date: Sat, 7 Oct 2023 16:47:40 +0530
Subject: [PATCH] Updated docs to use the term ZooKeeper correctly

Signed-off-by: Roshan Goswami <csengineer23@gmail.com>
---
 .github/vale/styles/Klaw/branding.yml                       | 3 ++-
 ...ss-kafka-governance-making-life-easier-for-developers.md | 6 +++---
 2 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/.github/vale/styles/Klaw/branding.yml b/.github/vale/styles/Klaw/branding.yml
index 8267b865..0d9d01a1 100644
--- a/.github/vale/styles/Klaw/branding.yml
+++ b/.github/vale/styles/Klaw/branding.yml
@@ -24,4 +24,5 @@ swap:
   "type[ -]?scripts?": TypeScript
   "(?i)ssl": SSL
   "(?<!Klaw )cluster api": Klaw Cluster API
-  "(?i)kafka[ -]?connect": Kafka Connect
\ No newline at end of file
+  "(?i)kafka[ -]?connect": Kafka Connect
+  "(?i)zookeeper": ZooKeeper
\ No newline at end of file
diff --git a/blog/2023/05/effortless-kafka-governance-making-life-easier-for-developers.md b/blog/2023/05/effortless-kafka-governance-making-life-easier-for-developers.md
index 8ad0cf1b..a2a4acc4 100644
--- a/blog/2023/05/effortless-kafka-governance-making-life-easier-for-developers.md
+++ b/blog/2023/05/effortless-kafka-governance-making-life-easier-for-developers.md
@@ -99,12 +99,12 @@ Failures are an inevitable part of any system, and Kafka applications
 are no different. These failures can occur at different levels,
 including client-side issues where event deserialization creates
 problems for consumers, as well as infrastructure-related issues that
-result in the loss of zookeeper/Kafka configurations.
+result in the loss of ZooKeeper/Kafka configurations.
 
 In the context of infrastructure failures, let's consider a scenario
 with 1000 topics, each possessing a unique configuration stored in a
-zookeeper. Now, imagine a situation where a disaster strikes, causing
-the zookeeper to crash and be unable to recover. This raises a critical
+ZooKeeper. Now, imagine a situation where a disaster strikes, causing
+the ZooKeeper to crash and be unable to recover. This raises a critical
 question: how swiftly can you retrieve the information and reboot your
 server? It's not just about having methods to store information but
 also about strategically implementing storage and retrieval processes