Docs: Fixing some markdown docs issues

- 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}

docs/README.md

@@ -154,7 +154,7 @@ used when committed.
 *   [Web Test Expectations and Baselines](testing/web_test_expectations.md) -
     Setting expected results of web tests.
 *   [Web Tests Tips](testing/web_tests_tips.md) - Best practices for web tests
-*   [Web Tests with Manual Fallback](testing/webt_tests_with_manual_fallback.md) -
+*   [Web Tests with Manual Fallback](testing/web_tests_with_manual_fallback.md) -
     Writing tests that simulate manual interventions
 *   [Extending the Web Test Framework](how_to_extend_web_test_framework.md)
 *   [Fixing Web Test Flakiness](testing/identifying_tests_that_depend_on_order.md) -

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.
 

docs/testing/web_tests.md

@@ -1,4 +1,4 @@
-# Web Tests (formly known as "Layout Tests" "LayoutTests")
+# Web Tests (formerly known as "Layout Tests" or "LayoutTests")
 
 Web tests are used by Blink to test many components, including but not
 limited to layout and rendering. In general, web tests involve loading pages
@@ -492,8 +492,7 @@ If there are current expectation files for `web_tests/foo/bar/test.html`,
 the above command will overwrite the current baselines at their original
 locations with the actual results. The current baseline means the `-expected.*`
 file used to compare the actual result when the test is run locally, i.e. the
-first file found in the [baseline search path]
-(https://cs.chromium.org/search/?q=port/base.py+baseline_search_path).
+first file found in the [baseline search path](https://cs.chromium.org/search/?q=port/base.py+baseline_search_path).
 
 If there are no current baselines, the above command will create new baselines
 in the platform-independent directory, e.g.