chore: fix typos

[hoangdv2429]

Description

This PR will fix every typos exist on current repo. After this we can add another CI to check for typo per PR submit.

PR checklist

• Tests written/updated
• Changelog entry added in .changelog (we use
  unclog to manage our changelog)
• Updated relevant documentation (docs/ or spec/) and code comments

[rootulp]

After this we can add another CI to check for typo per PR submit.

Which linter or CI check do you propose adding? This repo already enabled

celestia-core/.golangci.yml

Line 18 in 4b6c2dd

- misspell

[hoangdv2429]

Got it. I'll update to pass the check and also close the CI PR.

[rootulp]

LGTM. Some of these typos may exist in upstream https://github.com/cometbft/cometbft if you'd like to make a similar PR there

Thanks for your contribution!

[rootulp]

IMO we should ignore the failing govulncheck on this PR and instead tackle separately in #1151

[hoangdv2429]

`=== Informational ===

Found 2 vulnerabilities in packages that you import, but there are no call
stacks leading to the use of these vulnerabilities. You may not need to
take any action. See https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck
for details.

Vulnerability #1: GO-2023-2186
Incorrect detection of reserved device names on Windows in path/filepath
More info: https://pkg.go.dev/vuln/GO-2023-2186
Standard library
Found in: path/[email protected]
Fixed in: path/[email protected]

Vulnerability #2: GO-2023-2102
HTTP/2 rapid reset can cause excessive work in net/http
More info: https://pkg.go.dev/vuln/GO-2023-2102
Module: golang.org/x/net
Found in: golang.org/x/[email protected]
Fixed in: golang.org/x/[email protected]

Your code is affected by 2 vulnerabilities from the Go standard library.`
Yes, I agree. Seems like we need to bump those deps.

[hoangdv2429]

The failing check could be from json or toml. Please let's me check.

[hoangdv2429]

@rootulp Can you rerun the e2e test sir, I don't think I touch any config files

[rootulp]

@rootulp Can you rerun the e2e test sir, I don't think I touch any config files

Thanks for the ping! Sorry the CI on this repo is flakey. Re-running.