Fix miscellaneous errors in GitHub Actions / Reference / Workflow syntax

[gsrohde]

What article on docs.github.com is affected?

https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions

What part(s) of the article would you like to see updated?

1. Under the section jobs.<job_id>.steps.run in the subsection Exit codes and error action preference: Under the bullet point for cmd, the second item starts out "cmd.exe will exit with the error level of the last program it executed, and it will and return the error code to the runner." The second "and" is extraneous and should be deleted.

2. The last sentence in the section jobs.<job_id>.steps.with.entrypoint reads "The entrypoint keyword is meant to use with Docker container actions, but you can also use it with JavaScript actions that don't define any inputs." "to use" should be changed to "to be used".

3. This is a general comment about the syntax of the syntax article: Since, for the most part, the YAML used in workflow files can be considered a form of JSON, it indeed makes some sense to use JavaScript-like syntax to refer to the parts of the YAML file. For example, jobs.<job_id>.timeout-minutes clearly refers to the value corresponding to the timeout-minutes key in the hash value corresponding to the <job_id> key in the hash value corresponding to the jobs key, and this is precisely how you would refer to it in JavaScript. Where it gets confusing is in notations such as jobs.<job_id>.steps.timeout-minutes. This is because the value corresponding to the steps key is not another hash but rather an array (of steps). Using the dot notation obscures the fact that in this case, timeout-minutes applies to a particular step and doesn't apply to the set of steps as a whole. It would be clearer to write something like jobs.<job_id>.steps[n].timeout-minutes to make clear that timeout-minutes applies only to some particular step n and not to all steps. The [n] here stands in for any step in the sequence analogously to the way <job_id> stands in for some particular key in the jobs hash.

[janiceilene]

Thanks so much for opening an issue @gsrohde! I'll triage it for the right folks to take a look 👀

[lucascosti]

Thanks for pointing these out, @gsrohde!

1. and 2. should be easy fixes for anyone to pick up.

For 3., I do understand your description of the issue, but I think we'll need to discuss this one in the content team to maybe see if it's practical to implement for the improvement it would create. At the moment there are a lot of existing docs and product links to those sections, and if we were to update all the steps.<something> headings, those links everywhere will also need to be updated.

[janiceilene]

I'm going to add a good first issue label on this one and anyone is welcome to open a PR to fix 1 & 2 only 💛

[JBryceOrtiz]

I will fix 1 & 2 now!