fix: MIP-8 exponent rendering and code block label - #80
Merged
keone merged 1 commit intoAug 24, 2026
Conversation
mmv08
requested review from
Baltoli,
QEDK,
keone,
kjcamann and
pdobacz
as code owners
August 24, 2026 16:10
keone
approved these changes
Aug 24, 2026
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
2 participants
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.
Two small fixes on the MIP-8 page. The "after" screenshots come from a local Jekyll build of this branch.
1. Powers of two showed as broken text
The page wrote
2**256and2**249in plain text, so Markdown read the**as bold marks. In "Security Considerations" this made half a paragraph bold and hid the exponents. In "Rationale" it showed raw asterisks. Both now use<sup>tags and show as real powers of two.Security Considerations — before:
After:
Rationale — before:
After:
2. Code block was marked as Python
The ISMC commit code block was marked as Python, but it is plain pseudocode. The text above it and the code fence now say so, and the block no longer gets wrong Python highlighting.
Before:
After: