commit | 317532d47d945474e2d65f161a03fd7450aa8377 | [log] [tgz] |
---|---|---|
author | Quinten Yearsley <[email protected]> | Wed Oct 20 17:10:31 2021 |
committer | Chromium LUCI CQ <[email protected]> | Wed Oct 20 17:10:31 2021 |
tree | 7a12efb1d1f964c3877f2acbb32759d13ecca2cb | |
parent | cc1025cd9f63cd2800350071d258b3e887c5f791 [diff] [blame] |
Run a spellchecker on src/docs/ I'd also like to use this CL as a test for crbug.com/1257744 Change-Id: Ie958c515680a2a130c257c23f826d5a30a3963ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3229977 Commit-Queue: Quinten Yearsley <[email protected]> Reviewed-by: Andrii Shyshkalov <[email protected]> Cr-Commit-Position: refs/heads/main@{#933514}
diff --git a/docs/documentation_best_practices.md b/docs/documentation_best_practices.md index 623e18b..b8c9e954 100644 --- a/docs/documentation_best_practices.md +++ b/docs/documentation_best_practices.md
@@ -93,7 +93,7 @@ * Who maintains this directory and where I can learn more? 4. **Design docs, PRDs**: A good design doc or PRD discusses the proposed - implementation at length for the purpose of collecting feeback on that + implementation at length for the purpose of collecting feedback on that design. However, once the code is implemented, design docs should serve as archives of these decisions, not as half-correct docs (they are often misused). See