Unverified Commit 992ed7bb authored by Greg Walker's avatar Greg Walker Committed by GitHub

Apply suggestions from code review

Co-Authored-By: default avatarRyan Hofschneider <[email protected]>
parent d96f36cd
......@@ -9,18 +9,18 @@ A set of guidelines and best practices for an awesome engineering team
These documents are structured by topic; under each, we include "Requirement",
“Standard”, “Default”, and “Suggestion”.
{%include components/tag-requirement.html %} are practices that *must* be done for
{%include components/tag-requirement.html %} indicates practices that *must* be done for
regulatory, legal, compliance, or other reasons.
{%include components/tag-standard.html %} are practices that have a strong consensus across 18F; they
{%include components/tag-standard.html %} signifies practices that have a strong consensus across 18F; they
should generally be followed to ease the ATO process and make on-boarding
simpler.
{%include components/tag-default.html %} are safe selections that tend to be used by a large number of our
{%include components/tag-default.html %} practices are safe selections that tend to be used by a large number of our
projects; you may find yourself with a better or more tailored solution,
however.
{%include components/tag-suggestion.html %} contain examples that have worked well on a project or two;
{%include components/tag-suggestion.html %} indicates examples that have worked well on a project or two;
they're not widely used enough to be defaults, but are worth considering.
_Note: we've adopted the above classifications but not all the topics have been
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment