Fix bogus indentation in RDF spec #498
Merged
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.
This PR fixes a small formatting issue in the recently merged RDF specification.
The Markdown implementation used by Mkdocs only recognizes nested lists if the nested list items are indented by precisely 4 spaces (or a tab character) compared to the parent list item.
This was not caught prior to merging because I (and likely anyone who reviewed the PR) relied on GitHub’s Markdown preview, but the Github-flavoured Markdown is slightly different from the Mkdocs Markdown. Therefore the PR also amends the contributing documentation to recommend that documentation editors run
make servelocally.