README: make integrated and remote mode version information more clear

[ZZiigguurraatt]

• Move integrated mode version table up and make title more clear.
• Make remote mode compatibility title more clear.

[gemini-code-assist]

Summary of Changes

Hello @ZZiigguurraatt, 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 focuses on enhancing the clarity and organization of version compatibility information within the README.md file. The changes involve strategically relocating and renaming sections to distinctly separate integrated and remote mode daemon versioning details, thereby streamlining the process for users to quickly locate the specific compatibility information they need.

Highlights

• Integrated Mode Version Table Relocation: The table detailing daemon versions packaged with LiT in integrated mode has been moved to an earlier, more prominent section of the README for improved visibility and accessibility.
• Integrated Mode Title Clarification: The heading for the integrated mode version table has been updated to "Daemon Versions packaged with LiT in Integrated Mode" to explicitly clarify its context and purpose.
• Remote Mode Compatibility Title and Link Update: The title for the remote mode compatibility section has been made more clear, and an internal link within this section was updated to accurately reflect the new heading of the integrated mode table.

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 significantly improves the clarity of the README.md file by reorganizing the version compatibility information. The new sections for 'Integrated Mode' and 'Remote Mode' make it much easier for users to find the information relevant to their setup. My review includes a couple of minor suggestions to enhance the readability of the new headings.

[gemini-code-assist]

The use of both bold and italics (**_..._**) for emphasis on 'Integrated Mode' is a bit strong and can make the heading feel cluttered. Using only bold (**...**) is generally sufficient to draw attention and results in a cleaner look.

Suggested change

	## Daemon Versions packaged with LiT in **_Integrated Mode_**
	## Daemon Versions packaged with LiT in **Integrated Mode**

[ViktorT-11]

Nit: Potentially consider this one, as the italic is potentially not ideal for headers.

[ZZiigguurraatt]

changed to ***bold italics*** because the github rendering is already bold for links, so it did not stand out unless it was italics too and this syntax seemed cleaner than my previous one.

[ZZiigguurraatt]

also, github ignored _ italics _ only because it was bolding for the link.

[ViktorT-11]

Generally looks great! Except some small comments.

[ViktorT-11]

Nit: Potentially consider this one, as the italic is potentially not ideal for headers.

[lightninglabs-deploy]

@ViktorT-11: review reminder
@ZZiigguurraatt, remember to re-request review from reviewers when ready

[ViktorT-11]

LGTM after this has been rebased to include the new releases that have been added to the file. @ZZiigguurraatt, do you know how to rebase this, or would you like me to do that?

[ZZiigguurraatt]

LGTM after this has been rebased to include the new releases that have been added to the file. @ZZiigguurraatt, do you know how to rebase this, or would you like me to do that?

I can rebase

[ZZiigguurraatt]

LGTM after this has been rebased to include the new releases that have been added to the file. @ZZiigguurraatt, do you know how to rebase this, or would you like me to do that?

I can rebase

done

[ViktorT-11]

Thanks for an initial rebase! Unfortunately though, there seems to still be merge conflicts here, which you can see by the fact that CI isn't running + a reported merge conflict. You'd need to rebase this once more, and make sure that the HEAD your rebasing on, is that latest version of master.

[ViktorT-11]

An entry for the v0.16.0-apha.rc1 seems to be lost in the rebase here.

[ZZiigguurraatt]

Looks like you merged some more commits after I rebased, so I'll have to re-do it again. Let me know when you can prioritize my merge before other changes to README.md and then I'll re-do it again.