Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(240)

Side by Side Diff: docs/documentation_best_practices.md

Issue 2551513002: Fix spelling mistakes in //docs. (Closed)
Patch Set: Undo beng->being Created 4 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « docs/cr_user_manual.md ('k') | docs/emacs.md » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 # Documentation Best Practices 1 # Documentation Best Practices
2 2
3 "Say what you mean, simply and directly." - [Brian Kernighan] 3 "Say what you mean, simply and directly." - [Brian Kernighan]
4 (http://en.wikipedia.org/wiki/The_Elements_of_Programming_Style) 4 (http://en.wikipedia.org/wiki/The_Elements_of_Programming_Style)
5 5
6 [TOC] 6 [TOC]
7 7
8 ## Minimum viable documentation 8 ## Minimum viable documentation
9 9
10 A small set of fresh and accurate docs is better than a large 10 A small set of fresh and accurate docs is better than a large
(...skipping 92 matching lines...) Expand 10 before | Expand all | Expand 10 after
103 ## Implementation state determines document repository 103 ## Implementation state determines document repository
104 104
105 **If the doc is about implemented code, put it in README.md**. If it's 105 **If the doc is about implemented code, put it in README.md**. If it's
106 pre-implementation discussion, including Design docs, PRDs, and presentations, 106 pre-implementation discussion, including Design docs, PRDs, and presentations,
107 keep it in shared Drive folders. 107 keep it in shared Drive folders.
108 108
109 ## Duplication is evil 109 ## Duplication is evil
110 110
111 Do not write your own guide to a common technology or process. Link to it 111 Do not write your own guide to a common technology or process. Link to it
112 instead. If the guide doesn't exist or it's badly out of date, submit your 112 instead. If the guide doesn't exist or it's badly out of date, submit your
113 updates to the appriopriate docs/ directory or create a package-level 113 updates to the appropriate docs/ directory or create a package-level
114 README.md. **Take ownership and don't be shy**: Other teams will usually welcome 114 README.md. **Take ownership and don't be shy**: Other teams will usually welcome
115 your contributions. 115 your contributions.
OLDNEW
« no previous file with comments | « docs/cr_user_manual.md ('k') | docs/emacs.md » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698