From fae7663aef3a11843081b2568a50cc333a039f37 Mon Sep 17 00:00:00 2001
From: amitza <9674751+amitza@users.noreply.github.com>
Date: Tue, 27 Aug 2024 14:23:52 +0300
Subject: [PATCH] fix docs

---
 charts/provider/README.md.gotmpl | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/charts/provider/README.md.gotmpl b/charts/provider/README.md.gotmpl
index 5df0f6e..94a7b2f 100644
--- a/charts/provider/README.md.gotmpl
+++ b/charts/provider/README.md.gotmpl
@@ -77,7 +77,7 @@ EOF
 kubectl apply -f exported-key.yaml -n my-namespace
 ```
 
-### Create configuration for provider
+### Create secert configuration for provider
 
 Most provider configurations point to secure nodes and should remain encrypted on the cluster.
 For this you'll have to create another secert containing the entire nodes' configuration, for example:
@@ -158,7 +158,8 @@ key:
   passwordSecretKey: "password"
 
 chains:
-  lav1:
+  - name: my-lava-provider
+    id: lav1
     existingConfigSecret: "provider-config"
     existingConfigSecretKey: "config.yml"
 ```