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 9230b1f586..c95c8ccb66 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
@@ -1,10 +1,10 @@
 ---
 title: Adding a Secret
 weight: 
-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 containing the namespace(s) where you want to add a secret.
@@ -25,7 +25,6 @@ When creating a secret, you can make it available for any deployment within a pr
 
 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?
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 87a0a8177e..87476fd20c 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
@@ -1,7 +1,6 @@
 ---
 title: Adding ConfigMaps
 weight: 
-draft: true
 ---
 
 ConfigMaps store general configuration information for an application, such as configuration files, command-line arguments, environment variables, etc. ConfigMaps accept key value pairs in common string formats, like config files or JSON blobs. Add ConfigMaps to your Rancher workspaces so that you can add them to your workloads later. For more information on ConfigMaps, see the official [Kubernetes Documentation: Using ConfigMap](https://kubernetes-v1-4.github.io/docs/user-guide/configmap/).
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
index 1ecc50ba43..ab5a9f56bd 100644
--- a/content/rancher/v2.x/en/tasks/projects/add-registries/_index.md
+++ b/content/rancher/v2.x/en/tasks/projects/add-registries/_index.md
@@ -1,7 +1,6 @@
 ---
 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.
diff --git a/content/rancher/v2.x/en/tasks/projects/add-ssl-certificates/_index.md b/content/rancher/v2.x/en/tasks/projects/add-ssl-certificates/_index.md
index 674e2e0d6d..a9dfeaac88 100644
--- a/content/rancher/v2.x/en/tasks/projects/add-ssl-certificates/_index.md
+++ b/content/rancher/v2.x/en/tasks/projects/add-ssl-certificates/_index.md
@@ -1,7 +1,6 @@
 ---
 title: Adding SSL Certificates
 weight: 
-draft: true
 ---
 When you create an ingress within Rancher/Kubernetes, you must provide it with a TLS private key and certificate, which are used to encrypt and decrypt communications that come through the ingress. You can make certificates available for ingress use by navigating to its project or namespace, and then uploading the certificate.