Currently, when a user on mobile attempts to edit a protected page they don't have permission to edit, they're shown the message This page is protected to prevent vandalism. (mobile-frontend-editor-disabled)

However, from the software's perspective, it doesn't know why the page has been protected (at least, not without parsing the protection log), only that it is. It therefore seems potentially a little misleading to always state that the reason for a page's protection is "to prevent vandalism", when the actual reason for the page being protected could be different from that (e.g. an edit war, addition of unsourced content, sockpuppetry, etc.). It's probably also worth noting that some projects use a very specific definition of 'vandalism' - e.g., the English Wikipedia defines it as behaviour "deliberately intended to obstruct or defeat the project's purpose".

Doing some Phabricator-archaeology, I found that this was brought up briefly in T95305#1322596 in 2015. The current wording of this message appears to originate from 30917ee in December 2013; and its initial wording in July 2013 (from cb55047) appears to have been You are not allowed to edit this page.