docs: update link contents

[polymaer]

Description

it is confusing to use the same word (appd) representing two different entrypoints. i replaced the link contents with the specific item to make it more clear.

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• updated the relevant documentation or specification, including comments for documenting Go code
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

• Documentation
  • Updated references in beginner guide to use 'Node Client' and 'Application Interface' instead of 'appd'.

[coderabbitai]

Walkthrough

Walkthrough

The changes involve updating terminology in a documentation file related to building an application using a Makefile. Specifically, references to 'appd' were changed to 'Node Client' and 'Application Interface'. This update aims to improve clarity and consistency in the documentation.

Changes

File Path	Change Summary
docs/learn/beginner/00-app-anatomy.md	Updated references from 'appd' to 'Node Client' and 'Application Interface'.

---

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

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

Outside diff range and nitpick comments (7)

docs/learn/beginner/00-app-anatomy.md (7)

275-275: Clarify the Makefile's role in the build process.

The sentence "The Makefile primarily ensures that the go.mod is run before building the two entrypoints to the application, Node Client and Application Interface." could be clarified. It might be more accurate to say that the Makefile orchestrates the build process, including dependency management and compilation of the application's entry points.

---

Line range hint 56-56: Simplify the sentence for better readability.

Consider revising the sentence to: "The application's appCodec is used to serialize and deserialize data structures for storage, as stores can only persist []bytes."

---

Line range hint 60-60: Add a comma for clarity.

Consider adding a comma after "purposes" for better readability: "from simapp, the Cosmos SDK's own app used for demo and testing purposes, see an example..."

---

Line range hint 68-68: Simplify the sentence for better readability.

Consider revising the sentence to: "The constructor function must comply with the AppCreator signature to be used in the start command."

---

Line range hint 78-78: Vary sentence structure to enhance readability.

Consider revising to vary the sentence structure: "Instantiate a new application with a reference to a baseapp instance, a codec, and all the appropriate store keys. Following this, instantiate all the keeper objects defined in the application's type using the NewKeeper function of each of the application's modules."

---

Line range hint 81-81: Use "different from" instead of "different than".

Consider revising the sentence to: "Should the value be different from the predicted one, special logic defined in the invariant registry is triggered (usually the chain is halted)."

---

Line range hint 84-84: Remove redundancy in the phrase.

Consider revising the sentence to: "used to initialize the application when first started."

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a1ae4c3 and 57e86bd.

Files selected for processing (1)

• docs/learn/beginner/00-app-anatomy.md (1 hunks)

Additional Context Used

LanguageTool (17)

docs/learn/beginner/00-app-anatomy.md (17)

Near line 56: Consider a shorter alternative to avoid wordiness.
Context: ...rialize and deserialize data structures in order to store them, as stores can only persist ...

---

Near line 60: Possible missing comma found.
Context: ...ion from simapp, the Cosmos SDK's own app used for demo and testing purposes: ``...

---

Near line 68: Consider a shorter alternative to avoid wordiness.
Context: ...must fulfill the AppCreator signature in order to be used in the [start command](../adv...

---

Near line 78: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ..., and all the appropriate store keys. * Instantiate all the keeper objects def...

---

Near line 81: Did you mean ‘different from’? ‘Different than’ is often considered colloquial style.
Context: ...e module. Should the value be different than the predicted one, special logic define...

---

Near line 81: To elevate your writing, try using a synonym here.
Context: ...producing long-lasting effects that are hard to fix. * With the module manager, set ...

---

Near line 84: This phrase is redundant. Consider writing “started”.
Context: ...o initialize the application when it is first started. * PreBlocker: cal...

---

Near line 85: Loose punctuation mark.
Context: ...arted. * PreBlocker: called before BeginBlock. * [`Begin...

---

Near line 86: Loose punctuation mark.
Context: ...before BeginBlock. * [BeginBlocker, EndBlocker](#beginblocker-and-endbloc...

---

Near line 87: Loose punctuation mark.
Context: ...](../advanced/00-baseapp.md#antehandler): used to handle fees and signature verif...

---

Near line 148: Loose punctuation mark.
Context: ...our fields means: * InterfaceRegistry: The InterfaceRegistry is used by the ...

---

Near line 151: Loose punctuation mark.
Context: ...9-protobuf-state-encoding.md). * Codec: The default codec used throughout the C...

---

Near line 152: Loose punctuation mark.
Context: ...K uses Protobuf as Codec. * TxConfig: TxConfig defines an interface a clien...

---

Near line 153: Loose punctuation mark.
Context: .../advanced/01-transactions.md). * Amino: Some legacy parts of the Cosmos SDK sti...

---

Near line 164: Consider a shorter alternative to avoid wordiness.
Context: ...0-baseapp.md) to the appropriate module in order to be processed. This paradigm enables dev...

---

Near line 193: Consider a shorter alternative to avoid wordiness.
Context: ...3-L36 ``` Service methods use keeper in order to update the module state. Each module s...

---

Near line 217: If the ‘because’ clause is essential to the meaning, do not use a comma before the clause.
Context: ...to unmarshal them when it retrieves them, because stores only accept []bytes as value. ...

Markdownlint (12)

docs/learn/beginner/00-app-anatomy.md (12)

115: Expected: asterisk; Actual: dash
Unordered list style

---

116: Expected: asterisk; Actual: dash
Unordered list style

---

84: Expected: 2; Actual: 4
Unordered list indentation

---

85: Expected: 2; Actual: 4
Unordered list indentation

---

86: Expected: 2; Actual: 4
Unordered list indentation

---

87: Expected: 2; Actual: 4
Unordered list indentation

---

149: Expected: 2; Actual: 4
Unordered list indentation

---

150: Expected: 2; Actual: 4
Unordered list indentation

---

43: Expected: 0 or 2; Actual: 1
Trailing spaces

---

119: null
Fenced code blocks should be surrounded by blank lines

---

121: null
Fenced code blocks should be surrounded by blank lines

---

119: null
Fenced code blocks should have a language specified

Path-based Instructions (1)

docs/learn/beginner/00-app-anatomy.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

[julienrbrt]

@Mergifyio backport release/v0.50.x

[mergify]

backport release/v0.50.x

✅ Backports have been created

• #20462 docs: update link contents (backport #20437) has been created for branch release/v0.50.x