chromium/src
0
Fork 0
Code Activity

Docs: Fixing some markdown docs issues

Browse Source 
- Fixing broken links.
- Fixed spelling.

Bug: 896479
Change-Id: Id063538cbade42363eebf327afa0b6118123558f
Reviewed-on: https://chromium-review.googlesource.com/c/1401510
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#621539}
This commit is contained in:
Darwin Huang
2019-01-10 11:05:10 +00:00
committed by Commit Bot
parent c066ec3dae
commit a8cd381885
3 changed files with 4 additions and 5 deletions

2
docs/documentation_guidelines.md

@ -65,7 +65,7 @@ Don't assume that readers know everything you currently know.
If you got this far and have some experience with Chromium's code, you'll have figured out that these guidelines are aspirational more than what the world looks like today. So what do we do when working with existing code.
First off: ***[Documentation changes can be TBRed](https://chromium.googlesource.com/chromium/src/+/master/docs/code_reviews.md#TBR_ing-documentation-updates)***. Even in-code changes. If you have discovered something that isn't documented, have figured out how it works and would like to pay it forward, feel free to write something down and check it in.
First off: ***[Documentation changes can be TBRed](https://chromium.googlesource.com/chromium/src/+/master/docs/code_reviews.md#documentation-updates)***. Even in-code changes. If you have discovered something that isn't documented, have figured out how it works and would like to pay it forward, feel free to write something down and check it in.
At the component level, if you are the owner of a component that isn't documented, please add a README.md with content as per the above.