docs(consensus-node): reduce log level

[rootulp]

Motivated by celestiaorg/celestia-app#4643

cc: @tac0turtle

Screenshot

Summary by CodeRabbit

• Documentation
  • Improved readability by adding blank lines before lists in reset command sections.
  • Added an optional section explaining how to reduce log verbosity by updating the log level in the configuration file.

[coderabbitai]

Walkthrough

The documentation for consensus node reset procedures was updated to improve readability by inserting blank lines before bullet lists in three command descriptions. Additionally, a new optional section was added, providing guidance on reducing log verbosity by editing the log_level in the config.toml file. The changes are limited to formatting enhancements and the addition of a configuration tip, with no modifications to commands or their effects.

Changes

File(s)	Change Summary
how-to-guides/consensus-node.md	Inserted blank lines before lists for readability in reset command sections; added a new optional section on reducing log level with a configuration example.

Possibly related PRs

• docs: describe destructive action in docs #1939: Expands and clarifies reset command descriptions in the same documentation section, focusing on content details rather than formatting or configuration tips.

Suggested reviewers

• jcstein

Poem

A hop and a skip, with docs in my paws,
I tidied up lists and refined the cause.
Now logs can be quiet, your screens less bright,
With a tweak in config, you'll sleep well at night.
🐇✨

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

how-to-guides/consensus-node.md (1)

522-531: Add “Reduce log level” configuration tip
Great addition that directly addresses the PR objective of lowering log verbosity. Consider consolidating all optional configuration tweaks (logging, indexing, pruning, etc.) under a single Configuration options section for better discoverability. Optionally, if your style guide permits, you could switch from a diff-style code block to a toml-highlighted snippet to improve clarity for readers.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b5e7b4f and 15f2a6f.

📒 Files selected for processing (1)

• how-to-guides/consensus-node.md (4 hunks)

🔇 Additional comments (3)

how-to-guides/consensus-node.md (3)

364-364: Consistent Markdown list formatting
Adding a blank line before the list under Option 1: Reset blockchain data with reset-state improves readability and aligns with common Markdown style (and markdownlint rules).

---

380-380: Consistent Markdown list formatting
Adding a blank line before the list under Option 2: Full reset with unsafe-reset-all improves readability and aligns with Markdown best practices.

---

415-415: Consistent Markdown list formatting
Adding a blank line before the list under Option 4: Simple data directory cleanup enhances readability and follows Markdown guidelines.

[tac0turtle]

nice