Skip to content

Fix grammar error in Actions support documentation: "are be formatted" #42554

Closed

Description

@Nsanjayboruds

Code of Conduct

What article on docs.github.com is affected?

Location

File: content/actions/how-tos/get-support.md
Line: 40
URL: https://docs.github.com/en/actions/how-tos/get-support

Description

There's a grammatical error with a duplicate verb on line 40. The sentence contains "are be formatted" which should be "are formatted".

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

In the section about providing runner logs to support, there's a grammatical error.

Current text:
"Self-hosted runner log file names are be formatted: Runner_YYYY####-xxxxxx-utc.log and Worker_YYYY####-xxxxxx-utc.log."

Should be:
"Self-hosted runner log file names are formatted: Runner_YYYY####-xxxxxx-utc.log and Worker_YYYY####-xxxxxx-utc.log."

Why: The phrase "are be formatted" contains a double verb (grammatical error). It should simply be "are formatted".

Use case: This improves readability and professionalism of the documentation. Grammar errors can confuse readers, especially non-native English speakers.

Expected outcome: Correct, clear sentence that's easier to read and understand.

Additional information

This is located in the file content/actions/how-tos/get-support.md. I'm happy to submit a PR to fix this.

Activity

  1. added
    contentThis issue or pull request belongs to the Docs Content team
    on Jan 25, 2026
  2. added
    triageDo not begin working on this issue until triaged by the team
    on Jan 25, 2026
  3. nguyetdth1212-commits commented on Jan 26, 2026

    @nguyetdth1212-commits
  4. Nsanjayboruds commented on Jan 27, 2026

    @Nsanjayboruds
    ContributorAuthor

    i fix it #42555

  5. bugmaker00 commented on Jan 27, 2026

    @bugmaker00
  6. Nsanjayboruds commented on Jan 27, 2026

    @Nsanjayboruds
    ContributorAuthor

    I’ve fixed this issue in PR #42555

  7. Sharra-writes commented on Jan 30, 2026

    @Sharra-writes
    Contributor

    @Nsanjayboruds The PR you made for this was fine. Would you like to reopen it so I can approve it? The checks failing was nothing to do with you, we're just trying to make them more efficient and it usually breaks them temporarily.

  8. added
    github_actionsPull requests that update GitHub Actions content
    and removed
    triageDo not begin working on this issue until triaged by the team
    on Jan 30, 2026
  9. Nsanjayboruds commented on Feb 1, 2026

    @Nsanjayboruds
    ContributorAuthor

    hey @Sharra-writes
    Thanks for letting me know!
    I’ll go ahead and open a new PR #42674 so it can be reviewed and approved.
    Appreciate the clarification about the checks and thanks for your help 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    contentThis issue or pull request belongs to the Docs Content teamgithub_actionsPull requests that update GitHub Actions content

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions