Fix a typo#177
Closed
pavlenex wants to merge 1 commit into
Closed
Conversation
This was referenced Feb 6, 2026
Closed
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.
Same explanation as in #176
PLEASE DO NOT MERGE
This PR fixes a small typo.
I will be sending several small PR typo fixes in this repo, as part of the new website PR stratum-mining/stratumprotocol.org#300
The new website, just like the current one uses sv2-specs repo as a submodule, and whenever there's a marge in this repo, it SHOULD trigger a workflow which updates the submodule and rebuilds the website, so we always have stratumprotocol.com/specification page 1:1 as sv2-specs repo.
I'll be making several smaller PR's so we can test if workflows work good, will give green light when these are good to go one by one.