Insights remediations quickstart QE review edits (#344)

Fix QE testing comments

Author: michelle-purcell

docs/quickstarts/insights-remediate-plan-create/insights-remediate-plan-create.yml

@@ -18,12 +18,12 @@ spec:
 
   # Optional.
   description: |-
-    Create and execute a remediation plan to resolve an issue detected by the Insights Advisor service.
+    Create and execute a remediation plan to resolve an issue detected by the Insights advisor service.
   introduction: |-
-    In this quick start, from the console, you will create and execute a remediation plan on one or more systems to resolve an issue that the Insights Advisor service recommends remediating.
+    In this quick start, from the Red Hat Hybrid Cloud Console, you will create and execute a remediation plan on one or more systems to resolve an issue that the Insights advisor service recommends remediating.
     <br>
     <br>
-    The Advisor service assesses and monitors the health of your Red Hat Enterprise Linux (RHEL) infrastructure and provides recommendations to address availability, stability, performance, and security issues. 
+    The advisor service assesses and monitors the health of your Red Hat Enterprise Linux (RHEL) infrastructure and provides recommendations to address availability, stability, performance, and security issues. 
     Remediation plans use Ansible playbooks to remediate issues on systems in your Red Hat Enterprise Linux (RHEL) infrastructure. 
     <br>
     <br>
@@ -36,7 +36,7 @@ spec:
   tasks:
     - title: Create a Remediation plan
       description: |-
-        Pick an issue that the Advisor service has recommended remediating on a system in your RHEL infrastructure, and then create a remediation plan to execute.
+        Pick an issue that the advisor service has recommended remediating on a system in your RHEL infrastructure, and then create a remediation plan to execute.
 
         1. On the left navigation bar, go to **Operations** > **Advisor** > **Recommendations**. 
         2. Scroll through the list of recommendations and pick one whose **Remediation type** is set to **Playbook**. 
@@ -51,7 +51,7 @@ spec:
         6. With the help of the wizard, create a remediation plan named **_My-Plan-1_** and ensure you select the **Create a playbook** option.
         7. Click **Next**.
         8. Review the default selections under **Review systems** and **Remediation review**, adjust them as needed, and then click **Submit**.
-        9. Click **Open My-Plan-1** to view your new plan.
+        9. To view your new plan, click **Return to application**, and then go to **Automation Toolkit** > **Remediation Plans** > **My-Plan-1**.
       review:
         instructions: |-
           - Were you presented with the details and status of the **_My-Plan-1_** remediation plan that you just created?
@@ -83,21 +83,21 @@ spec:
             For more information, see [Remote Host Configuration and Management](https://docs.redhat.com/en/documentation/red_hat_insights/1-latest/html/remote_host_configuration_and_management/index).
             
            </details>
-        3. For each system that you want to remediate from within Insights, ensure you have enabled the Remote Host Configuration client (`rhc connect`{{copy}}) and have a direct connection to the RHEL system:
+        3. For each system that you want to remediate from within Insights, ensure you have enabled the Remote Host Configuration client (`rhc connect`) and have a direct connection to the RHEL system:
            <details>
             <summary><span style="color:#0066CC">&nbspNeed help connecting to a RHEL system?</span></summary>
             - Log on as a user with root access to the RHEL system, and execute the following commands: 
             <ol type="a">
               <li> `dnf install rhc rhc-worker-playbook`{{copy}}</li>
               <li> `dnf upgrade rhc rhc-worker-playbook`{{copy}}</li>
-              <li> `grep mqtt-reconnect-delay /etc/rhc/config.toml || echo 'mqtt-reconnect-delay = "10s"' >> /etc/rhc/config.toml rhc connect`{{copy}}</li>
-            </ol>
-            - After executing the commands, check the **Connection Status** column in the **Systems** tab of your remediation plan. The status should indicate that the system is **Connected**.
+              <li> `grep mqtt-reconnect-delay /etc/rhc/config.toml || echo 'mqtt-reconnect-delay = "10s"' >> /etc/rhc/config.toml`{{copy}}</li>
+              <li> `rhc connect`{{copy}}</li>
+          </ol>
+            - After executing the commands, refresh the plan details page and then check the **Connection Status** column in the **Systems** tab of your remediation plan. The status should indicate that the system is **Connected**.
           </details>
-        4. Go to **Automation Toolkit** > **Remediation plans** and open the remediation plan details for “My-Plan-1”. The execution readiness check will automatically run again.
       review:
         instructions: |-
-          - When the execution readiness check has rerun, is the **Execute** button now enabled?
+          - When the execution readiness check reruns, is the **Execute** button now enabled?
         failedTaskHelp: Review the remediation plan settings again and adjust the configuration as needed. [Learn more ...](https://docs.redhat.com/en/documentation/red_hat_insights/1-latest/html/red_hat_insights_remediations_guide_with_fedramp/creating-managing-playbooks_red-hat-insights-remediation-guide#viewing-archived-remediation-playbook_creating-managing-playbooks)<i class="pf-icon [fa-external-link-alt]"></i>
     - title: Execute a remediation plan
       description: |-