diff --git a/content/rancher/v2.x/en/concepts/catalogs/_index.md b/content/rancher/v2.x/en/concepts/catalogs/_index.md
index 2fa95c56b5f..de634ca76f6 100644
--- a/content/rancher/v2.x/en/concepts/catalogs/_index.md
+++ b/content/rancher/v2.x/en/concepts/catalogs/_index.md
@@ -54,7 +54,7 @@ The following table lists each file and sub-directory found in a Rancher chart d
 		</tr>
 		<tr>
 			<td> </td>
-			<td> <code>add-readme</code></td>
+			<td> <code>app-readme</code></td>
 			<td> Rancher Specific: Text displayed within Rancher.</td>
 		</tr>
 		<tr>
@@ -103,7 +103,7 @@ This reference contains variables that you can use in `questions.yml`.
 
 | Variable  | Type | Required | Description |
 | ------------- | ------------- | --- |------------- |
-| 	variable          | string  | true    |  define the variable name specified in the `values.yml`file, using `foo.bar` for nested object. |
+| 	variable          | string  | true    |  define the variable name specified in the `values.yml` file, using `foo.bar` for nested object. |
 | 	label             | string  | true      |  define the UI label. |
 | 	description       | string  | false      |  specify the description of the variable.|
 | 	type              | string  | false      |  default to `string` if not specified (current supported types are string, boolean, int, enum, password, storageclass and hostname).|
@@ -121,4 +121,4 @@ This reference contains variables that you can use in `questions.yml`.
 | 	show_if           | string      | false  | show current variable if conditional variable is true, for example `show_if: "serviceType=Nodeport"` |
 | 	show\_subquestion_if |  string  | false     | show subquestions if is true or equal to one of the options. for example `show_subquestion_if: "true"`|
 
-**subquestions**: `subquestions[]` cannot contain `subquestions` or `show_subquestions_if` keys, but all other keys in the above table are supported. 
+>**Note:** `subquestions[]` cannot contain `subquestions` or `show_subquestions_if` keys, but all other keys in the above table are supported.
diff --git a/content/rancher/v2.x/en/tasks/projects/launch-a-catalog-app/_index.md b/content/rancher/v2.x/en/tasks/projects/launch-a-catalog-app/_index.md
index a913466fe05..912d092d279 100644
--- a/content/rancher/v2.x/en/tasks/projects/launch-a-catalog-app/_index.md
+++ b/content/rancher/v2.x/en/tasks/projects/launch-a-catalog-app/_index.md
@@ -3,4 +3,30 @@ title: Launching a Catalog App
 weight: 
 draft: true
 ---
-Coming Soon
+
+1. From the **Global** view, open the project that you want to deploy to.
+
+2. From the main menu, choose **Catalog Apps**. Then click **Launch**.
+
+3. Click **Launch**.
+
+4. Find the app that you want to launch, and then click **View Now**.
+
+5. Under **Configuration Options** enter a **Name**. By default, this name is also used to create a Kubernetes namespace for the application.
+ 
+    * If you would like to change the **Namespace**, click **Customize** and enter a new name
+    * If you want to use a different namespace that already exists, click **Customize**, and then click **Use an existing namespace**. Choose a namespace from the list.
+
+6. Select a **Template Version**.
+
+7. Optional: Add answers to the deployment. Click **Add Answers** to add key value pairs.
+
+    * For native Helm charts, answers are provided as key value pairs in the **Answers** section.
+    * Keys and values are available within the **Detailed Descriptions** accordion.
+
+8. Review the files in **Preview**. When you're satisfied, click **Launch**
+
+**Result**: Your application is deployed to your chosen namespace. You can view the application status from the project's:
+
+- **Workloads** view
+- **Catalog Apps** view