From: evan.lloyd@arm.com
To: edk2-devel@lists.01.org
Cc: "ard.biesheuvel@linaro.org"@arm.com,
"leif.lindholm@linaro.org"@arm.com,
"Matteo.Carlini@arm.com"@arm.com, "lersek@redhat.com"@arm.com,
"liming.gao@intel.com"@arm.com,
"michael.d.kinney@intel.com"@arm.com,
"jordan.l.justen@intel.com"@arm.com, "nd@arm.com"@arm.com
Subject: [edk2-CCodingStandardsSpecification PATCH 2/5] Fix Chapter 2 Typos
Date: Wed, 3 Jan 2018 11:22:45 +0000 [thread overview]
Message-ID: <20180103112248.11880-3-evan.lloyd@arm.com> (raw)
In-Reply-To: <20180103112248.11880-1-evan.lloyd@arm.com>
From: Evan Lloyd <evan.lloyd@arm.com>
2.1 Accessibility - remove erroneous "as"
2.1 Confirmation - insert missing full stop
2.1 Forgiveness - excise superfluous "errors"
2.1 Standard techniques - remove redundant "be to"
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Evan Lloyd <evan.lloyd@arm.com>
---
2_guiding_principles.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/2_guiding_principles.md b/2_guiding_principles.md
index a7759f27dcf71a948b903332c9bc14946e445cd8..5a51225b65dec2159a4fb94481920666c0d042ff 100644
--- a/2_guiding_principles.md
+++ b/2_guiding_principles.md
@@ -47,7 +47,7 @@ The following is an alphabetical list of software design principles:
**Accessibility**
This entails designing objects and environments to be usable, with no
-modification, by the greatest number of people as possible, including people
+modification, by the greatest number of people possible, including people
with varying educational and social backgrounds, as well as those with motor or
sensory challenges.
@@ -68,7 +68,7 @@ shortterm memory, as well as to accommodate its limits.
This is a technique used for critical actions, inputs, or commands.
Confirmations are primarily used to prevent unintended actions. Minimize errors
in critical or irreversible operations with confirmations. If you overuse
-confirmations, expect that they will be ignored Avoid overusing confirmations
+confirmations, expect that they will be ignored. Avoid overusing confirmations
to ensure that they remain unexpected and uncommon; otherwise, they may be
ignored. Use a two-step operation for hardware confirmations and dialogs for
software confirmations.
@@ -97,7 +97,7 @@ about the assumptions you make.
**Forgiveness**
Design to help users avoid errors and reduce the negative consequences of
-errors any errors made. Recommended methods for achieving design forgiveness
+any errors made. Recommended methods for achieving design forgiveness
include affordances, reversibility of actions, and safety nets. Effectively
designing for forgiveness results in a design needing minimal confirmations,
warnings, and help.
@@ -171,7 +171,7 @@ classes of platforms from embedded systems to massively parallel computers.
Greater reliance on unique or exotic pieces makes a system harder to
understand, and more intimidating for someone trying to understand it the first
-time. Using standardized, common approaches should be to give the whole system
+time. Using standardized, common approaches should give the whole system
a familiar feeling. This standardization is one of the primary goals of this
document.
--
Guid("CE165669-3EF3-493F-B85D-6190EE5B9759")
next prev parent reply other threads:[~2018-01-03 11:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 11:22 [edk2-CCodingStandardsSpecification PATCH 0/5] Typographic Corrections evan.lloyd
2018-01-03 11:22 ` [edk2-CCodingStandardsSpecification PATCH 1/5] Fix Chapter 1 Typos evan.lloyd
2018-01-03 16:51 ` Laszlo Ersek
2018-01-04 19:40 ` Evan Lloyd
2018-01-03 11:22 ` evan.lloyd [this message]
2018-01-03 16:52 ` [edk2-CCodingStandardsSpecification PATCH 2/5] Fix Chapter 2 Typos Laszlo Ersek
2018-01-03 11:22 ` [edk2-CCodingStandardsSpecification PATCH 3/5] Fix Chapter 3 Typos evan.lloyd
2018-01-03 16:53 ` Laszlo Ersek
2018-01-03 11:22 ` [edk2-CCodingStandardsSpecification PATCH 4/5] Fix Chapter 4 Typo evan.lloyd
2018-01-03 16:56 ` Laszlo Ersek
2018-01-08 18:31 ` Evan Lloyd
2018-01-03 11:22 ` [edk2-CCodingStandardsSpecification PATCH 5/5] Fix Chapter 5 Typos evan.lloyd
2018-01-03 17:07 ` Laszlo Ersek
2018-01-08 18:26 ` Evan Lloyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180103112248.11880-3-evan.lloyd@arm.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox