Fix autoroll link

site/dev/sheriffing/index.md

 Tree Sheriffs Documentation
 ===========================
 
 ### Contents ###
 
 *   [What does a sheriff do?](#what_is_a_sheriff)
     +   [Skia tree](#skia_tree)
     +   [DEPS rolls](#deps_rolls)
     +   [Gold and Perf](#gold_and_perf)
     +   [Documentation](#sheriff_doc)
@@ skipping 20 matching lines @@
 ### Skia tree
 * Understand the [buildbots infrastructure](https://skia.org/dev/testing/buildbot).
 * Start watching the [status page](https://status.skia.org) for bot breakages.
 * Track down people responsible for breakages and revert broken changes if there is no easy fix.
 * Close and open the [tree](http://skia-tree-status.appspot.com).
 * Keep the builder comments on the [status page](https://status.skia.org) up to date.
 * File or follow up with [BreakingTheBuildbots bugs](https://bug.skia.org/?q=label:BreakingTheBuildbots). See the tip on [when to file bugs](#when_to_file_bugs).
 
 <a name="deps_rolls"></a>
 ### DEPS rolls
-* Ensure that [AutoRoll Bot](https://skia-tree-status.appspot.com/set_arb_action)'s DEPS rolls land successfully.
+* Ensure that [AutoRoll Bot](https://autoroll.skia.org)'s DEPS rolls land successfully.
 
 <a name="gold_and_perf"></a>
 ### Gold and Perf
 * Pay attention for new [Perf](https://perf.skia.org/) and [Gold](https://gold.skia.org/) alerts (by clicking on the bell at the top right of the [status page](https://status.skia.org)).
 * The sheriff's duty here is to make sure that when developers introduce new images or new perf regressions, that they are aware of what happened, and they use these tools to take appropriate action.
- 
+
 <a name="sheriff_doc"></a>
 ### Documentation
 * Improve/update this documentation page for future sheriffs, especially the [Tips section](#tips).
 
 In general, sheriffs should have a strong bias towards actions that keep the tree green and then open; if a simple revert can fix the problem, the sheriff <b>should revert first and ask questions later</b>.
 
 
 <a name="view_current_upcoming_sheriffs"></a>
 View current and upcoming sheriffs
 ----------------------------------
@@ skipping 84 matching lines @@
   * Note: this change is usually done in the DEPS roll patch itself
 
 * (Preferred but slower) Make a separate Blink patch by editing LayoutTests/TestExpectations
   * Add # comment about what has changed (I usually paraphrase the crbug text)
   * Add line(s) like the following after the comment:
       * crbug.com/<bug#youjustcreated> foo/bar/test-name.html [ NeedsManualRebaseline ]
   * Commit the patch you created and wait until it lands and rolls into Chrome
 
 * Retry the DEPS roll (for the 1st/dispreferred option this usually means just retrying the layout bots)
 * Make a Blink patch by editing LayoutTests/TestExpectations
-  * Add # comment about what has changed 
+  * Add # comment about what has changed
   * Add line(s) like the following after the comment:
       * crbug.com/<bug#youjustcreated> foo/bar/test-name.html [ NeedsRebaseline ]
         * (if you took the second option above you can just edit the existing line(s))
 
 * If you took the first/dispreferred option above:
   * Wait for the Blink patch to roll into Chrome
   * Create a Chrome patch that removes your suppressions from skia/skia_test_expectations.txt