Formatting and Wording fixes for #0009 Message Passing#125
Merged
Conversation
| ## Inbox | ||
|
|
||
| Again this will be one per MPID (owner), held on the MpidManagers, and synchronised by them at churn events. | ||
| Again this will be one per MPID (owner), held on the `MpidManager`̨s, and synchronised by them at churn events. |
Contributor
Author
There was a problem hiding this comment.
indeed. fixing that right away.
Contributor
|
@Ligthyear thanks again! |
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.
Going through the RFC #9 I made a few formatting fixes. Also added another sentence that explains how the cryptographic signature in the header is calculated (derived from the code mentioned later).
This change is