From 8a4007dfd0cffafa0ea4362349a450e68ff3a435 Mon Sep 17 00:00:00 2001
From: Logan Kilpatrick <23kilpatrick23@gmail.com>
Date: Sun, 17 Jan 2021 21:34:59 -0800
Subject: [PATCH] Update workflow-syntax-for-github-actions.md (#2353)

---
 content/actions/reference/workflow-syntax-for-github-actions.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/actions/reference/workflow-syntax-for-github-actions.md b/content/actions/reference/workflow-syntax-for-github-actions.md
index 1ebfc4e8d5..4030b05950 100644
--- a/content/actions/reference/workflow-syntax-for-github-actions.md
+++ b/content/actions/reference/workflow-syntax-for-github-actions.md
@@ -705,7 +705,7 @@ You can set the `shell` value to a template string using `command […options] {
 For built-in shell keywords, we provide the following defaults that are executed by {% data variables.product.prodname_dotcom %}-hosted runners. You should use these guidelines when running shell scripts.
 
 - `bash`/`sh`:
-  - Fail-fast behavior using `set -e o pipefail`: Default for `bash` and built-in `shell`. It is also the default when you don't provide an option on non-Windows platforms.
+  - Fail-fast behavior using `set -eo pipefail`: Default for `bash` and built-in `shell`. It is also the default when you don't provide an option on non-Windows platforms.
   - You can opt out of fail-fast and take full control by providing a template string to the shell options. For example, `bash {0}`.
   - sh-like shells exit with the exit code of the last command executed in a script, which is also the default behavior for actions. The runner will report the status of the step as fail/succeed based on this exit code.