add partials to the updating docs

Author: paigecalvert

docs/enterprise/installing-existing-cluster-airgapped.mdx

@@ -43,7 +43,9 @@ To install in an air gap cluster with KOTS:
 
    <AirGapLicense/>
 
-1. <BuildAirGapBundle/>
+1. Go the channel where the target release was promoted to build and download the air gap bundle for the release:
+
+   <BuildAirGapBundle/>
 
 1. <AirGapBundle/>
 

docs/enterprise/installing-kurl-airgap.mdx

@@ -36,7 +36,9 @@ To install an application with kURL:
 
    <AirGapLicense/>
 
-1. <BuildAirGapBundle/>
+1. Go the channel where the target release was promoted to build and download the air gap bundle for the release:
+
+   <BuildAirGapBundle/>
 
 1. <AirGapBundle/>
 

docs/enterprise/updating-app-manager.mdx

@@ -1,6 +1,7 @@
 import AdminConsole from "../partials/updating/_admin-console.mdx"
 import AdminConsoleAirGap from "../partials/updating/_admin-console-air-gap.mdx"
 import PushKotsImages from "../partials/install/_push-kotsadm-images.mdx"
+import BuildAirGapBundle from "../partials/install/_build-airgap-bundle.mdx"
 
 # Performing Updates in Existing Clusters
 
@@ -43,7 +44,11 @@ Add the `--deploy` flag to automatically deploy this version.
 
 To update an application in air gap environments:
 
-1. Get the new `.airgap` bundle for the target application release and ensure that it is available on your local machine.
+1. In the [Vendor Portal](https://vendor.replicated.com), go the channel where the target release is promoted to build and download the new `.airgap` bundle:
+   
+   <BuildAirGapBundle/>
+
+1. Ensure that you can access the downloaded bundle from the environment where the Admin Console is running.
 
 1. Run the following command to update the application:
 
@@ -57,7 +62,7 @@ To update an application in air gap environments:
     ```
     Replace:
     * `APP_SLUG` with the unique slug for the application. See [Get the Application Slug](/vendor/vendor-portal-manage-app#slug) in _Managing Applications_.
-    * `NEW_AIRGAP_BUNDLE` with the `.airgap` bundle for the target application version. See [Download Air Gap Bundles from the Download Portal](/vendor/releases-download-airgap-bundles#download-portal).
+    * `NEW_AIRGAP_BUNDLE` with the `.airgap` bundle for the target application version.
     * `REGISTRY_HOST` with the private registry that contains the Admin Console images.
     * `REGISTRY_NAMESPACE` with the registry namespace where the images are hosted (Optional). 
     * `RO_USERNAME` and `RO_PASSWORD` with the username and password for an account that has read-only access to the private registry.

docs/enterprise/updating-kurl.mdx

@@ -65,7 +65,7 @@ To update the kURL cluster in an air gap environment:
 
 1. Repeat the following steps on each node in the cluster to download and extract the kURL `.tar.gz` air gap bundle for the updated spec:
 
-   1. Download the `.tar.gz` air gap bundle for the kURL installer. kURL air gap bundles can be downloaded from the channel where the given release is promoted:
+   1. Download the kURL `.tar.gz` air gap bundle from the channel where the new kURL installer spec is promoted:
 
       * To download the kURL air gap bundle for the Stable channel:
 

docs/partials/install/_build-airgap-bundle.mdx

@@ -1,14 +1,10 @@
-Go the channel where the target release was promoted to build and download the air gap bundle for the release:
-   * If the **Automatically create airgap builds for newly promoted releases in this channel** setting is enabled on the channel, watch for the build status to complete.
-   * If automatic air gap builds are not enabled, go to the **Release history** page for the channel and build the air gap bundle manually. 
+* If the **Automatically create airgap builds for newly promoted releases in this channel** setting is enabled on the channel, watch for the build status to complete.
+* If automatic air gap builds are not enabled, go to the **Release history** page for the channel and build the air gap bundle manually. 
 
-     <img alt="Release history link on a channel card" src="/images/release-history-link.png" width="400px"/>
+   <img alt="Release history link on a channel card" src="/images/release-history-link.png" width="400px"/>
 
-     [View a larger version of this image](/images/release-history-link.png)
+   [View a larger version of this image](/images/release-history-link.png)
 
-     ![Build button on the Release history page](/images/release-history-build-airgap-bundle.png)
+   ![Build button on the Release history page](/images/release-history-build-airgap-bundle.png)
 
-    [View a larger version of this image](/images/release-history-build-airgap-bundle.png)
-
-
-     
+   [View a larger version of this image](/images/release-history-build-airgap-bundle.png)    

docs/partials/updating/_admin-console-air-gap.mdx

@@ -1,6 +1,12 @@
+import BuildAirGapBundle from "../install/_build-airgap-bundle.mdx"
+
 To perform an air gap update from the Admin Console:
 
-1. Download the `.airgap` bundle for the new application version. Ensure that you can access the downloaded bundle from the environment where the Admin Console is running.
+1. In the [Vendor Portal](https://vendor.replicated.com), go the channel where the target release is promoted to build and download the new `.airgap` bundle:
+   
+   <BuildAirGapBundle/>
+
+1. Ensure that you can access the downloaded bundle from the environment where the Admin Console is running.
 1. In the Admin Console, go to the **Version History** tab.
 1. Click **Upload a new version**.