From 251d79c39cfd24b59e322caf7a74ad07ce3d57ce Mon Sep 17 00:00:00 2001
From: DJ Adams <qmacro@gmail.com>
Date: Mon, 18 Jan 2021 05:02:46 +0000
Subject: [PATCH] Include 'shell command' as a possible step task (#2211)

Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>
---
 .../learn-github-actions/introduction-to-github-actions.md      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/actions/learn-github-actions/introduction-to-github-actions.md b/content/actions/learn-github-actions/introduction-to-github-actions.md
index c84f11c6b4..3d56d7db0c 100644
--- a/content/actions/learn-github-actions/introduction-to-github-actions.md
+++ b/content/actions/learn-github-actions/introduction-to-github-actions.md
@@ -147,7 +147,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s
   ```
 </td>
 <td>
-  Groups together all the steps that run in the <code>check-bats-version</code> job. Each line nested under this section is a separate action.
+  Groups together all the steps that run in the <code>check-bats-version</code> job. Each item nested under this section is a separate action or shell command.
 </td>
 </tr>
 <tr>