Typos fix

[MaxweLL22-22]

Fix: Corrected typos in source files

Changes

Corrected typo in /CODE_OF_CONDUCT.md (Line 9)

"socio-economic" → "socioeconomic"

Corrected typo in /CHANGELOG.md (Line 49)

"ditribution" → "distribution"

Corrected typo in /upgrades/CHANGELOG.md (Line 63)

"re-use" → "reuse"

Corrected typo in /app/upgrades.go (Line 23)

"unitialize" → "uninitialize"

Corrected typo in /tests/upgrade/upgrade_test.go (Line 757)

"commited" → "committed"

Corrected typo in /sdl/v2_test.go (Line 216)

"ture" → "true, pure"

Corrected typo in /sdl/v2_1_test.go (Line 174)

"ture" → "true, pure"

Corrected typo in /pubsub/bus.go (Line 112)

"curev" → "curve"

Corrected typo in /pubsub/bus.go (Line 122)

"curev" → "curve"

Corrected typo in /pubsub/bus.go (Line 133)

"curev" → "curve"

Purpose

Improved code accuracy and professionalism by fixing typos.

Summary by CodeRabbit

• Documentation

  • Fixed typographical and formatting errors in changelog entries and the Code of Conduct.
  • Corrected comment typos in test files for improved clarity.

• Style

  • Updated variable and error message wording for consistency and readability.

[github-actions]

Marked as stale; will be closed in five days.
Cut bait or go fishing!

[coderabbitai]

Walkthrough

This update consists of minor textual corrections across several files, including fixing typographical errors, improving comment clarity, and adjusting variable names for readability. No changes were made to the logic, control flow, or public interfaces of the codebase.

Changes

File(s)	Change Summary
CHANGELOG.md, upgrades/CHANGELOG.md	Corrected typographical errors and phrasing in changelog entries.
CODE_OF_CONDUCT.md	Updated phrasing for "socio-economic status" to "socioeconomic status" for consistency.
app/upgrades.go	Fixed typo in error message from "unitialize" to "uninitialize".
pubsub/bus.go	Renamed variable in event loop from curev to curve for clarity.
sdl/v2_1_test.go, sdl/v2_test.go	Corrected comment typos from "ture" to "true, pure" in test functions.

Poem

In files and docs, small errors fell,
A typo here, a phrase to quell.
With nimble paws, corrections made,
The code and comments now well-laid.
No logic changed, just clearer view—
A tidy warren, fresh and new!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dd37426 and 807fdbc.

📒 Files selected for processing (7)

• CHANGELOG.md (1 hunks)
• CODE_OF_CONDUCT.md (1 hunks)
• app/upgrades.go (1 hunks)
• pubsub/bus.go (3 hunks)
• sdl/v2_1_test.go (1 hunks)
• sdl/v2_test.go (1 hunks)
• upgrades/CHANGELOG.md (1 hunks)

🔇 Additional comments (7)

CHANGELOG.md (1)

49-49: Typo fix in Bug Fixes entry
The word “distribution” is now correctly spelled. No functional or structural changes here.

CODE_OF_CONDUCT.md (1)

9-9: Typo fix in pledge section
Changed “socio-economic” to “socioeconomic” for consistency and correctness. No behavior change.

sdl/v2_1_test.go (1)

174-174: Typo fix in test comment
Updated the misspelled “ture” to “true, pure” in the cross-validation comment. This is purely cosmetic and does not affect test logic.

app/upgrades.go (1)

23-23: Typo fix in error message
Corrected “uninitialize” spelling in the upgrade handler error return. No change to functionality.

upgrades/CHANGELOG.md (1)

52-52: Typo fix in upgrade description
Removed hyphen in “reuse” (was “re-use”). This is a text-only changelog update.

pubsub/bus.go (1)

112-113: Typo fix: consistent variable naming
The variable formerly named curev has been renamed to curve in its declaration, in the buffer assignment, and in the emission case. This change is purely cosmetic and does not alter behavior.

Also applies to: 122-123, 133-134

sdl/v2_test.go (1)

216-216: Typo fix in comment
Corrected the misspelling from "ture" to "true, pure" in the test comment. This change has no impact on test logic or execution.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.