From 91501b78d170cffe79dca6f5b86dfc43018fbfc6 Mon Sep 17 00:00:00 2001
From: bilalcaliskan <bilalcaliskan@protonmail.com>
Date: Sat, 11 Dec 2021 03:25:20 +0300
Subject: [PATCH] update readme

---
 .pre-commit-config.yaml | 1 -
 README.md               | 4 ++--
 2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index 7b4e2e1..746cd88 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -6,7 +6,6 @@ repos:
     hooks:
       -   id: check-yaml
       -   id: end-of-file-fixer
-      -   id: trailing-whitespace
   - repo: git://github.com/dnephin/pre-commit-golang
     rev: v0.4.0
     hooks:
diff --git a/README.md b/README.md
index 417eec1..eb50685 100644
--- a/README.md
+++ b/README.md
@@ -13,7 +13,7 @@ instances at the same time to manage the cache properly. If you are using Varnis
 
 varnish-cache-invalidator can be used for standalone Varnish instances or Varnish pods inside a Kubernetes cluster.
 
-**Standalone mode**
+**Standalone mode**  
 In that mode, varnish-cache-invalidator multiplexes requests on static standalone Varnish instances which are provided
 with **--targetHosts** flag. This flag gets comma seperated list of hosts.
 
@@ -23,7 +23,7 @@ Please check all the command line arguments on **Configuration** section. Requir
 --targetHosts
 ```
 
-**Kubernetes mode**
+**Kubernetes mode**  
 In that mode, varnish-cache-invalidator discovers kube-apiserver for running [Varnish](https://github.com/varnishcache/varnish-cache) pods inside
 Kubernetes and multiplexes **PURGE** requests on them at the same time to manage the cache properly.