From 46cc8e018589248d4e6510b42ec18e0e5d5621d1 Mon Sep 17 00:00:00 2001 From: Rawal27 Date: Sat, 26 Sep 2026 16:55:35 +0530 Subject: [PATCH] correct terminology for workflows and action Signed-off-by: Rawal27 --- .../actions/reference/workflows-and-actions/workflow-syntax.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/reference/workflows-and-actions/workflow-syntax.md b/content/actions/reference/workflows-and-actions/workflow-syntax.md index 22fd3cf022c0..5f916e52265e 100644 --- a/content/actions/reference/workflows-and-actions/workflow-syntax.md +++ b/content/actions/reference/workflows-and-actions/workflow-syntax.md @@ -684,7 +684,7 @@ We strongly recommend that you include the version of the action you are using b Some actions require inputs that you must set using the [`with`](#jobsjob_idstepswith) keyword. Review the action's README file to determine the inputs required. -Actions are either JavaScript files or Docker containers. If the action you're using is a Docker container you must run the job in a Linux environment. For more details, see [`runs-on`](#jobsjob_idruns-on). +Actions can be JavaScript, composite, or Docker container actions. If the action you're using is a Docker container you must run the job in a Linux environment. For more details, see [`runs-on`](#jobsjob_idruns-on). ### Example: Using versioned actions