Update missing-dependency-on-solution-import.md

Author: przlplx

support/power-platform/dataverse/working-with-solutions/missing-dependency-on-solution-import.md

@@ -28,7 +28,7 @@ In this situation, you can't continue the solution import until the missing depe
 
 The solution is dependent on a component that exists in the source environment where the solution is deployed. However, the component doesn't exist in the target environment that the solution is imported into.
 
-This issue might occur if applications are upgraded to their latest version through Microsoft scheduled maintenance in the source environment, but they aren't upgraded in the target environment.
+This issue might occur if applications are upgraded to their latest version (through Microsoft scheduled maintenance) in the source environment but not in the target environment.
 
 ## Workaround 1: Resolve missing dependency errors
 
@@ -72,7 +72,7 @@ To work around this issue, use one of the following methods:
 > [!IMPORTANT]
 > This experience might not be available yet in the environments of all regions.
 
-If a solution depends on only 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 displays the **Deploy Dependencies** option. If you select this option, and then select the **Import** button, the system first installs or updates the required dependencies, and then imports the solution. If the update or installation of a dependent application fails, the solution import also fails. You can track the status of these updates or installations on the solution history page.
+A solution might depend on only components from first-party Dynamics 365 applications that are missing or outdated in the target environment. In this situation, the system might be able to automatically update or install these components, and no manual action is required from the user. The **Missing dependencies** page displays the **Deploy Dependencies** option. If you select this option, and then you select the **Import** button, the system first installs or updates the required dependencies, and then imports the solution. If the update or installation of a dependent application fails, the solution import also fails. You can track the status of these updates or installations on the solution history page.
 
 :::image type="content" source="media/missing-dependency-on-solution-import/missing-dependencies-first-party-application.png" alt-text="The Applications section of the Missing dependencies page showing a first-party application that can be auto installed or updated from the system." lightbox="media/missing-dependency-on-solution-import/missing-dependencies-first-party-application.png":::