Skip to content

Commit ba5e193

Browse files
authored
chore(docs): minor typo fixes (#13187)
chore: fix typos
1 parent 7dcccff commit ba5e193

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

documentation/misc/Builtin-actors_Development.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ By default, the itests framework will use the current latest network version. Ed
6565

6666
This means that once the latest bundle is installed and `build/builtin_actors_gen.go` has an entry with the actors `Version` you want to test, you can proceed to write an itest using the same format as the existing itests without needing to provide additional options.
6767

68-
Sometimes, testing the upgrade boundary, or before and after upgrades, is desireable. For example, wanting to test that a feature works one way (or doesn't exist) before an upgrade, and another way after the upgrade, your itest will need an "upgrade schedule" which matches what is currently found in [`chain/consensus/filcns/upgrades.go`](../../chain/consensus/filcns/upgrades.go). The `kit.UpgradeSchedule` function in the itests framework can be used to set this up.
68+
Sometimes, testing the upgrade boundary, or before and after upgrades, is desirable. For example, wanting to test that a feature works one way (or doesn't exist) before an upgrade, and another way after the upgrade, your itest will need an "upgrade schedule" which matches what is currently found in [`chain/consensus/filcns/upgrades.go`](../../chain/consensus/filcns/upgrades.go). The `kit.UpgradeSchedule` function in the itests framework can be used to set this up.
6969

7070
For example, to test a feature that is only available after the network upgrade to version 24, you would instantiate the itest ensemble with the following option to dictate that the network starts on NV23 (using `-1` as the `Height`) but will perform an upgrade at height 100 to NV24:
7171

storage/sealer/worker_local.go

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -630,11 +630,11 @@ func (l *LocalWorker) GenerateWinningPoSt(ctx context.Context, ppt abi.Registere
630630

631631
vanilla, err := l.storage.GenerateSingleVanillaProof(ctx, mid, s, ppt)
632632
if err != nil {
633-
rerr = multierror.Append(rerr, xerrors.Errorf("get winning sector:%d,vanila failed: %w", s.SectorNumber, err))
633+
rerr = multierror.Append(rerr, xerrors.Errorf("get winning sector:%d,vanilla failed: %w", s.SectorNumber, err))
634634
return
635635
}
636636
if vanilla == nil {
637-
rerr = multierror.Append(rerr, xerrors.Errorf("get winning sector:%d,vanila is nil", s.SectorNumber))
637+
rerr = multierror.Append(rerr, xerrors.Errorf("get winning sector:%d,vanilla is nil", s.SectorNumber))
638638
}
639639
vproofs[i] = vanilla
640640
}(i, s)

tools/stats/headbuffer/head_buffer.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ func NewHeadChangeStackBuffer(size int) *HeadChangeStackBuffer {
2525
}
2626

2727
// Push adds a HeadChange to stack buffer. If the length of
28-
// the stack buffer grows larger than the initizlized size, the
28+
// the stack buffer grows larger than the initialized size, the
2929
// oldest HeadChange is returned.
3030
func (h *HeadChangeStackBuffer) Push(hc *api.HeadChange) (rethc *api.HeadChange) {
3131
if h.buffer.Len() >= h.size {

0 commit comments

Comments
 (0)