Follow-up from "Explain downloading patches and diffs from MRs"

In a merge request, Code > Email patches is confusing. Consider renaming "Email patches" to something more obvious / descriptive of the function.

Awareness: @annabeldunstone

---

the The following discussion from !104647 (merged) should be addressed:

@aqualls: When I selected Code > Email patches [on a merge request] I was confused because I interpreted email as a verb, as in "email these patches to me." That led me to read up on the git am command. https://git-scm.com/docs/git-am Is this understood by most people and I should be patted on the head and sent off with a cookie, or is this language confusing for others too?

@markrian: I already knew about git am's connection to email (emailing patches being the way Linux is developed), and I still found this confusing 😄

It reads as a verb 🤷 I'd suggest we either tweak this to something like Patches for email, or just simply Patches.

Related issues

• Related to Document the .diff feature in merge requests (#382622 - closed) which spawned some docs work
• Related to Explain downloading patches and diffs from MRs (!104647 - merged) where I documented the diff features.