chore: fix spelling errors

[github-prbot]

This PR fixes typos in the codebase.
Please review it, and merge if everything is fine.
If there are proto changes, run make proto-gen and commit the changes.

Summary by CodeRabbit

• Bug Fixes
  • Corrected a typo in the field name from Reciever to Receiver in the withdrawal functionality, ensuring clarity and accuracy in transactions.

[coderabbitai]

Walkthrough

Walkthrough

The recent update involves correcting a typographical error in the field name Reciever to Receiver across multiple files related to the lockup functionality. This correction ensures uniformity and accuracy in the naming convention used within the affected modules.

Changes

File Path	Change Summary
.../lockup/lockup.go .../proto/cosmos/accounts/defaults/lockup/tx.proto .../defaults/lockup/types/tx.pb.go	Corrected typo in Reciever to Receiver in WithdrawUnlockedCoins function and MsgWithdrawResponse message. Updated related methods for consistency.
.../api/cosmos/accounts/defaults/lockup/tx.pulsar.go	Fixed field name from reciever to receiver in functions and declarations related to MsgWithdrawResponse.

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>.
  • Generate unit-tests 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 tests 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yml

Commits

Files that changed from the base of the PR and between 36981e6 and 61cdada.

Files selected for processing (2)

• x/accounts/defaults/lockup/lockup.go (1 hunks)
• x/accounts/proto/cosmos/accounts/defaults/lockup/tx.proto (1 hunks)

Additional comments: 2

x/accounts/proto/cosmos/accounts/defaults/lockup/tx.proto (1)

• 119-119: The correction from reciever to receiver in the MsgWithdrawResponse message is a positive change for code readability and consistency. However, it's crucial to be aware that such changes can impact compatibility with existing systems that use this protobuf definition. Ensure that all references to this field are updated and consider the need for thorough testing to prevent issues in production.

Verification successful

---

The correction from reciever to receiver in the MsgWithdrawResponse message has been successfully verified. The updated field name receiver is consistently used within the specified protobuf files, and the old field name reciever is no longer present. This ensures code readability and consistency without impacting compatibility due to unresolved references to the old field name.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify that the updated field name is consistently used across the Go codebase.
rg --type proto "receiver" x/accounts/proto/cosmos/accounts/defaults/lockup/
# Verify that the old field name is no longer used.
rg --type proto "reciever" x/accounts/proto/cosmos/accounts/defaults/lockup/ | wc -l | awk '{if($1 > 0) {exit 1}}'

Length of output: 251

---

---

Script:

#!/bin/bash
# Verify that the updated field name "receiver" is consistently used across the codebase within protobuf files.
rg "receiver" x/accounts/proto/cosmos/accounts/defaults/lockup/
# Verify that the old field name "reciever" is no longer used within protobuf files.
rg "reciever" x/accounts/proto/cosmos/accounts/defaults/lockup/ | wc -l | awk '{if($1 > 0) {exit 1}}'

Length of output: 329

x/accounts/defaults/lockup/lockup.go (1)

• 314-314: The correction from Reciever to Receiver in the WithdrawUnlockedCoins method is a positive change for code readability and consistency. However, it's crucial to be aware that such changes can impact the function's callers if they rely on named return values. Ensure that all references to this variable are updated and consider the need for thorough testing to prevent issues in production.

Verification successful

---

The verification process confirms that the variable name "Receiver" has been correctly updated in the lockup.go file, and the old misspelled variable name "Reciever" is no longer used in the specified directory. This indicates that the typo correction has been thoroughly implemented. No further issues were found.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify that the updated variable name is consistently used across the Go codebase.
rg --type go "Receiver" x/accounts/defaults/lockup/
# Verify that the old variable name is no longer used.
rg --type go "Reciever" x/accounts/defaults/lockup/ | wc -l | awk '{if($1 > 0) {exit 1}}'

Length of output: 211

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yml

Commits

Files that changed from the base of the PR and between 61cdada and c4c4d0f.

Files selected for processing (2)

• api/cosmos/accounts/defaults/lockup/tx.pulsar.go (15 hunks)
• x/accounts/defaults/lockup/types/tx.pb.go (7 hunks)

Files skipped from review due to trivial changes (1)

• api/cosmos/accounts/defaults/lockup/tx.pulsar.go

Additional comments: 2

x/accounts/defaults/lockup/types/tx.pb.go (2)

• 449-449: The spelling correction from "Reciever" to "Receiver" in the MsgWithdrawResponse struct aligns with the PR's objective to fix spelling errors for clarity and consistency.
• 486-488: The getter method GetReceiver correctly reflects the updated field name spelling. This change is consistent with the PR's objective and improves code readability.