Fix inconsistent heading indentation (stray leading space on 4 headings) - #6
Open
simeon-kepp wants to merge 1 commit into
Open
Fix inconsistent heading indentation (stray leading space on 4 headings)#6simeon-kepp wants to merge 1 commit into
simeon-kepp wants to merge 1 commit into
Conversation
Four headings in README.md have a single leading space before the "###" ATX marker, unlike all other 99 headings in the document which start at column 0: - "MUST property names must be snake_case or camelCase [118]" - "MUST use same semantics for null and absent properties [123]" - "PUT" - "SHOULD use URL versioning [115]" GitHub's renderer tolerates up to 3 leading spaces on an ATX heading per CommonMark, so these still render correctly today - but the inconsistency shows up in stricter markdown linters/tooling and in diffs, and there's no reason for these four to differ from the other 99 headings in the same file. Purely whitespace, no wording changed. Co-authored-by: Laura Serna Gaviria <lsgaviria94@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Four headings in
README.mdhave a single stray leading space before the###marker, unlike all other 99 headings in the document (which start at column 0):MUST property names must be snake_case or camelCase [118]MUST use same semantics for null and absent properties [123]PUTSHOULD use URL versioning [115]GitHub tolerates up to 3 leading spaces on an ATX heading per CommonMark, so all four still render correctly today — this is a pure whitespace/consistency fix, not a rendering bug, and doesn't change any wording.
About us
We're Laura Serna Gaviria (Emergent Interaction Lab, Germany) and Simeon Kepp (RFI-IRFOS, Austria) — two of your neighbours to the north. We work on human–AI interaction research and API/systems engineering, and we've been reading through these guidelines closely for our own work, genuinely impressed that a federal government publishes something this thorough and this well-reasoned in the open. We love Switzerland, and this is a small, honest thank-you back — not a joke PR, just an actual fix we noticed while using the document for real.