docs: secure boot, image descriptions and keyboard layout clarification

[NotaInutilis]

Searching for the error message will send to this page now!

[gemini-code-assist]

Summary of Changes

Hello @NotaInutilis, 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 significantly enhances the clarity and helpfulness of the Secure Boot documentation. It aims to improve the user experience by providing more descriptive image alt texts, clarifying potential keyboard layout issues during enrollment, and explicitly detailing the error messages users might encounter, thereby making troubleshooting more straightforward.

Highlights

• Secure Boot Image Description: The documentation for Secure Boot now includes a more detailed description for the main image, explicitly listing the menu options such as 'Continue boot', 'Enroll MOK', 'Enroll key from disk', and 'Enroll hash from disk'.
• Keyboard Layout Clarification: An important note has been updated to clarify that the Secure Boot enrollment prompt exclusively uses a QWERTY keyboard layout, regardless of the user's physical hardware keyboard. This helps users understand why certain characters might be swapped (e.g., 'A' and 'Q' on AZERTY layouts) when entering passwords.
• Detailed Error Message: The exact text of the Secure Boot error message ('bad shim signature' and 'you need to load the kernel first') is now provided in a code block, making it easier for users to search for and identify the error. The accompanying image description has also been updated to reflect this detailed error message.

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 improves the secure boot documentation by adding more descriptive text for images, clarifying potential issues with keyboard layouts, and making an error message searchable by adding it as a text block. These are all valuable improvements for the user. I have one suggestion to improve the accessibility of the error message image by making its alt text more concise to avoid redundancy for screen reader users.

[gemini-code-assist]

While the descriptive alt text is good for accessibility, it's now redundant because the full error message is present in the code block just above. For users with screen readers, this means the long error message will be read out twice. To improve their experience, it's better to use a more concise alt text that describes the image's purpose, such as indicating it's a screenshot of the error mentioned above.

Suggested change