docs: update go module link

[beepdeepor]

Description

Same to #22003

Summary by CodeRabbit

• Documentation
  • Updated references to Go modules documentation for improved accuracy.
  • Clarified content in the "Dependencies and Makefile" section.
  • Made minor formatting adjustments for better readability.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces modifications to two documentation files focused on the refactoring of the Cosmos SDK into smaller Go modules. Changes include updated links to Go modules documentation and minor formatting adjustments. The refactoring aims to enhance maintenance, facilitate semantic versioning, and minimize API breaking changes. The updates ensure that documentation reflects current practices and resources without altering the underlying concepts.

Changes

File Path	Change Summary
docs/architecture/adr-053-go-module-refactoring.md	Updated the URL for Go documentation and clarified refactoring strategy for Go modules.
docs/learn/beginner/00-app-anatomy.md	Changed the link for Go modules documentation and made minor formatting adjustments.

Possibly related PRs

• chore: prepare core 1.0.0-alpha.1 #21564: Changes in core/CHANGELOG.md regarding versioning and module registration related to SDK refactoring.
• docs: use the right link for app.go[Supplementary Omission] #21616: Update to the Go modules documentation link in docs/build/building-modules/15-depinject.md.
• docs: fix broken links #21751: Updates to links in UPGRADING.md reflecting improvements in documentation.
• chore: add simsx labels & more #21776: Changes in .github/CODEOWNERS related to restructuring supporting modularization efforts.
• docs: fix buf link in protobuf.md #21781: Fix for the link in docs/build/tooling/00-protobuf.md ensuring accurate documentation.
• docs: redirect the modules introduce doc #21934: Redirection of modules introduction documentation supporting clarity of module resources.
• docs: update tooling link #21973: Updates to tooling links in documentation enhancing overall documentation quality.
• fix: update go module link #22003: Update to the Go module link in CONTRIBUTING.md for contributor resource accuracy.
• feat(core/handlers): improve handlers registration DevX #22007: Enhancements to handler registration in core/appmodule/v2/handlers.go related to modularization.

Suggested labels

backport/v0.52.x

Suggested reviewers

• julienrbrt
• sontrinh16
• tac0turtle

---

📜 Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between a3729c1 and b91f2ab.

📒 Files selected for processing (2)

• docs/architecture/adr-053-go-module-refactoring.md (1 hunks)
• docs/learn/beginner/00-app-anatomy.md (1 hunks)

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

• docs/architecture/adr-053-go-module-refactoring.md
• docs/learn/beginner/00-app-anatomy.md

---

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 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.

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.

[julienrbrt]

Thanks