Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chapter1: avoid derogatory term 'mess' #124

Closed
wants to merge 1 commit into from

Conversation

xypron
Copy link
Contributor

@xypron xypron commented Apr 16, 2024

Describe the intent of the EBBR specification using more positive terms.

Describe the intent of the EBBR specification using more positive terms.

Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
adding a defined standard (UEFI) to the existing firmware projects (U-Boot).
Or in simpler terms, EBBR is designed to reduce the embedded boot heterogeneity
by implementing a widely accepted standard (UEFI) in the existing firmware
projects (U-Boot).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can drop "the" here and just have "in existing firmware projects" or s/projects/project/ because you explicitly mention a single project.

Otherwise LGTM.

@@ -55,8 +55,9 @@ The challenge for EBBR is to define a set of boot standards that reduce the
amount of custom engineering required, make it possible for OS distributions to
support embedded platforms, while still preserving the firmware stack that
product vendors are comfortable with.
Or in simpler terms, EBBR is designed to solve the embedded boot mess by
adding a defined standard (UEFI) to the existing firmware projects (U-Boot).
Or in simpler terms, EBBR is designed to reduce the embedded boot heterogeneity
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would use 'variation' or 'differences' rather than heterogeneity. Might be easier for non-native English speaks?

@vstehle vstehle added this to the v2.2.0 milestone Apr 22, 2024
@vstehle
Copy link
Collaborator

vstehle commented Apr 22, 2024

Thanks all for having a look.
@xypron, I can merge it with the modifications from @nullr0ute and @robherring if that helps, or do you want to respin it yourself?

@vstehle
Copy link
Collaborator

vstehle commented Apr 29, 2024

Merged with the modifications from @nullr0ute and @robherring.

@vstehle vstehle closed this Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants