Typo fix: Lowercase m for Minimum

[frankieroberto]

Spotted this minor inconsistency.

[netlify]

✅ You can preview this change here:

Built without sensitive environment variables

Name	Link
🔨 Latest commit	a32505a
🔍 Latest deploy log	https://app.netlify.com/sites/govuk-design-system-preview/deploys/65b914839f8c1c0008b7db61
😎 Deploy Preview	https://deploy-preview-3498--govuk-design-system-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[owenatgov]

Easy peasy. Thanks Frankie! Will wait for a 2nd approval so that we're following due process.

[querkmachine]

Now I'm actually looking I can see a few places where we've upper-capped "Minimum", like the colours page, password pattern and help users create accounts.

Not to say this PR should blam them all, but probably worth a systematic look at the content now that this has been brought up.

[frankieroberto]

(just spotted this whilst watching the show-and-tell! 🙌 )

[36degrees]

Just a thought – WCAG seems to treat the different success criterion as proper nouns and title cases them everywhere in their own guidance. Should we follow suit instead?

It may make it clearer that we're referring to a specific thing rather than e.g the general concept of 'redundant entry'

[36degrees]

As an alternative option, I've raised another PR which consistently uses proper nouns for the success criteria – #3555

[calvin-lau-sig7]

Thanks all!

Currently I'd stuck with sentence case as we've done here. E.g.:

Focus not obscured (minimum)

Style guide on capitalisation says to "Always use sentence case, even in page titles and service names", which I'd probably put these criteria down as.

[frankieroberto]

@calvin-lau-sig7 @owenatgov can you approve the workflow, and then I think this can be merged?