Fix typos in documentation

proposals/kapp/001-crd-upgrade-safety/README.md

@@ -86,7 +86,7 @@ The `CRDUpgradeSafety` preflight check is a very nuanced preflight check and dif
 - Only issue warnings about potential problems
 - Fail closed/open
 
-In order to accomodate this configurability without introducing various versions of the same preflight check, the ability to specify preflight configurations will be added to the existing [`kapp` configuration file](https://carvel.dev/kapp/docs/v0.60.x/config/).
+In order to accommodate this configurability without introducing various versions of the same preflight check, the ability to specify preflight configurations will be added to the existing [`kapp` configuration file](https://carvel.dev/kapp/docs/v0.60.x/config/).
 
 As an example, configuring a preflight check could look something like:
 

site/content/imgpkg/docs/develop/air-gapped-workflow.md

@@ -30,7 +30,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.24.0/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.25.0/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.26.0/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.27.0/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.28.0/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.29.0/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.30.0/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.31.0/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.32.0/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.33.0/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.34.0/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.35.x/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.36.x/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.37.x/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.38.x/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.39.x/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.40.x/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.41.x/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.42.x/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.43.x/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.44.x/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.45.0/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/imgpkg/docs/v0.46.x/air-gapped-workflow.md

@@ -31,7 +31,7 @@ If you are trying to bundle your own or third-part software, you will need to cr
 
 You have two options how to transfer bundle from one registry to another:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 ### Option 1: From a location connected to both registries

site/content/kapp-controller/docs/v0.31.0/air-gapped-workflow.md

@@ -23,7 +23,7 @@ Most of the steps documented for the [imgpkg air-gapped workflow docs](/imgpkg/d
 still apply in the case of working with kapp-controller package repositories. A summary of these docs is that you will need to copy your package repository 
 bundle with `imgpkg` via one of the following options:
 
-- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transfered between registries.
+- Option 1: From a common location connected to both registries. This option is more efficient because only changed image layers will be transferred between registries.
 - Option 2: With intermediate tarball. This option works best when registries have no common network access.
 
 More detailed documents for [`Option 1`](/imgpkg/docs/latest/air-gapped-workflow/#option-1-from-a-location-connected-to-both-registries) and