🐞 improve readability (acrolyix score)

Author: andrewconnell

docs/design/authoring-pages.md

@@ -7,9 +7,7 @@ ms.localizationpriority: high
 
 # Authoring pages in a SharePoint site
 
-Authoring pages in SharePoint is a simple process, but it does require some familiarity with the SharePoint environment, as well as an understanding of what and who you are designing the page for. A few basic principles, such as remembering to "Start simple" and "Build on what's working," are valuable things to consider as you start authoring. It's also a good idea to consistently remind yourself of your audience and the goals that you are trying to help them achieve.
-
-<!-- Do we have content about the design principles that we can link to here? -->
+Authoring pages in SharePoint is a simple process, but it does require some familiarity with the SharePoint environment, and an understanding of what and who you are designing the page for. A few basic principles, such as remembering to "Start simple" and "Build on what's working," are valuable things to consider as you start authoring. It's also a good idea to consistently remind yourself of your audience and the goals that you're trying to help them achieve.
 
 The SharePoint page authoring experience has two modes:
 
@@ -72,7 +70,7 @@ After the page is published, all editing UI is disabled for the viewer or reader
 
 ## Mobile view
 
-All SharePoint pages are [responsive](grid-and-responsive-design.md) to allow the content of the page to be viewed on mobile devices. While designing a web part, it is important to understand how the new SharePoint site pages render across different devices.
+All SharePoint pages are [responsive](grid-and-responsive-design.md) to allow the content of the page to be viewed on mobile devices. While designing a web part, it's important to understand how the new SharePoint site pages render across different devices.
 
 ![Mobile view of site](../images/design-authoring-mobile.png)
 

docs/design/reactive-and-nonreactive-web-parts.md

@@ -17,7 +17,7 @@ Reactive web parts are fully client-side web parts. This means that each compone
 
 ## Nonreactive web parts
 
-Nonreactive web parts are not fully client-side; generally, one or more properties need to make a call to set/pull or store data on a server. For nonreactive web parts, you should enable the **Apply** button at the bottom of the property pane.
+Nonreactive web parts aren't fully client-side; generally, one or more properties need to make a call to set/pull or store data on a server. For nonreactive web parts, you should enable the **Apply** button at the bottom of the property pane.
 
 You can also customize the **Apply** button to be a more specific action.
 

docs/design/ui-text-for-web-parts.md

@@ -7,7 +7,7 @@ ms.localizationpriority: medium
 
 # UI text guidelines for SharePoint web parts
 
-One aspect of creating effective web parts in SharePoint is to use simple, understandable, and concise UI text. By keeping your message clear and easy to understand, you ensure that customers move through your experiences quickly and can identify the content they are looking for. This article provides guidance for writing UI text for key areas within SharePoint web parts.
+One aspect of creating effective web parts in SharePoint is to use simple, understandable, and concise UI text. By keeping your message clear and easy to understand, you ensure that customers move through your experiences quickly and can identify the content they're looking for. This article provides guidance for writing UI text for key areas within SharePoint web parts.
 
 ## Capitalization
 
@@ -27,12 +27,12 @@ Always capitalize:
 
 Follow the basic rules of punctuation to avoid grammatical errors in your experience. The following table provides guidance and reminders about what punctuation to use when, and why.
 
-|Punctuation  |Guidance                                        |Example          |
-|-------------|------------------------------------------------|-----------------|
-|Colons (:)  | Use colons if you are introducing a list in the web part description.<br/>Don't use colons in UI labels.| Choose one of the following: Cats, Dogs, Quokkas    |
-|Commas (,)  | Use serial commas (including before the word "and").  |I like cats, birds, and dogs. |
-|Ellipses (…)| Use ellipses to show truncation and for progress indicator strings.<br/>Don't use ellipses to indicate that the user must make further choices.|Truncation: Last modified by John Armstr…<br/>Progress indicator: Uploading… |
-|Periods (.) | Use periods as you normally would for descriptions.<br/>Don't use periods in titles, headings, or labels. Don't use periods for radio button options or check boxes. | Select the content that you want to highlight and how you want it displayed. Use a filter to narrow your selection. |
+| Punctuation  |                                                                               Guidance                                                                               |                                                       Example                                                       |
+| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
+| Colons (:)   | Use colons if you're introducing a list in the web part description.<br/>Don't use colons in UI labels.                                                             | Choose one of the following: Cats, Dogs, Quokkas                                                                    |
+| Commas (,)   | Use serial commas (including before the word "and").                                                                                                                 | I like cats, birds, and dogs.                                                                                       |
+| Ellipses (…) | Use ellipses to show truncation and for progress indicator strings.<br/>Don't use ellipses to indicate that the user must make further choices.                      | Truncation: Last modified by John Armstr…<br/>Progress indicator: Uploading…                                        |
+| Periods (.)  | Use periods as you normally would for descriptions.<br/>Don't use periods in titles, headings, or labels. Don't use periods for radio button options or check boxes. | Select the content that you want to highlight and how you want it displayed. Use a filter to narrow your selection. |
 
 ## Voice and tone
 
@@ -41,11 +41,11 @@ Crafting the right tone in your product communication is essential to building a
 ### Do
 
 - Use a casual, conversational tone in the UI.
-- Use contractions. For example, use "can't" instead of "cannot".
+- Use contractions. For example, use "can't" instead of "can't".
 - Read your UI text out loud to test the tone. Does it sound like everyday language?
 - Use simple words.
 - Remove technical details if they're not relevant to the user experience.
-- Use "Please" only if you are inconveniencing the user. Avoid overuse.
+- Use "Please" only if you're inconveniencing the user. Avoid overuse.
 - Use "Sorry" only in error messages in SharePoint that result in serious problems for the customer.
 
 ### Don't

docs/solution-guidance/Personalize-search-results-sample-app-for-SharePoint.md

@@ -64,7 +64,7 @@ In default.aspx.cs, choosing **Perform Personalized Search** calls the **btnPers
 
 - Uses **PeopleManager** to get all user profile properties for the user running this add-in.
 
-- Retrieves and checks the value of the **AboutMe** user profile property. If the value of the **AboutMe** property is **AppTest**, the search query retrieves all sites by using the query string  `contentclass:"STS_Site"`. If the value of the **AboutMe** property is not **AppTest**, the team site filter is appended to the query string (`WebTemplate=STS`), and the search query retrieves team sites only.
+- Retrieves and checks the value of the **AboutMe** user profile property. If the value of the **AboutMe** property is **AppTest**, the search query retrieves all sites by using the query string  `contentclass:"STS_Site"`. If the value of the **AboutMe** property isn't **AppTest**, the team site filter is appended to the query string (`WebTemplate=STS`), and the search query retrieves team sites only.
 
 - Calls the **ProcessQuery** method to retrieve the search results based on the supplied query string. **ProcessQuery** also demonstrates how to specify a list of properties to return with the search results.
 

docs/solution-guidance/Read-or-update-user-profile-properties-sample-app-for-SharePoint.md

@@ -153,7 +153,7 @@ Scenario 3 shows how to update a multivalued user profile property. The followin
 To add new skills to the **SPS-Skills** user profile property from this add-in:
 
 1. Enter HTML5, and then choose **Add Skill**.
-1. Enter ASP.Net, and then choose **Add Skill**.
+1. Enter ASP.NET, and then choose **Add Skill**.
 1. Choose **Run scenario 3**.
 1. Verify that **Skills current value** shows the new list of skills for the user.
 1. Verify that the **SPS-Skills** user profile property for the user now shows the new list of skills.