diff --git a/content/actions/creating-actions/setting-exit-codes-for-actions.md b/content/actions/creating-actions/setting-exit-codes-for-actions.md
index 5a65cac300..b2136f6b9d 100644
--- a/content/actions/creating-actions/setting-exit-codes-for-actions.md
+++ b/content/actions/creating-actions/setting-exit-codes-for-actions.md
@@ -23,7 +23,7 @@ type: 'how_to'
 Exit status | Check run status | Description
 ------------|------------------|------------
 `0` | `success` | The action completed successfully and other tasks that depends on it can begin.
-Nonzero value | `failure` | Any other exit code indicates the action failed. When an action fails, all concurrent actions are canceled and future actions are skipped. The check run and check suite both get a `failure` status.
+Nonzero value (any integer but 0)| `failure` | Any other exit code indicates the action failed. When an action fails, all concurrent actions are canceled and future actions are skipped. The check run and check suite both get a `failure` status.
 
 ### Setting a failure exit code in a JavaScript action
 
@@ -43,13 +43,11 @@ For more information, see "[Creating a JavaScript action](/articles/creating-a-j
 
 If you are creating a Docker container action, you can set a failure exit code in your `entrypoint.sh` script. For example:
 
-{% raw %}
 ```
 if <condition> ; then
   echo "Game over!"
   exit 1
 fi
 ```
-{% endraw %}
 
 For more information, see "[Creating a Docker container action](/articles/creating-a-docker-container-action)."