Several formatting fixes and improvements #696
Merged
Conversation
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
HolgerKnublauch
requested review from
recalcitrantsupplant,
robert-david and
simonstey
recalcitrantsupplant
approved these changes
Dec 10, 2025
TallTed
reviewed
Dec 15, 2025
| <aside class="example" title="A list expression that is used to enumerate the values of a shnex:remove expression."> | ||
| <div class="shapes-graph"> | ||
| <div class="turtle"> | ||
| <aside class="example" title="A list expression that is used to enumerate the values of a shnex:remove expression."> |
Member
There was a problem hiding this comment.
It's weird that some of these titles end with ., while most do not. I prefer the . endings, but I won't block if all are removed. Consistency is what I'm looking for.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is an editorial follow-up to recent merges to clean up formatting (often just indentation) but also some incorrect nesting of HTML tags that caused the TOC builder to fail.