Fixing errors

Author: limwainstein

articles/defender-for-iot/organizations/ot-deploy/on-premises-management-console-retirement.md

@@ -18,7 +18,7 @@ The on-premises management console will be retired on **January 1, 2025** with t
     - You can still use 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). [ ](../release-notes.md)  
+    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 console on version 24.1.2, and you upgrade to version 24.1.6, you can no longer use the on-premises management console.
 

articles/defender-for-iot/organizations/ot-deploy/transition-on-premises-management-console-to-cloud.md

@@ -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-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":::
+:::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":::
 
 ## How to manage the transition period