From e914c558da6c9d01871c957c8908e85461b76529 Mon Sep 17 00:00:00 2001 From: Nicolas Hoizey Date: Thu, 5 Jan 2023 10:49:12 +0100 Subject: [PATCH] Fixing a typo MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I don't think the past tense should be used here, even if the example just after doesn't apply this recommendation and uses lower camel case… --- .../creating-actions/metadata-syntax-for-github-actions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 6fd1dab0b3..7856709dde 100644 --- a/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -39,7 +39,7 @@ Action metadata files use YAML syntax. If you're new to YAML, you can read "[Lea ## `inputs` -**Optional** Input parameters allow you to specify data that the action expects to use during runtime. {% data variables.product.prodname_dotcom %} stores input parameters as environment variables. Input ids with uppercase letters are converted to lowercase during runtime. We recommended using lowercase input ids. +**Optional** Input parameters allow you to specify data that the action expects to use during runtime. {% data variables.product.prodname_dotcom %} stores input parameters as environment variables. Input ids with uppercase letters are converted to lowercase during runtime. We recommend using lowercase input ids. ### Example: Specifying inputs