From 63627bb7f3bf3ec7364654bfefb49c9249d27e37 Mon Sep 17 00:00:00 2001
From: Karl Johan Grahn <6355577+karl-johan-grahn@users.noreply.github.com>
Date: Sun, 28 Apr 2024 00:43:06 +0200
Subject: [PATCH] update (#653)

---
 docs/How-it-works.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/How-it-works.md b/docs/How-it-works.md
index 4646d9fa6..82b170568 100644
--- a/docs/How-it-works.md
+++ b/docs/How-it-works.md
@@ -2,7 +2,7 @@
 
 Reloader watches for `ConfigMap` and `Secret` and detects if there are changes in data of these objects. After change detection Reloader performs rolling upgrade on relevant Pods via associated `Deployment`, `Daemonset` and `Statefulset`.
 
-## How Change Detection Works
+## How Does Change Detection Work?
 
 Reloader watches changes in `configmaps` and `secrets` data. As soon as it detects a change in these. It forwards these objects to an update handler which decides if and how to perform the rolling upgrade.