Fix a couple minor typos in auto_bisect.

tools/auto_bisect/bisect_perf_regression.py

 #!/usr/bin/env python
 # Copyright 2013 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 """Chromium auto-bisect tool
 
 This script bisects a range of commits using binary search. It starts by getting
 reference values for the specified "good" and "bad" commits. Then, for revisions
 in between, it will get builds, run tests and classify intermediate revisions as
@@ skipping 59 matching lines @@
 
 # The script is in chromium/src/tools/auto_bisect. Throughout this script,
 # we use paths to other things in the chromium/src repository.
 
 # Possible return values from BisectPerformanceMetrics.RunTest.
 BUILD_RESULT_SUCCEED = 0
 BUILD_RESULT_FAIL = 1
 BUILD_RESULT_SKIPPED = 2
 
 # The confidence percentage we require to consider the initial range a
-# regression based on the test results of the inital good and bad revisions.
+# regression based on the test results of the initial good and bad revisions.
 REGRESSION_CONFIDENCE = 80
 # How many times to repeat the test on the last known good and first known bad
 # revisions in order to assess a more accurate confidence score in the
 # regression culprit.
 BORDER_REVISIONS_EXTRA_RUNS = 2
 
 # Patch template to add a new file, DEPS.sha under src folder.
 # This file contains SHA1 value of the DEPS changes made while bisecting
 # dependency repositories. This patch send along with DEPS patch to try server.
 # When a build requested is posted with a patch, bisect builders on try server,
@@ skipping 831 matching lines @@
         fetch_build_func, builder_name, self.opts.builder_type,
         build_request_id, build_timeout)
     if not archive_filename:
       logging.warn('%s [revision: %s]', error_msg, git_revision)
     return archive_filename
 
   def _UnzipAndMoveBuildProducts(self, downloaded_file, build_dir,
                                  build_type='Release'):
     """Unzips the build archive and moves it to the build output directory.
 
-    The build output directory is whereever the binaries are expected to
+    The build output directory is wherever the binaries are expected to
     be in order to start Chrome and run tests.
 
     TODO: Simplify and clarify this method if possible.
 
     Args:
       downloaded_file: File path of the downloaded zip file.
       build_dir: Directory where the the zip file was downloaded to.
       build_type: "Release" or "Debug".
 
     Returns:
@@ skipping 1872 matching lines @@
       # bugs. If you change this, please update the perf dashboard as well.
       bisect_utils.OutputAnnotationStepStart('Results')
     print 'Runtime Error: %s' % e
     if opts.output_buildbot_annotations:
       bisect_utils.OutputAnnotationStepClosed()
   return 1
 
 
 if __name__ == '__main__':
   sys.exit(main())