Fix workflow in Actions 'Introductions' article (github#8141)

content/actions/learn-github-actions/introduction-to-github-actions.md

@@ -77,6 +77,8 @@ You can create an example workflow in your repository that automatically trigger
         steps:
           - uses: actions/checkout@v2
           - uses: actions/setup-node@v2
+            with:
+              node-version: '14'
           - run: npm install -g bats
           - run: bats -v
     ```
@@ -171,10 +173,12 @@ To help you understand how YAML syntax is used to create a workflow file, this s
 
   ```yaml
       - uses: actions/setup-node@v2
+        with:
+          node-version: '14'
   ```
 </td>
 <td>
-  This action installs the <code>node</code> software package on the runner, giving you access to the <code>npm</code> command.
+  This step uses the <code>actions/setup-node@v2</code> action to install the specified version of the <code>node</code> software package on the runner, which gives you access to the <code>npm</code> command.
 </td>
 </tr>
 <tr>

content/actions/reference/workflow-syntax-for-github-actions.md

@@ -640,15 +640,15 @@ Actions are either JavaScript files or Docker containers. If the action you're u
 ### Example: Using versioned actions
 
 ```yaml
-steps:    
+steps:
   # Reference a specific commit
-  - uses: actions/setup-node@c46424eee26de4078d34105d3de3cc4992202b1e
+  - uses: actions/checkout@a81bbbf8298c0fa03ea29cdc473d45769f953675
   # Reference the major version of a release
-  - uses: actions/setup-node@v2
+  - uses: actions/checkout@v2
   # Reference a specific version
-  - uses: actions/setup-node@v2.2.0
+  - uses: actions/checkout@v2.2.0
   # Reference a branch
-  - uses: actions/setup-node@main
+  - uses: actions/checkout@main
 ```
 
 ### Example: Using a public action