Acrolinx

Author: Simonx Xu

support/dynamics-365/sales/button-in-command-bar-not-appear-after-grid-item-selection.md

@@ -6,7 +6,7 @@ ms.topic: troubleshooting
 ms.date: 03/31/2021
 ms.custom: sap:Opportunity
 ---
-# Button in command bar does not appear after grid item selection in Microsoft Dynamics CRM Online
+# Button in command bar doesn't appear after grid item selection in Microsoft Dynamics CRM Online
 
 This article provides a resolution for the issue that the button customized to show doesn't appear as expected after one or more grid items are selected in Microsoft Dynamics CRM Online.
 
@@ -30,11 +30,11 @@ This means that buttons that don't require an item to be selected, will simply n
 The method that the determination is made is based on whether the command associated with the ribbon button has a SelectionCount rule. If it has a SelectionCount rule, it's considered to be an *item-specific* command.
 
 > [!NOTE]
-> Flyouts and split buttons are excluded from this change, and still shown in both cases of when items are selected or not. This is to ensure that menu items, some of which may be generated dynamically, is not incorrectly hidden.
+> Flyouts and split buttons are excluded from this change, and still shown in both cases of when items are selected or not. This is to ensure that menu items, some of which may be generated dynamically, isn't incorrectly hidden.
 
 ## Resolution
 
-This is designed behavior, that affects all buttons, not just custom buttons, but out of box buttons as well (Note - flyouts and split buttons excluded since they have a menu with further child buttons and cannot be easily categorized). This is an explicit design change from web client to Unified Client.
+This is designed behavior that affects all buttons not just custom buttons, but out of box buttons as well (Note - flyouts and split buttons excluded since they have a menu with further child buttons and can't be easily categorized). This is an explicit design change from web client to Unified Client.
 
 In most cases, it's helpful to hide buttons that don't act on selected items, so that *item-specific* commands appear more prominently.
 

support/power-platform/dataverse/environment-app-access/error-when-accessing-app-module.md

@@ -23,7 +23,7 @@ User does not have a license to access this app module uniqueName=< unique name>
 
 ## Cause
 
-This issue occurs when an application requires a license and the administrator hasn't assigned the appropriate license to the user(s) of the application.
+This issue occurs when an application requires a license and the administrator hasn't assigned the appropriate license to the users of the application.
 
 For example, if the user with a team member license tries to access the Customer Service Hub application, the user will see this error:
 
@@ -41,4 +41,4 @@ The resolution is to reach out to your administrator and request the license to
 
 **Access to Custom Apps:**
 
-For access to custom apps (canvas or model-driven), you need to be assigned a Dynamics 365 Enterprise or Professional license, **Power AppsPer User** plan or the environment needs to be given **Power Appsper app** plans (aka **app passes**). For more information about **Power Appsper app** plans (aka **app passes**), see [About Power Apps per app plans](/power-platform/admin/about-powerapps-perapp).
+For access to custom apps (canvas or model-driven), you need to be assigned a Dynamics 365 Enterprise or Professional license, **Power AppsPer User** plan or the environment needs to be given **Power Appsper app** plans (also known as **app passes**). For more information about **Power Appsper app** plans (also known as **app passes**), see [About Power Apps per app plans](/power-platform/admin/about-powerapps-perapp).

support/power-platform/dataverse/working-with-solutions/error-code-80048539-when-importing-solution-patch.md

@@ -35,32 +35,32 @@ Solution manifest import: FAILURE: Holding solution MyPatchTesting_Upgrade alrea
 ## Cause
 
 > [!NOTE]
-> If you are using make.powerapps.com to import your unmanaged solution update and get this error Microsoft is aware of the issue and is working on a fix. To work around the issue open the **Advanced** settings and select the option **Update (not recommended)**.
+> If you're using make.powerapps.com to import your unmanaged solution update and get this error Microsoft is aware of the issue and is working on a fix. To work around the issue open the **Advanced** settings and select the option **Update (not recommended)**.
 
 Error code **80048539** indicates an invalid patch is being imported. There are a few potential causes including the following:
 
 ### Cause 1
 
 If you see the error details mentioned in the Symptom 1 Details section mentioned above:
 
-The solution patch version is lower than the version of the solution already installed. For example: A solution named SolutionA is already installed with version 1.1.0.0 and you are trying to import a patch that is version 1.0.1.0.
+The solution patch version is lower than the version of the solution already installed. For example: A solution named SolutionA is already installed with version 1.1.0.0 and you're trying to import a patch that is version 1.0.1.0.
 
 ### Cause 2
 
 If you see the error details mentioned in the Symptom 2 Details section mentioned above:
 
-This can occur if you already have an upgrade imported for that solution but it has not yet been applied. After importing a solution that is an upgrade of an existing solution, the end of the solution import provides a button to apply the solution upgrade. If you did not select that button during a prior import of a solution upgrade for this solution, you need to locate the solution in your solutions list and select the **Apply Solution Upgrade** button.
+This can occur if you already have an upgrade imported for that solution but it hasn't yet been applied. After importing a solution that is an upgrade of an existing solution, the end of the solution import provides a button to apply the solution upgrade. If you didn't select that button during a prior import of a solution upgrade for this solution, you need to locate the solution in your solutions list and select the **Apply Solution Upgrade** button.
 
 ## Resolution
 
 ### Resolution 1
 
 If you see the error details mentioned in the Symptom 1 Details section mentioned above:
 
-Verify the solution patch version you are trying to import is a higher version than the solution already installed.
+Verify the solution patch version you're trying to import is a higher version than the solution already installed.
 
 ### Resolution 2
 
 If you see the error details mentioned in the Symptom 2 Details section mentioned above:
 
-Navigate to **Settings**, **Customizations**, and then select **Solutions**. Select the existing installed solution you are trying to upgrade and then select **Apply Solution Upgrade**.
+Navigate to **Settings**, **Customizations**, and then select **Solutions**. Select the existing installed solution you're trying to upgrade and then select **Apply Solution Upgrade**.