-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update node syncing content [Fixes #12003] #13201
Conversation
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
I think I need to update Snap further for better detail: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @m4sterbunny! Left a few comments/requests to clean things up then think we can get this in soon
Quick housekeeping notes... "12003(docs):fixes as per issue" Issue Names: I see you're referencing an issue (12003). By convention, we'll place Issue Body: Try to use the default template to get started. Under a Thanks! |
as per review Co-authored-by: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
as per review Co-authored-by: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
as per review Co-authored-by: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
as per review Co-authored-by: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
updates heading level as per review BUT need to verify did I introduce the heading that impacted
I think I resolved all @wackerow PTAL |
as per review Co-authored-by: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks a lot @m4sterbunny! Bringing in
@all-contributors please add @m4sterbunny for content |
I've put up a pull request to add @m4sterbunny! 🎉 |
Description
Execution client summary table did not link users to sync types
Sync types were poorly identified and incomplete
Small proofs including:
Issue
Fixes #12003