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.

Sign up for GitHub

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
Closed

chapter1: avoid derogatory term 'mess' #124

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions source/chapter1-about.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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?

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.


However, EBBR is a specification, not an implementation.
The goal of EBBR is not to mandate U-Boot and Linux.
Expand Down