src: fix comment typos

[sjungwon03]

Fix typos in source comments.

- // Eagerly compile primordials/boostrap/main scripts during code cache+ // Eagerly compile primordials/bootstrap/main scripts during code cache- // If any bulitins should be eagerly compiled i.e. with inner functions+ // If any builtins should be eagerly compiled i.e. with inner functions- // documentation suggets. As a compromise, we currently only block on+ // documentation suggests. As a compromise, we currently only block on- // that criticl user-blocking tasks are not lost.+ // that critical user-blocking tasks are not lost.- // If the stream is not a local undirectional stream and is_readable is+ // If the stream is not a local unidirectional stream and is_readable is

This supersedes #64488, which was closed after an unrelated macOS
test-debugger-exec timeout. This PR is based on the current main branch.

[nodejs-github-bot]

Review requested:

• @nodejs/quic
• @nodejs/startup

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.24%. Comparing base (7a11a9b) to head (f9179cd).
⚠️ Report is 14 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64509 +/- ##
=======================================
Coverage 90.24% 90.24% =======================================
Files 739 739 Lines 241669 241669 Branches 45543 45552 +9 =======================================
+ Hits 218087 218098 +11 + Misses 15150 15110 -40 - Partials 8432 8461 +29 

Files with missing lines	Coverage Δ
src/node_builtins.cc	76.13% <ø> (-0.38%)	⬇️
src/node_builtins.h	100.00% <ø> (ø)
src/node_platform.cc	76.24% <ø> (ø)

... and 25 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pimterry]

Thanks @sjungwon03.

In future though, there's no need to open a new PR if a CI job fails. Just check the cause: if it seems like it's a flaky test issue unrelated to the change then somebody can re-run it to get it passing. Alternatively if it's an actual issue in the change you can push another commit to fix the problem.

[sjungwon03]

Thanks for the clarification. I’ll check the failure first next time and keep the existing PR open if it is unrelated to the change. I’ll push a follow-up commit only when the failure is caused by my change.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74828/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74835/

[nodejs-github-bot]

Landed in 358adc8

[sjungwon03]

Fix typos in source comments.

- // Eagerly compile primordials/boostrap/main scripts during code cache+ // Eagerly compile primordials/bootstrap/main scripts during code cache- // If any bulitins should be eagerly compiled i.e. with inner functions+ // If any builtins should be eagerly compiled i.e. with inner functions- // documentation suggets. As a compromise, we currently only block on+ // documentation suggests. As a compromise, we currently only block on- // that criticl user-blocking tasks are not lost.+ // that critical user-blocking tasks are not lost.- // If the stream is not a local undirectional stream and is_readable is+ // If the stream is not a local unidirectional stream and is_readable is

This supersedes #64488, which was closed after an unrelated macOS
test-debugger-exec timeout. This PR is based on the current main branch.

[nodejs-github-bot]

Review requested:

• @nodejs/quic
• @nodejs/startup

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.24%. Comparing base (7a11a9b) to head (f9179cd).
⚠️ Report is 14 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64509 +/- ##
=======================================
Coverage 90.24% 90.24% =======================================
Files 739 739 Lines 241669 241669 Branches 45543 45552 +9 =======================================
+ Hits 218087 218098 +11 + Misses 15150 15110 -40 - Partials 8432 8461 +29 

Files with missing lines	Coverage Δ
src/node_builtins.cc	76.13% <ø> (-0.38%)	⬇️
src/node_builtins.h	100.00% <ø> (ø)
src/node_platform.cc	76.24% <ø> (ø)

... and 25 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pimterry]

Thanks @sjungwon03.

In future though, there's no need to open a new PR if a CI job fails. Just check the cause: if it seems like it's a flaky test issue unrelated to the change then somebody can re-run it to get it passing. Alternatively if it's an actual issue in the change you can push another commit to fix the problem.

[sjungwon03]

Thanks for the clarification. I’ll check the failure first next time and keep the existing PR open if it is unrelated to the change. I’ll push a follow-up commit only when the failure is caused by my change.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74828/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74835/

[nodejs-github-bot]

Landed in 358adc8

[sjungwon03]

Fix typos in source comments.

- // Eagerly compile primordials/boostrap/main scripts during code cache+ // Eagerly compile primordials/bootstrap/main scripts during code cache- // If any bulitins should be eagerly compiled i.e. with inner functions+ // If any builtins should be eagerly compiled i.e. with inner functions- // documentation suggets. As a compromise, we currently only block on+ // documentation suggests. As a compromise, we currently only block on- // that criticl user-blocking tasks are not lost.+ // that critical user-blocking tasks are not lost.- // If the stream is not a local undirectional stream and is_readable is+ // If the stream is not a local unidirectional stream and is_readable is

This supersedes #64488, which was closed after an unrelated macOS
test-debugger-exec timeout. This PR is based on the current main branch.

[nodejs-github-bot]

Review requested:

• @nodejs/quic
• @nodejs/startup

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.24%. Comparing base (7a11a9b) to head (f9179cd).
⚠️ Report is 14 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64509 +/- ##
=======================================
Coverage 90.24% 90.24% =======================================
Files 739 739 Lines 241669 241669 Branches 45543 45552 +9 =======================================
+ Hits 218087 218098 +11 + Misses 15150 15110 -40 - Partials 8432 8461 +29 

Files with missing lines	Coverage Δ
src/node_builtins.cc	76.13% <ø> (-0.38%)	⬇️
src/node_builtins.h	100.00% <ø> (ø)
src/node_platform.cc	76.24% <ø> (ø)

... and 25 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pimterry]

Thanks @sjungwon03.

In future though, there's no need to open a new PR if a CI job fails. Just check the cause: if it seems like it's a flaky test issue unrelated to the change then somebody can re-run it to get it passing. Alternatively if it's an actual issue in the change you can push another commit to fix the problem.

[sjungwon03]

Thanks for the clarification. I’ll check the failure first next time and keep the existing PR open if it is unrelated to the change. I’ll push a follow-up commit only when the failure is caused by my change.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74828/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74835/

[nodejs-github-bot]

Landed in 358adc8

[sjungwon03]

Fix typos in source comments.

- // Eagerly compile primordials/boostrap/main scripts during code cache+ // Eagerly compile primordials/bootstrap/main scripts during code cache- // If any bulitins should be eagerly compiled i.e. with inner functions+ // If any builtins should be eagerly compiled i.e. with inner functions- // documentation suggets. As a compromise, we currently only block on+ // documentation suggests. As a compromise, we currently only block on- // that criticl user-blocking tasks are not lost.+ // that critical user-blocking tasks are not lost.- // If the stream is not a local undirectional stream and is_readable is+ // If the stream is not a local unidirectional stream and is_readable is

This supersedes #64488, which was closed after an unrelated macOS
test-debugger-exec timeout. This PR is based on the current main branch.

[nodejs-github-bot]

Review requested:

• @nodejs/quic
• @nodejs/startup

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.24%. Comparing base (7a11a9b) to head (f9179cd).
⚠️ Report is 14 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64509 +/- ##
=======================================
Coverage 90.24% 90.24% =======================================
Files 739 739 Lines 241669 241669 Branches 45543 45552 +9 =======================================
+ Hits 218087 218098 +11 + Misses 15150 15110 -40 - Partials 8432 8461 +29 

Files with missing lines	Coverage Δ
src/node_builtins.cc	76.13% <ø> (-0.38%)	⬇️
src/node_builtins.h	100.00% <ø> (ø)
src/node_platform.cc	76.24% <ø> (ø)

... and 25 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pimterry]

Thanks @sjungwon03.

In future though, there's no need to open a new PR if a CI job fails. Just check the cause: if it seems like it's a flaky test issue unrelated to the change then somebody can re-run it to get it passing. Alternatively if it's an actual issue in the change you can push another commit to fix the problem.

[sjungwon03]

Thanks for the clarification. I’ll check the failure first next time and keep the existing PR open if it is unrelated to the change. I’ll push a follow-up commit only when the failure is caused by my change.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74828/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74835/

[nodejs-github-bot]

