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 6058b75964d..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
@@ -3,4 +3,33 @@ title: Adding a Secret
 weight: 
 draft: true
 ---
-Coming Soon
+
+[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 containing the namespace(s) where you want to add a secret.
+
+1. From the main menu, select **Resources > Secrets**. Click **Add Secret**.
+
+1. Enter a **Name** for the secret.
+
+    >**Note:** Kubernetes classifies secrets, certificates, ConfigMaps, and registries all as [secrets](https://kubernetes.io/docs/concepts/configuration/secret/), and no two secrets in a project or namespace can have duplicate names. Therefore, to prevent conflicts, your secret must have a unique name among all secrets within your workspace.
+
+1. Select a **Scope** for the secret.
+
+1. From **Secret Values**, click **Add Secret Value** to add a key value pair. Add as many values as you need.
+
+	>**Tip:** You can add multiple key value pairs to the secret by copying and pasting.
+	>
+	> ![Bulk Key Value Pair Copy/Paste]({{< baseurl >}}/img/rancher/bulk-key-values.gif)
+
+1. Click **Save**.
+	
+
+**Result:** Your secret is added to the project or namespace, depending on the scope you chose. You can view the secret in the Rancher UI from the **Resources > Secrets** view.
+
+## What's Next?
+
+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).
diff --git a/content/rancher/v2.x/en/tasks/projects/add-configmaps/_index.md b/content/rancher/v2.x/en/tasks/projects/add-configmaps/_index.md
index a3e97507150..75bb0a2b077 100644
--- a/content/rancher/v2.x/en/tasks/projects/add-configmaps/_index.md
+++ b/content/rancher/v2.x/en/tasks/projects/add-configmaps/_index.md
@@ -20,13 +20,13 @@ ConfigMaps store general configuration information for an application, such as c
 
 1. From **Config Map Values**, click **Add Config Map Value** to add a key value pair to your ConfigMap. Add as many values as you need.
 
-	
+1. Click **Save**.
+
 	>**Note:** Don't use ConfigMaps to store sensitive data [use a secret](../add-a-secret).
 	>
 	>**Tip:** You can add multiple key value pairs to the ConfigMap by copying and pasting.
 	>
 	> ![Bulk Key Value Pair Copy/Paste]({{< baseurl >}}/img/rancher/bulk-key-values.gif)
-	
 
 **Result:** Your ConfigMap is added to the namespace. You can view it in the Rancher UI from the **Resources > Config Maps** view.
 
@@ -37,4 +37,4 @@ Now that you have a ConfigMap added to a namespace, you can add it to a workload
 - Application environment variables.
 - Specifying parameters for a Volume mounted to the workload.
 
-For more information on adding ConfigMaps to a workload, see [Deploying Workloads](../../workloads/deploy-workloads).
+For more information on adding ConfigMaps to a workload, see [Deploying Workloads](../../workloads/deploy-workloads).
\ No newline at end of file
diff --git a/content/rancher/v2.x/en/tasks/projects/add-registries/_index.md b/content/rancher/v2.x/en/tasks/projects/add-registries/_index.md
new file mode 100644
index 00000000000..35506db9e92
--- /dev/null
+++ b/content/rancher/v2.x/en/tasks/projects/add-registries/_index.md
@@ -0,0 +1,33 @@
+---
+title: Adding Registries
+weight: 
+draft: true
+---
+
+Registries are secrets containing credentials used to authenticate with [private registries](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/). Deployments use these secrets to authenticate with a private registry and then pull a Docker image hosted on it.
+
+>**Prerequisites:** You must have a [private registry](https://docs.docker.com/registry/deploying/) configured.
+
+>**Note:** Currently, credentials are pulled automatically only if the workload is created in the Rancher UI and not kubectl.
+
+1. From the **Global** view, select the project containing the namespace(s) where you want to add a registry.
+
+1. From the main menu, select **Resources > Registries**. Click **Add Registry**.
+
+1. Enter a **Name** for the registry.
+
+    >**Note:** Kubernetes classifies secrets, certificates, ConfigMaps, and registries all as [secrets](https://kubernetes.io/docs/concepts/configuration/secret/), and no two secrets in a project or namespace can have duplicate names. Therefore, to prevent conflicts, your registry must have a unique name among all secrets within your workspace.
+
+1. Select a **Scope** for the registry.
+
+1. Select the website that hosts your private registry. Then enter credentials that authenticate with the registry.
+
+1. Click **Save**.
+	
+**Result:** Your secret is added to the project or namespace, depending on the scope you chose. You can view the secret in the Rancher UI from the **Resources > Registries** view.
+
+## What's Next?
+
+Now that you have a registry added to the project or namespace, you can add it to a workload that's deploying an image from your private registry.
+
+For more information on adding a registry to a workload, see [Deploying Workloads](../../workloads/deploy-workloads).
diff --git a/content/rancher/v2.x/en/tasks/projects/use-private-registries/_index.md b/content/rancher/v2.x/en/tasks/projects/use-private-registries/_index.md
deleted file mode 100644
index caa3a46f234..00000000000
--- a/content/rancher/v2.x/en/tasks/projects/use-private-registries/_index.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Using Private Registries
-weight: 
-draft: true
----
-Coming Soon