Typo police.

BUG=none
TEST=none

Review URL: http://codereview.chromium.org/6802015

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@80671 0039d316-1c4b-4281-b951-d872f2087c98

5 files changed, 18 insertions, 18 deletions

diff --git a/chrome/installer/mac/dirdiffer.sh b/chrome/installer/mac/dirdiffer.sh
index 6c2957f..6c9b3d1 100755
--- a/chrome/installer/mac/dirdiffer.sh
+++ b/chrome/installer/mac/dirdiffer.sh
@@ -1,6 +1,6 @@
 #!/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.
 
@@ -63,7 +63,7 @@
 #   matches this pattern, dirdiffer will also ignore the directory's contents.
 # DIRDIFFER_NO_DIFF
 #   When an entry in new_dir matches this regular expression, it will not be
-#   represented in patch_dir by a $gbs file prepared by goobsdif. It will only
+#   represented in patch_dir by a $gbs file prepared by goobsdiff. It will only
 #   appear as a $bz2, $gz, or $raw file. Only files in new_dir, not
 #   directories,  will be matched against this regular expression.
 #
@@ -433,7 +433,7 @@ verify_patch_dir() {
 
 # 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
diff --git a/chrome/installer/mac/dirpatcher.sh b/chrome/installer/mac/dirpatcher.sh
index 223e82c..e313cbd 100755
--- a/chrome/installer/mac/dirpatcher.sh
+++ b/chrome/installer/mac/dirpatcher.sh
@@ -1,6 +1,6 @@
 #!/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.
 
@@ -283,7 +283,7 @@ patch_dir() {
 
 # 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
diff --git a/chrome/installer/mac/dmgdiffer.sh b/chrome/installer/mac/dmgdiffer.sh
index 17676a7..313f184 100755
--- a/chrome/installer/mac/dmgdiffer.sh
+++ b/chrome/installer/mac/dmgdiffer.sh
@@ -1,6 +1,6 @@
 #!/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.
 
@@ -30,7 +30,7 @@
 # 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
@@ -129,7 +129,7 @@ mount_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() {
@@ -393,7 +393,7 @@ make_patch_dmg() {
 
 # 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
diff --git a/chrome/installer/mac/keystone_install.sh b/chrome/installer/mac/keystone_install.sh
index 8ec43059..f0e8a79 100755
--- a/chrome/installer/mac/keystone_install.sh
+++ b/chrome/installer/mac/keystone_install.sh
@@ -1,6 +1,6 @@
 #!/bin/bash -p
 
-# Copyright (c) 2009 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.
 
@@ -227,7 +227,7 @@ ensure_writable_symlink() {
 }
 
 # ensure_writable_symlinks_recursive calls ensure_writable_symlink for every
-# symbolic link in |directory|, recursivley.
+# symbolic link in |directory|, recursively.
 #
 # In some very weird and rare cases, it is possible to wind up with a user
 # installation that contains symbolic links that the user does not have write
@@ -242,7 +242,7 @@ ensure_writable_symlink() {
 # application to /Applications, resulting in the program's user being set to
 # the user's own ID.  If, subsequently, a .pkg package is installed over that,
 # the existing directory ownership will be preserved, but file ownership will
-# be changed to whateer is specified by the package, typically root.  This
+# be changed to whatever is specified by the package, typically root.  This
 # applies to symbolic links as well.  On a subsequent update, rsync will be
 # able to copy the new files into place, because the user still has permission
 # to write to the directories.  If the symbolic link targets are not changing,
@@ -672,7 +672,7 @@ main() {
   # bootstrap installations, which just have an empty .app directory.  Only
   # require it when doing a patch update, and use it to validate that the
   # patch applies to the old installed version.  By definition, skeleton
-  # bootstraps can't be installed with patch udpates.  They require the full
+  # bootstraps can't be installed with patch updates.  They require the full
   # application on the disk image.
   if [[ -n "${is_patch}" ]]; then
     if [[ -z "${old_version_app}" ]]; then
@@ -714,7 +714,7 @@ main() {
   # Make sure that ${installed_versions_dir} exists, so that it can receive
   # the versioned directory.  It may not exist if updating from an older
   # version that did not use the versioned layout on disk.  Later, during the
-  # rsync to copy the applciation directory, the mode bits and timestamp on
+  # rsync to copy the application directory, the mode bits and timestamp on
   # ${installed_versions_dir} will be set to conform to whatever is present in
   # the update.
   #
@@ -1060,7 +1060,7 @@ main() {
   # To determine which directories are in use, both ps and lsof are used.
   # Each approach has limitations.
   #
-  # The ps check looks for processes within the verisoned directory.  Only
+  # The ps check looks for processes within the versioned directory.  Only
   # helper processes, such as renderers, are within the versioned directory.
   # Browser processes are not, so the ps check will not find them, and will
   # assume that a versioned directory is not in use if a browser is open
@@ -1076,7 +1076,7 @@ main() {
   # root, the lsof check can only find processes running as the effective user
   # performing the update.
   #
-  # These limitations are motiviations to additionally preserve the versioned
+  # These limitations are motivations to additionally preserve the versioned
   # directory corresponding to the version that was just replaced.
   note "cleaning up old versioned directories"
 
diff --git a/chrome/installer/mac/sign_versioned_dir.sh.in b/chrome/installer/mac/sign_versioned_dir.sh.in
index bfda849..4affd5e 100644
--- a/chrome/installer/mac/sign_versioned_dir.sh.in
+++ b/chrome/installer/mac/sign_versioned_dir.sh.in
@@ -1,6 +1,6 @@
 #!/bin/bash -p
 
-# Copyright (c) 2009 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.
 
@@ -34,7 +34,7 @@ codesign_id="${3}"
 
 versioned_dir="${app_path}/Contents/Versions/@VERSION@"
 
-# An .app bundle to be signed can be signed directly. Normally, signging a
+# An .app bundle to be signed can be signed directly. Normally, signing a
 # framework bundle requires that each version within be signed individually.
 # http://developer.apple.com/mac/library/technotes/tn2007/tn2206.html#TNTAG13
 # In Chrome's case, the framework bundle is unversioned, so it too can be