Tweaking sections and TOC

Author: limwainstein

articles/defender-for-iot/organizations/TOC.yml

@@ -56,13 +56,7 @@
 - name: Deploy OT monitoring
   items:
   - name: OT deployment path
-    href: ot-deploy/ot-deploy-path.md
-  - name: On-premises management console retirement
-    items:
-    - name: On-premises management console retirement
-      href: ot-deploy/on-premises-management-console-retirement.md
-    - name: Transition to the cloud
-      href: ot-deploy/transition-on-premises-management-console-to-cloud.md
+    href: ot-deploy/ot-deploy-path.md  
   - name: Plan and prepare for an OT deployment
     items:
     - name: Plan your OT monitoring system
@@ -136,8 +130,17 @@
       href: ot-deploy/update-device-inventory.md
     - name: Create a learned baseline of OT alerts
       href: ot-deploy/create-learned-baseline.md
-  - name: Deploy in hybrid or air-gapped environments
-    href: ot-deploy/air-gapped-deploy.md
+  - name: Hybrid or air-gapped environments
+    items:
+    - name: Deploy hybrid or air-gapped
+      href: ot-deploy/air-gapped-deploy.md   
+    - name: On-premises management console
+      items:
+      - name: On-premises management console retirement
+        href: ot-deploy/on-premises-management-console-retirement.md
+      - name: Transition to the cloud
+        href: ot-deploy/transition-on-premises-management-console-to-cloud.md
+        
 - name: Tutorials
   items:
   - name: Onboard and activate a virtual OT sensor

articles/defender-for-iot/organizations/media/on-premises-architecture/transition-new.png

@@ -9,23 +9,24 @@ ms.date: 12/17/2024
 
 This article describes the retirement of the on-premises management console from **January 1, 2025**.
 
-### Retirement timeline of the Central Manager
+### Retirement details
 
 The on-premises management console will be retired on **January 1, 2025** with the following updates/changes:
 
 - Sensor versions released after **January 1, 2025** won't be managed by an on-premises management console. 
 - For versions released prior to **January 1, 2025**: 
     - You can still use the on-premises management console. 
-    - In these versions, Defender for IoT no longer provides support service or maintains the on-premises management console. 
+    - Defender for IoT no longer provides support service or maintains the on-premises management console. 
 
     For a list of supported versions, see [OT monitoring software versions](release-notes.md).    
 
-- Following any version upgrade, you will no longer be able to use the on-premises management console. For example, if you're using the on-premises management portal on version 24.1.2, and you upgrade to version 24.1.6, you can no longer use the on-premises management console.
+- Following any version upgrade, you will no longer be able to use the on-premises management console. For example, if you're using the on-premises management console on version 24.1.2, and you upgrade to version 24.1.6, you can no longer use the on-premises management console.
 
 ## Air-gapped sensor support
 
-- Air-gapped sensor support isn't affected by these changes to the on-premises management console support. We continue to support air-gapped deployments and assist with the [transition to the cloud](transition-on-premises-management-console-to-cloud.md). The sensors retain a full user interface so that they can be used in "lights out" scenarios and continue to analyze and secure the network in the event of an outage.
-- Air-gapped sensors that can't connect to the cloud can be managed directly via the sensor console UI, CLI, or API.
+Air-gapped sensor support isn't affected by the on-premises management console retirement. We continue to support air-gapped deployments and assist with the [transition to the cloud](transition-on-premises-management-console-to-cloud.md). The sensors retain a full user interface so that they can be used in "lights out" scenarios and continue to analyze and secure the network in the event of an outage.
+
+Air-gapped sensors that can't connect to the cloud can be managed directly via the sensor console UI, CLI, or API.
 
 ## Next steps
 

articles/defender-for-iot/organizations/media/on-premises-architecture/transition.png

@@ -19,7 +19,7 @@ Our [current architecture guidance](#architecture-guidance) is designed to be mo
 
 If you're an existing customer using an on-premises management console to manage your OT sensors, we recommend transitioning to the updated architecture guidance. The following image shows a graphical representation of the transition steps to the new recommendations:
 
-:::image type="content" source="../media/on-premises-architecture/transition.png" alt-text="Diagram of the transition from a legacy on-premises management console to the newer recommendations." border="false" lightbox="../media/on-premises-architecture/transition.png":::
+:::image type="content" source="../media/on-premises-architecture/transition-new.png" alt-text="Diagram of the transition from a legacy on-premises management console to the newer recommendations." border="false" lightbox="../media/on-premises-architecture/transition.png":::
 
 ## How to manage the transition period