Skip to content

Commit

Permalink
fix typos (#4288)
Browse files Browse the repository at this point in the history
  • Loading branch information
xiaobei0715 authored Jan 7, 2025
1 parent 8d189c2 commit 780a61d
Show file tree
Hide file tree
Showing 5 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion docs/src/consensus/fork-generation.md
Original file line number Diff line number Diff line change
Expand Up @@ -110,7 +110,7 @@ so a validator observing `E3` and `E3'` can slash L3 and safely choose `x` for
that slot. Once a validator commits to a fork, other forks can be discarded
below that tick count. For any slot, validators need only consider a single "has
entries" chain or a "ticks only" chain to be proposed by a leader. But multiple
virtual entries may overlap as they link back to the a previous slot.
virtual entries may overlap as they link back to the previous slot.

#### Time Division

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ title: instruction introspection
## Problem

Some smart contract programs may want to verify that another Instruction is present in a
given Message since that Instruction could be be performing a verification of certain data,
given Message since that Instruction could be performing a verification of certain data,
in a precompiled function. (See secp256k1_instruction for an example).

## Solution
Expand Down
2 changes: 1 addition & 1 deletion docs/src/implemented-proposals/repair-service.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ Each validator advertises separately on gossip the various parts of an

- The `stash`: An epoch-long compressed set of all completed slots.
- The `cache`: The Run-length Encoding (RLE) of the latest `N` completed
slots starting from some some slot `M`, where `N` is the number of slots
slots starting from some slot `M`, where `N` is the number of slots
that will fit in an MTU-sized packet.

`Epoch Slots` in gossip are updated every time a validator receives a
Expand Down
2 changes: 1 addition & 1 deletion docs/src/proposals/ledger-replication-to-implement.md
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,7 @@ We have the following constraints:

in CBC mode with `NUM_CHACHA_ROUNDS` of encryption.

6. The archiver initializes a chacha rng with the a signed recent PoH value as
6. The archiver initializes a chacha rng with the signed recent PoH value as

the seed.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ Let `remaining_set` be all other nodes with contact info not contained in
`epoch_set`.

If `epoch_set.len < 2*FANOUT` then we may randomly select up to
`2*FANOUT - epoch_set.len` nodes to to retransmit to from `remaining_set`.
`2*FANOUT - epoch_set.len` nodes to retransmit to from `remaining_set`.

## Receiving retransmitted shred

Expand Down

0 comments on commit 780a61d

Please sign in to comment.