Fix grammar errors

[Pronoss]

This pull request improves the readability and professionalism of the code by fixing grammar errors in the comments and error handling messages across multiple files in the project.

Brief Changelog

• Fixed typos such as "occurred" and "automatically" in error messages and comments.
• Corrected the spelling of "decoder" and other words in various files.
• Standardized language in function descriptions and error handling to improve clarity.

Testing and Verifying

• This change is a trivial rework/code cleanup without any test coverage.
• Manual verification was performed by reviewing the changes to ensure the grammar corrections were applied appropriately.

Summary by CodeRabbit

• Documentation

  • Corrected several typographical errors in comments across multiple files
  • Fixed spelling mistakes in error messages and comments
  • Updated linter directive in test utilities

• Chores

  • Minor text corrections that do not impact code functionality

[graphite-app]

How to use the Graphite Merge Queue

Add the label graphite/merge to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[coderabbitai]

Walkthrough

This pull request consists of minor typographical corrections across several files in the codebase. The changes primarily involve fixing spelling errors in comments, error messages, and linter directives. These modifications do not alter the functional behavior of the code but improve readability and accuracy of textual elements. The corrections span multiple files in the cardinal and relay packages, addressing typos in words like "sequencer", "occurred", "automatically", "essentially", "storage", and a linter directive.

Changes

File	Change Summary
cardinal/router/router.go	Corrected "seqeuncer" to "sequencer" in error message
cardinal/world.go	Fixed "error occured" to "error occurred"
cardinal/world_fixture.go	Corrected "autoamtically" to "automatically" in comment
relay/nakama/auth/custom.go	Updated "essentialy" to "essentially" in comment
relay/nakama/siwe/siwe.go	Fixed typo in comment about storage object
relay/nakama/testutils/testutils.go	Changed linter directive from //nolint:decorder to //nolint:decoder

Possibly related PRs

• fix: Fix grammar issues in multiple files #826: The main PR and this PR both involve corrections to error messages, specifically addressing typographical errors to improve clarity in the code.

Suggested reviewers

• ezavada

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

relay/nakama/testutils/testutils.go (1)

158-158: Add explanation for the nolint directive.

The grammar fix from decorder to decoder looks good. However, as per the linter suggestion, please add an explanation for why we're disabling this check.

-type FakeNakamaModule struct { //nolint:decoder
+type FakeNakamaModule struct { //nolint:decoder // Allowing custom field ordering for test implementation

🧰 Tools

🪛 golangci-lint (1.62.2)

158-158: directive //nolint:decoder should provide explanation such as //nolint:decoder // this is why

(nolintlint)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b9213ba and 0a8f63f.

📒 Files selected for processing (6)

• cardinal/router/router.go (1 hunks)
• cardinal/world.go (1 hunks)
• cardinal/world_fixture.go (1 hunks)
• relay/nakama/auth/custom.go (1 hunks)
• relay/nakama/siwe/siwe.go (1 hunks)
• relay/nakama/testutils/testutils.go (1 hunks)

✅ Files skipped from review due to trivial changes (5)

• cardinal/router/router.go
• relay/nakama/auth/custom.go
• cardinal/world.go
• cardinal/world_fixture.go
• relay/nakama/siwe/siwe.go

🧰 Additional context used

🪛 golangci-lint (1.62.2)

relay/nakama/testutils/testutils.go

158-158: directive //nolint:decoder should provide explanation such as //nolint:decoder // this is why

(nolintlint)