Update lab with new wording

Why is this change being made?

This MR fixes an issue with the lab where the wording does not match up.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Division: If the update affects your division, share the MR in your division Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Update lab with new wording

---

content/handbook/customer-success/professional-services-engineering/education-services/gitlabcicdhandsonlab5.md

@@ -176,7 +176,7 @@ Variables in GitLab CI/CD have a precedence, which means variables at a higher '
 
     > This is a project level variable, meaning it is accessible only inside the current project.
 
-1. Setting variables does not trigger a pipeline run, so click **Build > Pipelines** in the left navigation pane, click the **Run Pipeline** button, and click the second **Run Pipeline** button.
+1. Setting variables does not trigger a pipeline run, so click **Build > Pipelines** in the left navigation pane, click the **New Pipeline** button, and click the  **Run Pipeline** button.
 
 1. Click on the widget for the `environment variables` job from your running pipeline and verify the variables and their values are correctly displayed in the job output.