From 0e7b75813743e0b7fca001e4199492f00277fc43 Mon Sep 17 00:00:00 2001
From: Argelbargel <karsten.kraus@web.de>
Date: Mon, 30 Sep 2024 11:42:57 +0200
Subject: [PATCH] fix readme

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 5733a15..511e95a 100644
--- a/README.md
+++ b/README.md
@@ -198,7 +198,7 @@ vault:
 #### Vault Leader-Detection
 It is recommended to specify only a single url in `vault.nodes.urls` which always points to the current leader (e.g. to 
 `http(s)://vault-active.<vault-namespace>.svc.cluster.local:<vault-server service-port>` when using the vault-helm chart) and to disable the automatic leader detection by not specifying `nodes.autoDetectLeader` or setting it to `false`. 
-If automatic leader detection is enabled the response of (vault's /sys/leader-API-Endpoint)[https://developer.hashicorp.com/vault/api-docs/system/leader] must return a `leaderAddress` reachable by the agent.
+If automatic leader detection is enabled the response of [vault's /sys/leader-api-endpoint](https://developer.hashicorp.com/vault/api-docs/system/leader) must return a `leaderAddress` reachable by the agent.
 If you specify multiple urls in `vault.nodes.urls` without enabling `vault.nodes.autoDetectLeader`, the agent contacts each node and check whether it is the current leader.