resolve the warning and review the draft

Author: lucciz01

support/power-platform/dataverse/working-with-solutions/media/missing-dependency-on-solution-import/missing-dependencies-first-party-application.png

@@ -2,7 +2,7 @@
 title: Missing dependencies during solution import in Power Apps
 description: Works around an issue about missing dependencies that occurs when you import a solution in the target environment in Microsoft Power Apps.
 ms.reviewer: matp
-ms.date: 04/17/2025
+ms.date: 07/15/2025
 author: swatimadhukargit
 ms.author: swatim
 ms.custom: sap:Working with Solutions\Dependencies prevent a solution import
@@ -61,18 +61,14 @@ Next to the application name, you'll find an **Install** or **Update** button th
 
   - System administrators can use the **Update** button to open the application update page in the Power Platform admin center.
   - Non-system administrators can use the **Copy Update Link** button to copy the application update link and request their system administrator to update the application.
- 
 
 > [!IMPORTANT]
 > This experience described below might not be available to the environments of all the regions yet.
 
+When a solution depends only on components from first-party Dynamics 365 applications that are missing or outdated in the target environment, the system might be able to automatically update or install these components. In this case, no manual action is required from the user. The **Missing dependencies** page will display a checkbox **Deploy Dependencies**. Selecting this option allows the system to automatically update or install the required components before importing the solution. If the update or installation of a dependent application fails, the solution import will also fail. You can track the status of these updates or installations on the solution history page.
 
-When the solution relies only on components from first party Dynamics 365 applications that are missing or outdated in the target environment. If these components can be auto-updated by the system, no manual install/update is required by the user. The page will show a checkbox **Deploy Dependencies** which will consent the system to automatically update/install the missing components before the import of solution by updating/installing its corresponding application followed by import of the solution. If the update/install of dependent application fails, the import of the solution will fail as well. The status of update/install can be tracked in the solution history page. 
+:::image type="content" source="media/missing-dependency-on-solution-import/missing-dependencies-first-party-application.png" alt-text="Screenshot that shows the Applications section of the Missing dependencies page with first-party application which can be auto installed or updated from the system." lightbox="media/missing-dependency-on-solution-import/missing-dependencies-first-party-application.png":::
 
-:::image type="content" source="media/missing-dependency-on-solution-import/missing-dependencies-1Papplication.png" alt-text="Screenshot that shows the Applications section of the Missing dependencies page with 1P application which can be auto installed/updated from the system." lightbox="media/missing-dependency-on-solution-import/missing-dependencies-1Papplication.png":::
-
-
-  
 ### Missing dependencies coming from another managed solution
 
 This issue occurs when the solution relies on components from another managed solution that's missing in the target environment. You can find these dependencies in the **Managed Solutions** section of the **Missing dependencies** page. Expanding the section provides additional details.