Acrolinx

Author: Mattp123

powerapps-docs/maker/data-platform/preferred-solution.md

@@ -18,7 +18,7 @@ ms.custom:
 
 By default, unless already in the context of an unmanaged solution, all solution components are stored in the solution named Common Data Services Default Solution. Because there's no separation of components between makers and the Common Data Services Default Solution can't be exported for import to other environments, this typically isn't the best model.
 
-Using preferred solutions is a way to set which solution will support each maker's edits that happen anywhere in Power Apps. It enables makers to view and update which solution they are using. After you set your preferred solution, you can create components in the solution you specify and those components will automatically be in that solution so that you control the components within the solution. Then, you can export your preferred solution and import the solution to other Microsoft Dataverse environments.
+Using preferred solutions is a way to set which solution will support each maker's edits that happen anywhere in Power Apps. It enables makers to view and update which solution they're using. After you set your preferred solution, you can create components in the solution you specify and those components will automatically be in that solution so that you control the components within the solution. Then, you can export your preferred solution and import the solution to other Microsoft Dataverse environments.
 
 ## Prerequisites
 
@@ -50,7 +50,7 @@ You can delete your preferred solution or a preferred solution that other makers
 
 - You can't set or view the preferred solution in the classic solution explorer.
 - Components that are created in the classic solution explorer won't go into the preferred solution.
-- Preferred solution currently doesn't work with cards, dataflows, AI Builder, chatbots, connections, gateways, custom connectors, and canvas apps created from image or a figma design.
+- Preferred solution currently doesn't work with cards, dataflows, AI Builder, chatbots, connections, gateways, custom connectors, and canvas apps created from image or a Figma design.
 - When a component is already part of an existing unmanaged solution, it will still be added to the preferred solution.
 
 ### See also