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

Fixed a few typos in quality.rst. #139

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fixed a few typos in quality.rst. #139

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
4 changes: 2 additions & 2 deletions quality.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Diátaxis is an approach to *quality* in documentation.
"Quality" is a word in danger of losing some of its meaning; it's something we
all approve of, but rarely risk trying to describe in any rigorous way. We
want quality in our documentation, but much less often specify what exactly
what we mean by that.
we mean by that.

All the same, we can generally point to examples of "high quality
documentation" when asked, and can identify lapses in quality when we see
Expand Down Expand Up @@ -135,7 +135,7 @@ How we recognise deep quality
Consider how we judge the quality of say, clothing. Clothes must have
*functional quality* (they must keep us appropriately warm and dry, stand up
to wear). These things are objectively measurable. You don't really need to
know much about clothes to assess how well they do those this. If water gets
know much about clothes to assess how well they do those things. If water gets
in, or the clothing falls apart - it lacks quality.

There are other characteristics of quality in clothing that can't simply be
Expand Down