From a2758944a506e28e2a4db2c7ace19e7680b543d7 Mon Sep 17 00:00:00 2001 From: "Jason L. van Brackel" Date: Tue, 3 Jul 2018 13:55:08 -0400 Subject: [PATCH] Minor spelling and grammar updates --- .../rancher/v2.x/en/tasks/projects/add-a-secret/_index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/rancher/v2.x/en/tasks/projects/add-a-secret/_index.md b/content/rancher/v2.x/en/tasks/projects/add-a-secret/_index.md index 819cb8d77c3..3f09f4cc029 100644 --- a/content/rancher/v2.x/en/tasks/projects/add-a-secret/_index.md +++ b/content/rancher/v2.x/en/tasks/projects/add-a-secret/_index.md @@ -7,9 +7,9 @@ draft: true [Secrets](https://kubernetes.io/docs/concepts/configuration/secret/#overview-of-secrets) store sensitive data like passwords, tokens, or keys. They may contain one or more key value pairs. When creating a secret, you can make it available for any deployment within a project, or you can limit it to a single namespace. -1. From the **Global** view, select the project or project containing the namespace that you want to add a secret to. +1. From the **Global** view, select the project containing the namespace(s) where you want to add a secret. -1. From the main menu, select **Resources > Secret**. Click **Add Secret**. +1. From the main menu, select **Resources > Secrets**. Click **Add Secret**. 1. Enter a **Name** for the secret. @@ -32,4 +32,4 @@ When creating a secret, you can make it available for any deployment within a pr Now that you have a secret added to the project or namespace, you can add it to a workload that you deploy. -For more information on adding secret to a workload, see [Deploying Workloads](../../workloads/deploy-workloads). \ No newline at end of file +For more information on adding secret to a workload, see [Deploying Workloads](../../workloads/deploy-workloads).