Make improvements to Sheriffing documentation

Bug: 1034648
Change-Id: Ib846a51312469cfe2b8ab0fdd0c005f504aa4680
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2129243
Commit-Queue: Eric Foo <efoo@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Eric Foo <efoo@chromium.org>
Auto-Submit: Eric Foo <efoo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755198}

docs/branch_sheriff.md

@@ -23,6 +23,9 @@ important for branch sheriffs. Over the course of your shift, you may need to
 coordinate with trunk sheriffs, troopers, release TPMs, and others -- don't
 hesitate to do so, particularly if you have questions.
 
+Points of contact (i.e. platform-specific sheriffs) can be found
+[here](http://goto.google.com/chrome-branch-sheriffing#points-of-contact).
+
 ## Processes
 
 In general, you'll want to follow the same processes outlined in
@@ -55,6 +58,12 @@ Once you've done that, you'll be able to check out branches:
 To determine the appropriate branch number, you can either use
 [chromiumdash](#chromiumdash) or check [milestone.json][milestone-json] directly.
 
+### Findit
+As FindIt is not available on branches, one way to try to find culprits is using
+`git bisect` locally and upload changes to a gerrit CL and run the needed trybots
+to check. This is especially useful when the errors are not reproducible on your
+local builds or you don't have the required hardware to build the failed tests.
+
 ### Flaky tests
 
 You should largely ignore flaky tests for the time being unless you have
@@ -76,7 +85,10 @@ Use the [branch SoM console][sheriff-o-matic] rather than the main chromium cons
 
 ### Consoles
 
-Use the [beta][main-beta] and [stable][main-stable] branch consoles rather than the main console.
+Use the [beta][main-beta] and [stable][main-stable] branch consoles rather than the
+main console. A new console is created for each milestone. They are named
+"Chromium M## Console" and can be found under the
+[Chromium Project](https://ci.chromium.org/p/chromium).
 
 ### Chromiumdash
 

docs/sheriff.md

@@ -154,6 +154,10 @@ for example), the important features of the build page are:
    Note that the sharded tasks are actually executing on different machines and
    are aggregated back into the builder's results.
 
+#### CI<->Try Mapping
+To translate CI builder names to try builder names, refer to the
+[CI<->Try mapping](https://source.chromium.org/chromium/chromium/tools/build/+/master:scripts/slave/recipe_modules/chromium_tests/trybots.py).
+
 ### The Flake Portal (The "New Flakiness Dashboard")
 
 The [new flakiness dashboard] is much faster than the old one but has a