Approved, as the workflow doesn't appear to be used anywhere: but is there a reason content and translated-content have their own workflows instead of using this one?

Generally, translated-content has a different setup. In particular, it requires a content checkout, so this workflow wouldn't work as is.

On the other hand, based on https://github.com/search?q=org%3Amdn+%2Fmarkdownlint-cli%2F+path%3A.github%2Fworkflows++NOT+is%3Aarchived&type=code, only translated-content seems to still have a markdown-lint workflow, whereas content runs it as part of the pr-check-lint_content workflow.

Overall, although content and translated-content already share most of the linting dependencies and scripts, the workflows seem to differ enough that it isn't straightforward to unify, and the added complexity just probably isn't worth it.

PS: If we had more repos with a single translated locale, it might be worth to extract those though.