Skip to content

Editorial (Normative): "Web" to "web", harmonise when SC is upper or lowercase #4461

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 24 commits into
base: main
Choose a base branch
from

Conversation

patrickhlauke
Copy link
Member

@patrickhlauke patrickhlauke commented Jun 22, 2025

Split out normative-only version of #4428

Relates to #4427

Changes unnecessary capitalisation of "Web" to "web", a few straggler cases where lowercase "success criterion/criteria" was referring to specific ones, where we do want title case

…s criteria"

Also includes:

* change "web based" to "web-based"
* change "Web Unit" to "web unit"
* change "Web Page" to "web page" (where appropriate)

Closes #4427
Per @bruce-usab's comment, removed one instance altogether as it was unnecessary, and replaced another with "set of web pages" which is the correct term here that matches the wording of the related SC
Copy link

netlify bot commented Jun 22, 2025

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit b08f56f
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/68593824d8776c0008889c63
😎 Deploy Preview https://deploy-preview-4461--wcag2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@patrickhlauke patrickhlauke changed the title Patrickhlauke web web normative Editorial: "Web" to "web", harmonise when SC is upper or lowercase Jun 22, 2025
@patrickhlauke patrickhlauke changed the title Editorial: "Web" to "web", harmonise when SC is upper or lowercase Editorial (Normative): "Web" to "web", harmonise when SC is upper or lowercase Jun 22, 2025
@kfranqueiro
Copy link
Contributor

The content in _includes should remain in #4428; that is used for informative docs, not TR space.

@patrickhlauke
Copy link
Member Author

@kfranqueiro sigh ... done

@mbgower mbgower added ErratumRaised Potential erratum for a Recommendation Normative labels Jun 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Editorial ErratumRaised Potential erratum for a Recommendation Normative
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants