fix: scripts comment typos (#40207)

## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`

## Feature

- [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes by running `pnpm lint`
- [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
This commit is contained in:
hiro 2022-09-05 11:26:54 +09:00 committed by GitHub
parent 6356095481
commit 17e84fed39
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions

View file

@ -99,7 +99,7 @@ const collectTraces = async (filePath, metadata) => {
const traces = new Map()
const rootTraces = []
// Input trace file contains newline-seperated sets of traces, where each line is valid JSON
// Input trace file contains newline-separated sets of traces, where each line is valid JSON
// type of Array<TraceEvent>. Read it line-by-line to manually reconstruct trace trees.
//
// We have to read through end of the trace -

View file

@ -12,7 +12,7 @@ const createEvent = (trace, ph, cat) => ({
ph,
// process id. We don't collect this for now, putting arbitrary numbers.
pid: 1,
// thread id. We don't collect this for now, putting arbitrary numebers.
// thread id. We don't collect this for now, putting arbitrary numbers.
tid: 10,
args: trace.tags,
})
@ -112,7 +112,7 @@ const collectTraces = async (filePath, outFilePath, metadata) => {
const traces = new Map()
const rootTraces = []
// Input trace file contains newline-seperated sets of traces, where each line is valid JSON
// Input trace file contains newline-separated sets of traces, where each line is valid JSON
// type of Array<TraceEvent>. Read it line-by-line to manually reconstruct trace trees.
//
// We have to read through end of the trace -