trivial: typo fix

This commit is contained in:
yyforyongyu 2020-08-13 07:33:52 +08:00
parent 37a29b4869
commit 57f7115437
No known key found for this signature in database
GPG Key ID: 9BCD95C4FF296868
6 changed files with 10 additions and 10 deletions

@ -482,7 +482,7 @@ func GetClientMissedBlocks(chainConn ChainConn, clientBestBlock *BlockEpoch,
return missedBlocks, nil
}
// RewindChain handles internal state updates for the notifier's TxNotifier It
// RewindChain handles internal state updates for the notifier's TxNotifier. It
// has no effect if given a height greater than or equal to our current best
// known height. It returns the new best block for the notifier.
func RewindChain(chainConn ChainConn, txNotifier *TxNotifier,

@ -262,7 +262,7 @@ type HistoricalConfDispatch struct {
// inclusion of within the chain.
ConfRequest
// StartHeight specifies the block height at which to being the
// StartHeight specifies the block height at which to begin the
// historical rescan.
StartHeight uint32

@ -727,7 +727,7 @@ func (b *boltArbitratorLog) FetchContractResolutions() (*ContractResolutions, er
numOutgoing uint32
)
// Next, we'll read out he incoming and outgoing HTLC
// Next, we'll read out the incoming and outgoing HTLC
// resolutions.
err = binary.Read(resReader, endian, &numIncoming)
if err != nil {

@ -59,7 +59,7 @@ type ChainArbitratorConfig struct {
// broadcast our commitment transaction if we have incoming htlcs. This
// value should be set based on our current fee estimation of the
// commitment transaction. We use this to determine when we should
// broadcast instead of the just the HTLC timeout, as we want to ensure
// broadcast instead of just the HTLC timeout, as we want to ensure
// that the commitment transaction is already confirmed, by the time the
// HTLC expires. Otherwise we may end up not settling the htlc on-chain
// because the other party managed to time it out.
@ -89,7 +89,7 @@ type ChainArbitratorConfig struct {
DeliverResolutionMsg func(...ResolutionMsg) error
// MarkLinkInactive is a function closure that the ChainArbitrator will
// use to mark that active HTLC's shouldn't be attempt ted to be routed
// use to mark that active HTLC's shouldn't be attempted to be routed
// over a particular channel. This function will be called in that a
// ChannelArbitrator decides that it needs to go to chain in order to
// resolve contracts.
@ -157,7 +157,7 @@ type ChainArbitratorConfig struct {
// resolution.
OnionProcessor OnionProcessor
// PaymentsExpirationGracePeriod indicates is a time window we let the
// PaymentsExpirationGracePeriod indicates a time window we let the
// other node to cancel an outgoing htlc that our node has initiated and
// has timed out.
PaymentsExpirationGracePeriod time.Duration

@ -500,7 +500,7 @@ func (c *chainWatcher) closeObserver(spendNtfn *chainntnfs.SpendEvent) {
select {
// We've detected a spend of the channel onchain! Depending on the type
// of spend, we'll act accordingly , so we'll examine the spending
// of spend, we'll act accordingly, so we'll examine the spending
// transaction to determine what we should do.
//
// TODO(Roasbeef): need to be able to ensure this only triggers

@ -1987,7 +1987,7 @@ func (c *ChannelArbitrator) resolveContract(currentContract ContractResolver) {
switch {
// If this contract produced another, then this means
// the current contract was only able to be partially
// resolved in this step. So we'll not a contract swap
// resolved in this step. So we'll do a contract swap
// within our logs: the new contract will take the
// place of the old one.
case nextContract != nil:
@ -2082,7 +2082,7 @@ func (c *ChannelArbitrator) UpdateContractSignals(newSignals *ContractSignals) {
// channelAttendant is the primary goroutine that acts at the judicial
// arbitrator between our channel state, the remote channel peer, and the
// blockchain Our judge). This goroutine will ensure that we faithfully execute
// blockchain (Our judge). This goroutine will ensure that we faithfully execute
// all clauses of our contract in the case that we need to go on-chain for a
// dispute. Currently, two such conditions warrant our intervention: when an
// outgoing HTLC is about to timeout, and when we know the pre-image for an