update airgap images

Author: paigecalvert

docs/enterprise/updating-licenses.md

@@ -14,7 +14,7 @@ To update licenses in online environments:
 
    [View a larger version of this image](/images/online-license-tab.png)
 
-   When the license is updated, KOTS makes a new version available that includes the license changes and a dialog is displayed:
+   When the license is updated, KOTS makes a new version available that includes the license changes:
 
    ![License updated successfully](/images/kots-license-update-message.png)
 
@@ -26,7 +26,7 @@ To update licenses in online environments:
 
 1. In the dialog, click **Go to new version** to navigate to the **Version history** page.
 
-1. On the **Version history** page, next to the new version labeled **License Change**, click **Deploy** then **Yes, Deploy**.
+1. On the **Version history** page, next to the new version labeled **License Change**, click **Deploy** then **Yes, deploy**.
 
     ![Deploy license change](/images/kots-deploy-license-change.png)
 
@@ -40,12 +40,41 @@ To update licenses in online environments:
 
 ## Update Air Gap Licenses
 
-Click **Upload license** on the right side of the license pane and select the latest license from your machine.
+To update licenses in air gap environments:
 
-![Airgap License](/images/airgap-license-tab.png)
+1. Download the new license. Ensure that it is available on the air gapped machine where KOTS and the application are installed. 
 
-- A **License is already up to date** note appears if no changes are detected.
-- A **License uploaded successfully** note appears when the changes are successfully applied.
+1. In the Admin Console, go to the **License** tab.
+
+1. Click **Upload license** and select the new license from your machine.
+
+   ![Airgap License](/images/airgap-license-tab.png)
+
+   [View a larger version of this image](/images/airgap-license-tab.png)
+
+   When the license is updated, KOTS makes a new version available that includes the license changes:
+
+   ![License updated successfully](/images/kots-airgap-license-update-message.png)
+
+   [View a larger version of this image](/images/kots-airgap-license-update-message.png)
+
+   :::note
+   If no changes are detected, a **License is already up to date** message appears.
+   :::
+
+1. In the dialog, click **Go to new version** to navigate to the **Version history** page.
+
+1. On the **Version history** page, next to the new version labeled **License Change**, click **Deploy** then **Yes, deploy**.
+
+    ![Deploy license change](/images/kots-deploy-license-change.png)
+
+    [View a larger version of this image](/images/kots-deploy-license-change.png)
+
+    The version with the license change is then displayed as the currently deployed version, as shown belowå: 
+
+    ![Currently deployed version](/images/kots-license-change-currently-deployed.png)
+
+    [View a larger version of this image](/images/kots-license-change-currently-deployed.png)
 
 ## Upgrade from a Community License
 
@@ -54,4 +83,4 @@ If you have a community license, you can change your license by uploading a new
 To change a community license to another license:
 
 1. In the **License** tab of the Admin Console, click **Change license**.
-1. In the dialog, upload the new license file.
+1. In the dialog, upload the new license file.

docs/vendor/licenses-about.mdx

@@ -43,17 +43,6 @@ Built-in fields are reserved field names. You can specify the values for these f
 
 You can also create custom license fields to define entitlements specific to the customer. For example, you can create a custom license field to limit the number of active users permitted. For more information about creating custom license fields, see [Managing Custom License Fields](licenses-adding-custom-fields).
 
-## About License Expiration Handling {#expiration}
-
-The built-in `expires_at` license field defines the expiration date for a customer license. When you set an expiration date in the Vendor Portal, the `expires_at` field is set to midnight UTC on the date selected.
-
-Replicated enforces the following logic when a license expires:
-* By default, instances with expired licenses continue to run.
-   To change the behavior of your application when a license expires, you can can add custom logic in your application that queries the `expires_at` field using the Replicated SDK in-cluster API. For more information, see [Querying Entitlements with the Replicated SDK API](/vendor/licenses-reference-sdk).
-* Expired licenses cannot log in to the Replicated registry to pull a Helm chart for installation or upgrade.
-* Expired licenses cannot pull application images through the proxy service or from the Replicated registry.
-* (KOTS Only) KOTS prevents instances with expired licenses from receiving updates.
-
 ## About Updating Licenses
 
 This section includes information about making changes to customer licenses, including editing license details in the Vendor Portal as well as updating or replacing licenses in customer installations.
@@ -95,6 +84,17 @@ Community licenses are the only license type that can be replaced with a new lic
 
 Unless the existing customer is using a community license, it is not possible to replace one license with another license without reinstalling the application. When you need to make changes to a customer's entitlements, Replicated recommends that you edit the customer's license details in the Vendor Portal, rather than issuing a new license.
 
+## About License Expiration Handling {#expiration}
+
+The built-in `expires_at` license field defines the expiration date for a customer license. When you set an expiration date in the Vendor Portal, the `expires_at` field is set to midnight UTC on the date selected.
+
+Replicated enforces the following logic when a license expires:
+* By default, instances with expired licenses continue to run.
+   To change the behavior of your application when a license expires, you can can add custom logic in your application that queries the `expires_at` field using the Replicated SDK in-cluster API. For more information, see [Querying Entitlements with the Replicated SDK API](/vendor/licenses-reference-sdk).
+* Expired licenses cannot log in to the Replicated registry to pull a Helm chart for installation or upgrade.
+* Expired licenses cannot pull application images through the proxy service or from the Replicated registry.
+* (KOTS Only) KOTS prevents instances with expired licenses from receiving updates.
+
 ## About Customer Channel Assignment {#channel-assignment}
 
 This section provides information about managing the channel a customer is assigned, including changing the assigned channel and manaing channel assignments for customers with or without the KOTS entitlement. For information about how to assign a customer to a channel, see [Create a Customer](releases-creating-customer#create-a-customer) in _Creating and Managing Customers_.