docs: add note about no prefix on hash

[jcstein]

Overview

User expected trusted hash to have 0x prefix, when it does not. this makes that clear

[gemini-code-assist]

Summary of Changes

Hello @jcstein, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the clarity of the Celestia node documentation by specifically addressing a common user misconception regarding the SyncFromHash configuration parameter. It ensures that users are explicitly informed that the trusted hash value should not include a 0x prefix, thereby preventing potential configuration errors and improving the overall user experience when setting up light nodes.

Highlights

• Documentation Clarity: Clarified that the SyncFromHash value should not include a 0x prefix when configuring Celestia light nodes in the config.toml file, addressing a common user confusion point.
• Configuration Guidance: Updated two key documentation files, celestia-node-trusted-hash.md and quick-start.md, to explicitly state the absence of the 0x prefix for trusted hash values.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request clarifies that the trusted hash should not have a 0x prefix in the documentation, which is a helpful addition for users. I've added a couple of suggestions: one to improve list formatting for consistency in the documentation, and another to consider ignoring an auto-generated file from source control.