Wording updates on ACE design guidance

Author: VesaJuvonen

docs/spfx/viva/design/designing-card.md

@@ -31,7 +31,7 @@ Each dashboard card has the following elements:
 
 Icons from the pre-defined set are theme-friendly and will automatically adjust to light and dark themes using theme primary color.
 
-For customized icons, maximum size is 24px by 24px. Recommended formats are PNG or SVG. SVG icons scale better across different screen resolutions. Please make sure the icon has a transparent background, and it looks good both on light and dark theme. Learn about SharePoint themes.
+For customized icons, maximum size is 24 px by 24 px. Recommended formats are PNG or SVG. SVG icons scale better across different screen resolutions. Make sure the icon has a transparent background, and it looks good both on light and dark theme. Learn about SharePoint themes.
 
 1. Title: Typically the app name. All titles should be in sentence case.
 
@@ -49,7 +49,7 @@ There are three types of cards layouts available to choose from.
 - Heading + Image
 - Heading + Description
 
-All layouts come in two sizes: medium or large. Card size will determine how the space in the dashboard is utilized. It's useful to start with medium size cards. Try and use large size card if they are needed to showcase additional info that does not fit in the medium size.
+All layouts come in two sizes: medium or large. Card size will determine how the space in the dashboard is utilized. It's useful to start with medium size cards. Use large size card if they are needed to showcase additional info that does not fit in the medium size.
 
 #### Heading​​​​​​​
 
@@ -86,7 +86,7 @@ Here are the best practices for designing card interactions:
 - The overall card should always be interactive.
 - If the primary button is used, because of its visual prominence, it should be the most important action on the card.
 - The secondary button can used either on its own or in conjunction with the primary button if two actions are needed (only available in large size card layouts). If it's used with the primary button, make sure it is linked to the second most important action on the card. In that case, the card itself will become the least important action.
-- For button labels, use concise and clear text that accurately reflects button behavior. Eg. 'View tasks' can better than only 'View'.
+- For button labels, use concise and clear text that accurately reflects button behavior. For example 'View tasks' can better than only 'View'.
 - Make sure each interaction on the card is unique.
 - Design cards to avoid making users jump around to different experiences. For example, it's ideal if you can keep interactions within the Viva Connections app using Quick view. Next best is to keep user interactions within the dashboard.
 
@@ -104,7 +104,7 @@ Here are the best practices for designing card interactions:
 
 ## Platforms and modes
 
-Dashboard cards are supported on iOS, Android, and Web. However, note that there are slight differences the styling between different platforms – fonts (Segoe UI for desktop, Roboto for Android, SF Display Pro for iOS), colors, sizes, and spacing is slightly tweaked to better suit the respective platform and make the cards look consistent with the overall experience of that platform.
+Dashboard cards are supported on iOS, Android, and Web. However there are slight differences the styling between different platforms – fonts (Segoe UI for desktop, Roboto for Android, SF Display Pro for iOS), colors, sizes, and spacing is slightly tweaked to better suit the respective platform and make the cards look consistent with the overall experience of that platform.
 
 :::image type="content" source="../../../images/viva-design/img_card_platforms.jpg" alt-text="Card container and elements":::
 
@@ -122,11 +122,11 @@ To display your custom app in the dashboard picker, you will need the following:
 
 :::image type="content" source="../../../images/viva-design/img_card_toolbox2.jpg" alt-text="Card container and elements":::
 
-**1. Icon:** Unique visual representation of this app. Your custom icon be a maximum size is 24px by 24px and should preferably in PNG or SVG format. SVG icons scale better across different screen resolutions. It is preferable to use a monochromatic icon, but you can use color icons if you want represent your unique brand with the icons. Either way, make sure the icon has a transparent background, and it looks good both on light and dark theme. ​​​​​​​Learn about SharePoint themes.. The same icon is to be used for the dashboard card (see above).
+**1. Icon:** Unique visual representation of this app. Your custom icon maximum size is 24 px by 24 px and should preferably in PNG or SVG format. SVG icons scale better across different screen resolutions. It is preferable to use a monochromatic icon, but you can use color icons if you want to represent your unique brand with the icons. Either way, make sure the icon has a transparent background, and it looks good both on light and dark theme. ​​​​​​​Learn about SharePoint themes.. The same icon is to be used for the dashboard card (see above).
 
 **1. Title:** Make sure the title of the app is concise and is not truncated. Recommended length is 10-12 characters. The same title should be used for the dashboard card (see above) and the quick view (link quick view page) (if used). If you have multiple apps, it is recommended that each app has a unique title. All titles should be sentence case.
 
-**1. Descriptive text:** A clear, concise description explains the purpose of the card and provides information about how to use it. It should show up in the tooltip on hover (in web). Make sure the text wraps appropriately and is not too wide or too narrow in the tooltip. The optimal line length for is considered to be 50-60 characters per line, including spaces.
+**1. Descriptive text:** A clear, concise description explains the purpose of the card and provides information about how to use it. It should show up in the tooltip on hover (in web). Make sure the text wraps appropriately and is not too wide or too narrow in the tooltip. The optimal line length is considered to be 50-60 characters per line, including spaces.
 
 ### Defining settings for the card
 

docs/spfx/viva/design/designing-quick-view.md

@@ -15,6 +15,9 @@ Here are a few examples of quick views:
 
 :::image type="content" source="../../../images/viva-design/img_quickviews.jpg" alt-text="Card container and elements":::
 
+> [!TIP]
+> Sample adaptive card designs for the quick views are available from [GitHub](https://github.com/pnp/AdaptiveCards-Templates)
+
 The Quick View experience works across different platforms and form-factors based on a single JSON. This introduces certain limitations in terms of available styling and placement on controls. You should not expect identical or pixel perfect comparison of a quick view rendered on web / iOS or Android.
 
 > [!TIP]
@@ -63,7 +66,7 @@ While you can open several children quick views from the parent quick view, we r
 
 ### Quick views vs Web views
 
-Despite being visually similar, they are two very different surfaces for different use cases.
+Despite being visually similar, they are two different surfaces for different use cases.
 
 :::image type="content" source="../../../images/viva-design/img_quickview_webview.jpg" alt-text="Card container and elements":::