From b35a3258166cb6e9452211b95c2c8e6cfc0bdf69 Mon Sep 17 00:00:00 2001 From: Aayush Rajasekaran Date: Mon, 4 Jul 2022 11:17:00 -0400 Subject: [PATCH] Fixup typos --- documentation/en/default-lotus-miner-config.toml | 4 ++-- node/config/doc_gen.go | 4 ++-- node/config/types.go | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/documentation/en/default-lotus-miner-config.toml b/documentation/en/default-lotus-miner-config.toml index 984ec08fb..b39926904 100644 --- a/documentation/en/default-lotus-miner-config.toml +++ b/documentation/en/default-lotus-miner-config.toml @@ -350,7 +350,7 @@ # # In normal operation, when preparing to compute WindowPoSt, lotus-miner will perform a round of reading challenges # from all sectors to confirm that those sectors can be proven. Challenges read in this process are discarded, as - # we're only interested in checkdng that sector data can be read. + # we're only interested in checking that sector data can be read. # # When using builtin proof computation (no PoSt workers, and DisableBuiltinWindowPoSt is set to false), this process # can save a lot of time and compute resources in the case that some sectors are not readable - this is caused by @@ -359,7 +359,7 @@ # When using PoSt workers, this process is mostly redundant, with PoSt workers challenges will be read once, and # if challenges for some sectors aren't readable, those sectors will just get skipped. # - # Disabling sector pre-checks will slightly requice IO load when proving sectors, possibly resulting in shorter + # Disabling sector pre-checks will slightly reduce IO load when proving sectors, possibly resulting in shorter # time to produce window PoSt. In setups with good IO capabilities the effect of this option on proving time should # be negligible. # diff --git a/node/config/doc_gen.go b/node/config/doc_gen.go index 4761ff753..8e35af782 100644 --- a/node/config/doc_gen.go +++ b/node/config/doc_gen.go @@ -668,7 +668,7 @@ Before enabling this option, make sure your PoSt workers work correctly.`, In normal operation, when preparing to compute WindowPoSt, lotus-miner will perform a round of reading challenges from all sectors to confirm that those sectors can be proven. Challenges read in this process are discarded, as -we're only interested in checkdng that sector data can be read. +we're only interested in checking that sector data can be read. When using builtin proof computation (no PoSt workers, and DisableBuiltinWindowPoSt is set to false), this process can save a lot of time and compute resources in the case that some sectors are not readable - this is caused by @@ -677,7 +677,7 @@ the builtin logic not skipping snark computation when some sectors need to be sk When using PoSt workers, this process is mostly redundant, with PoSt workers challenges will be read once, and if challenges for some sectors aren't readable, those sectors will just get skipped. -Disabling sector pre-checks will slightly requice IO load when proving sectors, possibly resulting in shorter +Disabling sector pre-checks will slightly reduce IO load when proving sectors, possibly resulting in shorter time to produce window PoSt. In setups with good IO capabilities the effect of this option on proving time should be negligible. diff --git a/node/config/types.go b/node/config/types.go index 9a1dcbe00..f92727942 100644 --- a/node/config/types.go +++ b/node/config/types.go @@ -249,7 +249,7 @@ type ProvingConfig struct { // // In normal operation, when preparing to compute WindowPoSt, lotus-miner will perform a round of reading challenges // from all sectors to confirm that those sectors can be proven. Challenges read in this process are discarded, as - // we're only interested in checkdng that sector data can be read. + // we're only interested in checking that sector data can be read. // // When using builtin proof computation (no PoSt workers, and DisableBuiltinWindowPoSt is set to false), this process // can save a lot of time and compute resources in the case that some sectors are not readable - this is caused by @@ -258,7 +258,7 @@ type ProvingConfig struct { // When using PoSt workers, this process is mostly redundant, with PoSt workers challenges will be read once, and // if challenges for some sectors aren't readable, those sectors will just get skipped. // - // Disabling sector pre-checks will slightly requice IO load when proving sectors, possibly resulting in shorter + // Disabling sector pre-checks will slightly reduce IO load when proving sectors, possibly resulting in shorter // time to produce window PoSt. In setups with good IO capabilities the effect of this option on proving time should // be negligible. //