aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTony Ruscoe <tonyruscoe@gmail.com>2019-10-08 10:13:52 +0100
committerGitHub <noreply@github.com>2019-10-08 10:13:52 +0100
commit55b15d1b959023ffabb2282e2104dbbe65b242df (patch)
tree98e47e06906e51b1e368c8a6476040ebfeade8c5
parent5651966e0275572a9956199418d89c9ccc7b2b1a (diff)
parent041a167880642c8a6d894ccbbe500a25b825b552 (diff)
downloadgoogle-styleguide-55b15d1b959023ffabb2282e2104dbbe65b242df.tar.gz
Merge pull request #479 from amanvell/patch-2
Minor spelling/grammar correction
-rw-r--r--docguide/best_practices.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docguide/best_practices.md b/docguide/best_practices.md
index 8f02545..580b75b 100644
--- a/docguide/best_practices.md
+++ b/docguide/best_practices.md
@@ -57,7 +57,7 @@ docs are in bad shape:
## Prefer the good over the perfect
Your documentation should be as good as possible within a reasonable time frame.
-The standards for an documentation review are different from the
+The standards for a documentation review are different from the
standards for code reviews. Reviewers can and should ask for improvements, but
in general, the author should always be able to invoke the "Good Over Perfect
Rule". It's preferable to allow authors to quickly submit changes that improve