Landed in 358adc8

[sjungwon03]

Fix typos in source comments.

- // Eagerly compile primordials/boostrap/main scripts during code cache+ // Eagerly compile primordials/bootstrap/main scripts during code cache- // If any bulitins should be eagerly compiled i.e. with inner functions+ // If any builtins should be eagerly compiled i.e. with inner functions- // documentation suggets. As a compromise, we currently only block on+ // documentation suggests. As a compromise, we currently only block on- // that criticl user-blocking tasks are not lost.+ // that critical user-blocking tasks are not lost.- // If the stream is not a local undirectional stream and is_readable is+ // If the stream is not a local unidirectional stream and is_readable is

This supersedes #64488, which was closed after an unrelated macOS
test-debugger-exec timeout. This PR is based on the current main branch.

[nodejs-github-bot]

Review requested:

• @nodejs/quic
• @nodejs/startup

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.24%. Comparing base (7a11a9b) to head (f9179cd).
⚠️ Report is 14 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64509 +/- ##
=======================================
Coverage 90.24% 90.24% =======================================
Files 739 739 Lines 241669 241669 Branches 45543 45552 +9 =======================================
+ Hits 218087 218098 +11 + Misses 15150 15110 -40 - Partials 8432 8461 +29 

Files with missing lines	Coverage Δ
src/node_builtins.cc	76.13% <ø> (-0.38%)	⬇️
src/node_builtins.h	100.00% <ø> (ø)
src/node_platform.cc	76.24% <ø> (ø)

... and 25 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pimterry]

Thanks @sjungwon03.

In future though, there's no need to open a new PR if a CI job fails. Just check the cause: if it seems like it's a flaky test issue unrelated to the change then somebody can re-run it to get it passing. Alternatively if it's an actual issue in the change you can push another commit to fix the problem.

[sjungwon03]

Thanks for the clarification. I’ll check the failure first next time and keep the existing PR open if it is unrelated to the change. I’ll push a follow-up commit only when the failure is caused by my change.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74828/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74835/

[nodejs-github-bot]

Landed in 358adc8

[sjungwon03]

Fix typos in source comments.

- // Eagerly compile primordials/boostrap/main scripts during code cache+ // Eagerly compile primordials/bootstrap/main scripts during code cache- // If any bulitins should be eagerly compiled i.e. with inner functions+ // If any builtins should be eagerly compiled i.e. with inner functions- // documentation suggets. As a compromise, we currently only block on+ // documentation suggests. As a compromise, we currently only block on- // that criticl user-blocking tasks are not lost.+ // that critical user-blocking tasks are not lost.- // If the stream is not a local undirectional stream and is_readable is+ // If the stream is not a local unidirectional stream and is_readable is

This supersedes #64488, which was closed after an unrelated macOS
test-debugger-exec timeout. This PR is based on the current main branch.

[nodejs-github-bot]

Review requested:

• @nodejs/quic
• @nodejs/startup

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.24%. Comparing base (7a11a9b) to head (f9179cd).
⚠️ Report is 14 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64509 +/- ##
=======================================
Coverage 90.24% 90.24% =======================================
Files 739 739 Lines 241669 241669 Branches 45543 45552 +9 =======================================
+ Hits 218087 218098 +11 + Misses 15150 15110 -40 - Partials 8432 8461 +29 

Files with missing lines	Coverage Δ
src/node_builtins.cc	76.13% <ø> (-0.38%)	⬇️
src/node_builtins.h	100.00% <ø> (ø)
src/node_platform.cc	76.24% <ø> (ø)

... and 25 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pimterry]

Thanks @sjungwon03.

In future though, there's no need to open a new PR if a CI job fails. Just check the cause: if it seems like it's a flaky test issue unrelated to the change then somebody can re-run it to get it passing. Alternatively if it's an actual issue in the change you can push another commit to fix the problem.

[sjungwon03]

Thanks for the clarification. I’ll check the failure first next time and keep the existing PR open if it is unrelated to the change. I’ll push a follow-up commit only when the failure is caused by my change.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74828/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74835/

[nodejs-github-bot]

Landed in 358adc8

[sjungwon03]

Fix typos in source comments.

- // Eagerly compile primordials/boostrap/main scripts during code cache+ // Eagerly compile primordials/bootstrap/main scripts during code cache- // If any bulitins should be eagerly compiled i.e. with inner functions+ // If any builtins should be eagerly compiled i.e. with inner functions- // documentation suggets. As a compromise, we currently only block on+ // documentation suggests. As a compromise, we currently only block on- // that criticl user-blocking tasks are not lost.+ // that critical user-blocking tasks are not lost.- // If the stream is not a local undirectional stream and is_readable is+ // If the stream is not a local unidirectional stream and is_readable is

This supersedes #64488, which was closed after an unrelated macOS
test-debugger-exec timeout. This PR is based on the current main branch.

[nodejs-github-bot]

Review requested:

• @nodejs/quic
• @nodejs/startup

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.24%. Comparing base (7a11a9b) to head (f9179cd).
⚠️ Report is 14 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64509 +/- ##
=======================================
Coverage 90.24% 90.24% =======================================
Files 739 739 Lines 241669 241669 Branches 45543 45552 +9 =======================================
+ Hits 218087 218098 +11 + Misses 15150 15110 -40 - Partials 8432 8461 +29 

Files with missing lines	Coverage Δ
src/node_builtins.cc	76.13% <ø> (-0.38%)	⬇️
src/node_builtins.h	100.00% <ø> (ø)
src/node_platform.cc	76.24% <ø> (ø)

... and 25 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pimterry]

Thanks @sjungwon03.

In future though, there's no need to open a new PR if a CI job fails. Just check the cause: if it seems like it's a flaky test issue unrelated to the change then somebody can re-run it to get it passing. Alternatively if it's an actual issue in the change you can push another commit to fix the problem.

[sjungwon03]

Thanks for the clarification. I’ll check the failure first next time and keep the existing PR open if it is unrelated to the change. I’ll push a follow-up commit only when the failure is caused by my change.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74828/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74835/

[nodejs-github-bot]

Landed in 358adc8

[sjungwon03]

Fix typos in source comments.

- // Eagerly compile primordials/boostrap/main scripts during code cache+ // Eagerly compile primordials/bootstrap/main scripts during code cache- // If any bulitins should be eagerly compiled i.e. with inner functions+ // If any builtins should be eagerly compiled i.e. with inner functions- // documentation suggets. As a compromise, we currently only block on+ // documentation suggests. As a compromise, we currently only block on- // that criticl user-blocking tasks are not lost.+ // that critical user-blocking tasks are not lost.- // If the stream is not a local undirectional stream and is_readable is+ // If the stream is not a local unidirectional stream and is_readable is

This supersedes #64488, which was closed after an unrelated macOS
test-debugger-exec timeout. This PR is based on the current main branch.

[nodejs-github-bot]

Review requested:

• @nodejs/quic
• @nodejs/startup

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.24%. Comparing base (7a11a9b) to head (f9179cd).
⚠️ Report is 14 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64509 +/- ##
=======================================
Coverage 90.24% 90.24% =======================================
Files 739 739 Lines 241669 241669 Branches 45543 45552 +9 =======================================
+ Hits 218087 218098 +11 + Misses 15150 15110 -40 - Partials 8432 8461 +29 

Files with missing lines	Coverage Δ
src/node_builtins.cc	76.13% <ø> (-0.38%)	⬇️
src/node_builtins.h	100.00% <ø> (ø)
src/node_platform.cc	76.24% <ø> (ø)

... and 25 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pimterry]

Thanks @sjungwon03.

In future though, there's no need to open a new PR if a CI job fails. Just check the cause: if it seems like it's a flaky test issue unrelated to the change then somebody can re-run it to get it passing. Alternatively if it's an actual issue in the change you can push another commit to fix the problem.

[sjungwon03]

Thanks for the clarification. I’ll check the failure first next time and keep the existing PR open if it is unrelated to the change. I’ll push a follow-up commit only when the failure is caused by my change.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74828/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74835/

[nodejs-github-bot]

Landed in 358adc8