The human readable name of the module is displayed in different ways in the user interface, like this:
This is not about the machine name, which is captcha, nor is its about the official name, which should probably remain to be upper cased as CAPTCHA.
An old discussion from 2007 about whether to use Captcha or CAPTCHA generally, also for the name is captcha, Captcha or CAPTCHA?.
But for consistency in the user interface, we should decide to use either CAPTCHA or Captcha everywhere, for example as in "Add a Captcha" or "Add a CAPTCHA".
To not introduce big changes, which might affect for example translations, the pragmatic solution is probably to use CAPTCHA in user interfaces, consistently.
Decide if we should use CAPTCHA or Captcha in the user interface generally, and update the code.
Active
2.0
User interface
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
So actually, with all that in mind and thinking more about it, we should probably streamline all non-machine name instances in the user interface to be "CAPTCHA", not "Captcha", for consistency and to align with the norm.
+1 ✅