From 74e9e5f4fbfee1acefa1f2bcfd7e0711980f1380 Mon Sep 17 00:00:00 2001
From: "nabil.abdennad" <nabil.abdennadher@hesge.ch>
Date: Tue, 22 Oct 2024 09:30:13 +0200
Subject: [PATCH] secrets

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

diff --git a/README.md b/README.md
index de99c5e..f28342d 100644
--- a/README.md
+++ b/README.md
@@ -102,7 +102,7 @@ Both the `data-retrieval` and `forecast` folders have the following structure:
 
 ### Task 2: Data Retrieval deployment
 
-The data-retrieval module must access the S3 object storage to read the CSV file containing the electrical consumption. You must therfore use the AWS Acess key and secret key. We use "secrets" to propagate confidential data through the cluster. Read the data-retrieval-deployment.yaml carefully and spot the name of the secrets used. The secrets must be generated by the following command:
+The data-retrieval module must access the S3 object storage to read the CSV file containing the electrical consumption. You must therfore use the AWS Acess key and secret key. We use "secrets" to propagate confidential data through the cluster. Read the data-retrieval-deployment.yaml carefully and find out where the secrets should be used. The secrets must be generated by the following command:
 
 ```bash
 kubectl create secret generic <name-of-the-secrets> \
-- 
GitLab