Use merge consistently

This commit is contained in:
Paul Hauner 2022-03-02 19:03:06 +11:00
parent f071931e46
commit bf25d323fc
No known key found for this signature in database
GPG Key ID: 5E2CFF9B75FA63DF
1 changed files with 2 additions and 2 deletions

View File

@ -118,8 +118,8 @@ following are true:
In effect, there are restrictions on when a *merge block* can be optimistically In effect, there are restrictions on when a *merge block* can be optimistically
imported. The merge block is the first block in any chain where imported. The merge block is the first block in any chain where
`is_execution_block(block) == True`. Any descendant of a transition block may `is_execution_block(block) == True`. Any descendant of a merge block may be
be imported optimistically at any time. imported optimistically at any time.
*See [Fork Choice Poisoning](#fork-choice-poisoning) for the motivations behind *See [Fork Choice Poisoning](#fork-choice-poisoning) for the motivations behind
these conditions.* these conditions.*