Tweak SkiaLab docs

site/dev/testing/skialab.md

 SkiaLab
 =======
 
 Overview
 --------
 
 Skia's buildbots are hosted in three places:
 
 * Google Compute Engine. This is the preferred location for bots which don't
   need to run on physical hardware, ie. anything that doesn't require a GPU,
@@ skipping 49 matching lines @@
 1. Click on the box associated with a failed build.
 2. A popup will appear with some information about the build, including the
    builder and buildslave. Click the "Lookup" link next to "Host machine". This
    will bring you to the [SkiaLab Hosts](https://status.skia.org/hosts) page,
    which contains information about the machines in the lab, pre-filtered to
    select the machine which runs the buildslave in question.
 3. The information box will display the hostname of the machine as well as the
    KVM switch and number used to access the machine, if the machine is in the
    SkiaLab.
 4. Walk over to the lab. While standing at the KVM switch indicated by the host
-   information page, double tab <ctrl> and then press the number or letter from
+   information page, double tap \<ctrl\> and then press the number or letter from
    the information page. It may be necessary to move or click the mouse to wake
    the machine up.
 5. Log in to the machine if necessary. The password is stored in
    [Valentine](https://valentine/).
 
 ### Rebooting a problematic Android device
 
 Follow the same process as above, with some slight changes:
 
 1. On the [Status](https://status.skia.org/) page, click the box for the failed
@@ skipping 20 matching lines @@
 
 This assumes that we're just adding a host machine for a new buildbot slave,
 and doesn't cover how to make changes to the buildbot code to change the
 behavior of the builder itself.
 
 1. Obtain the machine itself and place it on the racks in the lab. Connect
    power, ethernet, and KVM cables.
 2. If we already have a disk image appropriate for this machine, follow the
    instructions for flashing a disk image to a machine below. Otherwise, follow
    the instructions for bringing up a new machine from scratch.
-3. Set the hostname for the machine.
-4. Add the new slave to the slaves.cfg file on the appropriate master, eg.
+3. Power on the machine. Be sure to kill any buildbot processes that start up,
+   eg. `killall python` on Linux and Mac, and just close any cmd instances which
+   pop up on Windows.
+4. Set the hostname for the machine.
+5. Ensure that the machine is labeled with its hostname and KVM number.
+6. Add the new slave to the slaves.cfg file on the appropriate master, eg.
    https://chromium.googlesource.com/chromium/tools/build/+/master/masters/master.client.skia/slaves.cfg,
    and upload the change for code review.
-5. Add an entry for the new host machine to the slave_hosts_cfg.py file in the
+7. Add an entry for the new host machine to the slave_hosts_cfg.py file in the
    Skia infra repo: https://skia.googlesource.com/buildbot/+/master/site_config/slave_hosts_cfg.py,
    and upload it for review.
-6. Commit the change to add the slave to the master. Once it lands, commit the
+8. Commit the change to add the slave to the master. Once it lands, commit the
    slave_hosts_cfg.py change immediately afterward.
-7. Restart the build master. Either ask borenet@ to do this or file a
+9. Restart the build master. Either ask borenet@ to do this or file a
    [ticket](https://code.google.com/p/chromium/issues/entry?template=Build%20Infrastructure&labels=Infra-Labs,Restrict-View-Google,Infra-Troopers&summary=Restart%20request%20for%20[%20name%20]&comment=Please%20provide%20the%20reason%20for%20restart.%0A%0ASet%20to%20Pri-0%20if%20immediate%20restarted%20is%20required,%20otherwise%20please%20set%20to%20Pri-1%20and%20the%20restart%20will%20happen%20when%20the%20trooper%20gets%20a%20free%20moment.) for a trooper to do it.
-8. Reboot the machine and monitor the build master to ensure that it connects.
+10. Reboot the machine and monitor the build master to ensure that it connects.
+    This can take some time, since the bot needs to sync Chrome.
 
 
 ### Bringing up a new Android bot
 
 1. Locate or add a host machine. We generally want to keep the number of
    devices attached to each host below 5 or so. If a new host machine is
    required, follow the above instructions for bringing up a new buildbot
    host machine, with the exception that the slave corresponds to the Android
    device, not the host machine itself.
 2. Ensure that the buildslave is not yet running:
@@ skipping 78 matching lines @@
 11. Select the external drive to use for /home/partimag, something like,
     "1000GB_ntfs_My_Passport".
 12. Select the bot_img directory.
 13. "Beginner"
 14. "savedisk"
 15. Choose a name for the disk image. The convention is:
     `skiabot-<hardware type>-<OS>-<disk image revision #>`
 12. Choose the hard drive in the machine. It should be the only option.
 13. "y"
 14. Choose "reboot" or "shut down" when finished.