From b567f550b8d0ed0c44ecf5c990eaed4310f22956 Mon Sep 17 00:00:00 2001
From: Klaudia Grzondziel <35192450+klaudiagrz@users.noreply.github.com>
Date: Tue, 14 Jul 2020 12:50:28 +0200
Subject: [PATCH] Fix a variable name in the command (#136)

---
 addons/gcp-service-broker-0.1.0/docs/broker/overview.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/addons/gcp-service-broker-0.1.0/docs/broker/overview.md b/addons/gcp-service-broker-0.1.0/docs/broker/overview.md
index 79de3a1b..dded72c1 100644
--- a/addons/gcp-service-broker-0.1.0/docs/broker/overview.md
+++ b/addons/gcp-service-broker-0.1.0/docs/broker/overview.md
@@ -12,7 +12,7 @@ The MySQL database is used to keep the broker's state. You can configure an exte
 
 ## Create a Secret
 
-To add the GCP Service Broker to your Namespace, prepare a service account and a JSON access key. 
+To add the GCP Service Broker to your Namespace, prepare a service account and a JSON access key.
 
 Follow these steps to create a Kubernetes Secret which contains a JSON access key:
 
@@ -30,7 +30,7 @@ Follow these steps to create a Kubernetes Secret which contains a JSON access ke
 
 7. Create a Secret from the JSON file by running this command:
 
-        kubectl create secret generic gcp-broker-data --from-file=sa-key={filename} --from-literal=project-name={gcp-project} --namespace {namespace}
+        kubectl create secret generic gcp-broker-data --from-file=sa-key={FILENAME} --from-literal=project-name={GCP_PROJECT_ID} --namespace {NAMESPACE}
 
 8. Click **Done**.