Update config-intro.md

Author: michelle-luna

jekyll/_cci2/config-intro.md

@@ -130,7 +130,7 @@ The above two changes to the config significantly affect how you get work done.
 So far so good?  Let’s spend a moment on orchestration.  In this example, we will spend more time doing analysis than step-by-step modification.
 The CircleCI workflow model is based on the orchestration of predecessor jobs.  This is why the reserved word used for workflow definition is `requires.`  Jobs initiation is always defined in terms of the successful completion of prior jobs.  For example, a job vector such as [A, B, C] would be implemented with jobs B and C each requiring the job prior.  Job A would not have a requires block because it starts immediately. For example, job A starts immediately; B requires A; C requires B.
 
-In the example below, an event triggering a build will cause `Hello-World` to start immediately.  The remainder of the jobs will wait.  When `Hello-World` completes, both `I-Have-Code` and `Run-In-A-Container` will start.  That is because both `I-Have-Code` and `Run-In-A-Container` require `Hello-World` to complete successfully before they can start.  Next, the approval job called `Hold-For-Approval` will become available when both `I-Have-Code` and `Run-In-A-Container` complete.  The `Hold-For-Approval` job is slightly different from the others.  It represents a manual intervention to allow the workflow to continue.  While the workflow is waiting for a user (through the CircleCI UI or API) to approve the job, all state is preserved based on the original triggering event.  CircleCI understands that Approval jobs may take hours or even days before completing - although we suggest hours over days. Once `Hold-For-Approval` completes through a manual intervention, the final job `Now-Complete` will run.
+In the example below, an event triggering a build will cause `Hello-World` to start immediately.  The remainder of the jobs will wait.  When `Hello-World` completes, both `I-Have-Code` and `Run-With-Node` will start.  That is because both `I-Have-Code` and `Run-With-Node` require `Hello-World` to complete successfully before they can start.  Next, the approval job called `Hold-For-Approval` will become available when both `I-Have-Code` and `Run-With-Node` complete.  The `Hold-For-Approval` job is slightly different from the others.  It represents a manual intervention to allow the workflow to continue.  While the workflow is waiting for a user (through the CircleCI UI or API) to approve the job, all state is preserved based on the original triggering event.  CircleCI understands that Approval jobs may take hours or even days before completing - although we suggest hours over days. Once `Hold-For-Approval` completes through a manual intervention, the final job `Now-Complete` will run.
 
 All of the job names are arbitrary.  This allows you to create workflows as complex as you need while staying meaningful and clear to the next developer that reads the `config.yml`.