chore: fix some minor issues in the comments

chain/events/events_called.go

@@ -390,7 +390,7 @@ type StateMatchFunc func(oldTs, newTs *types.TipSet) (bool, StateChange, error)
 //   - `StateChangeHandler` is called when the specified state change was observed
 //     on-chain, and a confidence threshold was reached, or the specified `timeout`
 //     height was reached with no state change observed. When this callback is
-//     invoked on a timeout, `oldTs` and `states are set to nil.
+//     invoked on a timeout, `oldTs` and `states` are set to nil.
 //     This callback returns a boolean specifying whether further notifications
 //     should be sent, like `more` return param from `CheckFunc` above.
 //

cmd/lotus-pcr/main.go

@@ -116,7 +116,7 @@ var findMinersCmd = &cli.Command{
 	Name:  "find-miners",
 	Usage: "find miners with a desired minimum balance",
 	Description: `Find miners returns a list of miners and their balances that are below a
-   threhold value. By default only the miner actor available balance is considered but other
+   threshold value. By default only the miner actor available balance is considered but other
    account balances can be included by enabling them through the flags.
 
    Examples

cmd/lotus-shed/diff.go

@@ -146,7 +146,7 @@ var diffMinerStates = &cli.Command{
 					}
 
 					if sectorsSnapshotA.Length() != sectorsSnapshotB.Length() {
-						fmt.Println("sector snapshots have different lengts!")
+						fmt.Println("sector snapshots have different lengths!")
 					}
 
 					var infoA miner9.SectorOnChainInfo

documentation/en/api-experimental-user-facing-v2-docs/CLAUDE.md

@@ -9,7 +9,7 @@ This directory contains the experimental user-facing documentation for Filecoin'
 
 ## Workflow
 1. (If this hasn't already been don) Copy updates from Notion into this repository
-2. Make changes, likely using Claude Code by pointing to to local changes or changes in a PR.
+2. Make changes, likely using Claude Code by pointing to local changes or changes in a PR.
 2. Regenerate the table of contents if you've added or modified sections
 3. Submit changes for team review via pull request
 4. After approval, publish updated content back to Notion