Typo police.

chrome/installer/mac/dmgdiffer.sh

 #!/bin/bash -p
 
-# Copyright (c) 2010 The Chromium Authors. All rights reserved.
+# Copyright (c) 2011 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.
 
 # usage: dmgdiffer.sh old_dmg new_dmg patch_dmg
 #
 # dmgdiffer creates a disk image containing a binary update able to patch
 # a product originally distributed in old_dmg to the version in new_dmg. Much
 # of this script is generic, but the make_patch_fs function is specific to
 # a product: in this case, Google Chrome.
 #
 # This script operates by mounting old_dmg and new_dmg, creating a new
 # filesystem structure containing dirpatches generated by dirdiffer and
 # goobsdiff (which should be located in the same directory as this script),
 # and producing a disk image from that structure.
 #
 # The Chrome make_patch_fs function produces an disk image that is able to
 # update a single old version on any Keystone channel to a new version on a
 # specific Keystone channel (the Keystone channel associated with new_dmg).
 # Chrome's updates are split into two dirpatches: one updates the old
 # versioned directory to the new one, and the other updates the remainder of
 # the application. The versioned directory is split out from the rest because
 # it contains the bulk of the application and its name changes from version to
 # version, and dirdiffer/dirpatcher do not directly handle name changes. This
 # approach also allows the versioned directory dirpatch to be applied in-place
 # in most cases during an update, rather than relying on a temporary
 # directory. In order to allow a single update dmg to apply to an old version
 # on any Keystone channel, several small files are never distributed as diffs,
 # and only as full (possibly compressed) versions of the new files. These
 # files include the outer application's Info.plist which contains Keystone
-# channel information, and anything created or modified by code-signinig the
+# channel information, and anything created or modified by code-signing the
 # outer application.
 #
 # Application of update disk images produced by this script is
 # product-specific. With updates managed by Keystone, the update disk images
 # can contain a .keystone_install script that is able to locate and update
 # the installed product.
 #
 # Exit codes:
 #  0  OK
 #  1  Unknown failure
@@ skipping 78 matching lines @@
 }
 
 # make_patch_fs is responsible for comparing the old and new disk images
 # mounted at old_fs and new_fs, respectively, and populating patch_fs with the
 # contents of what will become a disk image able to update old_fs to new_fs.
 # It then outputs a string which will be used as the volume name of the
 # patch_dmg.
 #
 # The entire patch contents are placed into a .patch directory to hide them
 # from ordinary view. The disk image will be given a volume name like
-# "Google Chrome 5.0.375.55-5.0.375.70" as an identifying aide, although
+# "Google Chrome 5.0.375.55-5.0.375.70" as an identifying aid, although
 # uniqueness is not important and users will never interact directly with
 # them.
 make_patch_fs() {
   local old_fs="${1}"
   local new_fs="${2}"
   local patch_fs="${3}"
 
   readonly PRODUCT_NAME="Google Chrome"
   readonly APP_NAME="${PRODUCT_NAME}.app"
   readonly APP_NAME_RE="${PRODUCT_NAME}\\.app"
@@ skipping 243 matching lines @@
   unset g_cleanup_mount_points[${#g_cleanup_mount_points[@]}]
 
   package_patch_dmg "${patch_fs}" "${patch_dmg}" "${volume_name}" "${temp_dir}"
 
   rm -rf "${temp_dir}"
   unset g_cleanup[${#g_cleanup[@]}]
 }
 
 # shell_safe_path ensures that |path| is safe to pass to tools as a
 # command-line argument. If the first character in |path| is "-", "./" is
-# prepended to it. The possibily-modified |path| is output.
+# prepended to it. The possibly-modified |path| is output.
 shell_safe_path() {
   local path="${1}"
   if [[ "${path:0:1}" = "-" ]]; then
     echo "./${path}"
   else
     echo "${path}"
   fi
 }
 
 usage() {
@@ skipping 33 matching lines @@
   trap - EXIT
 }
 
 if [[ ${#} -ne 3 ]]; then
   usage
   exit 2
 fi
 
 main "${@}"
 exit ${?}