address acrolyix findings for readability

Author: andrewconnell

docs/apis/webhooks/webhooks-reference-implementation.md

@@ -157,7 +157,7 @@ Create a web job that on a weekly basis reads all the subscription IDs from the
 > [!NOTE]
 > This web job is not part of this reference implementation.
 
-The actual renewal of a SharePoint list webhook can be done by using a [`PATCH /_api/web/lists('list-id')/subscriptions(‘subscriptionID’)`](./lists/update-subscription.md) REST call.
+The actual renewal of a SharePoint list webhook can be done by using a `[PATCH /_api/web/lists('list-id')/subscriptions(‘subscriptionID’)](./lists/update-subscription.md)` REST call.
 
 In the reference implementation, updating of webhooks is implemented in the [WebHookManager](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List/SharePoint.WebHooks.Common/WebHookManager.cs) class of the **SharePoint.WebHooks.Common** project.
 

docs/declarative-customization/site-design-trigger-flow-tutorial.md

@@ -105,7 +105,7 @@ In order to capture the site creation event and create the corresponding list it
     Get-SPOSiteDesign
     ```
 
-To create a site design, you first need to create a site script. A site design is a container that refers to one or more site scripts.
+    To create a site design, you first need to create a site script. A site design is a container that refers to one or more site scripts.
 
 1. Copy the following JSON code to your clipboard and modify it. Set the **url** property to the value that you copied when you created the flow. The URL looks similar to the following:
 

docs/declarative-customization/site-theming/sharepoint-site-theming-overview.md

@@ -91,7 +91,9 @@ To do this, you must use a Windows PowerShell script with a CSOM (client-side ob
 
 1. Verify that the following is returned:
 
-    `ClientSideThemingOptOut - 5138468e-3d76-4f72-9de4-e029f1245a7b`
+    ```powershell
+    ClientSideThemingOptOut - 5138468e-3d76-4f72-9de4-e029f1245a7b
+    ```
 
 For more information about Windows PowerShell, see [PowerShell](/powershell/scripting/overview).
 

docs/spfx/release-1.16.md

@@ -65,11 +65,9 @@ if (!!this.context.sdks.microsoftTeams) {
 }
 ```
 
-See more details around these options from following article
+For more information, see: [Extend Outlook and Office with the SharePoint Framework](office/overview.md).
 
-* [Extend Outlook and Office with the SharePoint Framework](office/overview.md)
-
-> [!Important]
+> [!IMPORTANT]
 > Using the Teams SDK v2 within the SharePoint Framework solutions is generally available starting from the 1.16 version, enabling usage of the Teams SDK v2 immediately.
 > Support for publishing Teams apps (including SPFx solutions) within the Outlook and in Office.com (Microsoft 365 app) is however still in preview and is planned to be generally available for both mobile and desktop experiences within the first half of calendar year 2023.
 
@@ -81,7 +79,7 @@ This version supports the teams-js v2. `this.context.sdks.microsoftTeams.teamsJs
 > teams-js v2 is backward compatible with teams-js v1. We will continue to support v1 for existing solutions.
 
 > [!TIP]
-> Teams JavaScript SDK v2 enables new scenarios for developers. See following announcement for additional details on the Teams JS SDK v2 capabilities - [Microsoft Teams JS SDK v2 is now generally available](https://devblogs.microsoft.com/microsoft365dev/microsoft-teams-js-sdk-v2-is-now-generally-available/)
+> Teams JavaScript SDK v2 enables new scenarios for developers. For more information on the Teams JS SDK v2 capabilities, see [Microsoft Teams JS SDK v2 is now generally available](https://devblogs.microsoft.com/microsoft365dev/microsoft-teams-js-sdk-v2-is-now-generally-available/).
 
 ### teams-js v2 typings support
 
@@ -96,7 +94,7 @@ SPFx now supports React 17 by default (scaffolded as part of the solution).
 
 ### Ability to set dataVersion in web part's manifest
 
-Set a data version for this preconfigured entry. This is optional and can be used in cases where the SPPKG is updated independently from code (e.g. hosted on a CDN). Web Parts can read this value for backwards compatibility with out of date default properties.
+Set a data version for this preconfigured entry. This is optional and can be used in cases where the SPPKG is updated independently from code (for example, hosted on a CDN). Web Parts can read this value for backwards compatibility with out of date default properties.
 
 ### General availability of Search Query extensions
 
@@ -170,7 +168,7 @@ Node.js v12 & v14 are no longer supported. SPFx v1.16 requires Node.js v16.
 
 ## Preview Features and Capabilities
 
-Following features are still in preview status as part of the 1.16 release and should not be used in production. We are looking into releasing them officially as part of the upcoming 1.17 release.
+Following features are still in preview status as part of the 1.16 release and shouldn't be used in production. We're looking into releasing them officially as part of the upcoming 1.17 release.
 
 ### Web part Top Actions
 
@@ -202,10 +200,7 @@ export interface ITopActions {
 > Although type of Top Action Configuration is `IPropertyPaneField<any>` we currently support buttons and choice groups only.
 > It means you can use either `PropertyPaneChoiceGroup(...)` and `PropertyPaneButton(...)`, or specify your own configurations that will resolve to `IPropertyPaneField<IPropertyPaneChoiceGroupProps>` and `IPropertyPaneField<IPropertyPaneButtonProps>`
 
-See more details on the code level guidance from the following article
-
-* [Adding support for Top Actions](web-parts/guidance/getting-started-with-top-actions.md)
-
+For more information on Top Actions, see [Adding support for Top Actions](web-parts/guidance/getting-started-with-top-actions.md).
 
 ## Deprecations
 
@@ -219,18 +214,18 @@ Here's a list of specific issues fixed around SharePoint Framework since the pre
 ### August-November Timeframe
 
 - [#8146](https://github.com/SharePoint/sp-dev-docs/issues/8146) - SPFX Application Customizer breaks Anonymous Links for PDF Files
-- [#8266](https://github.com/SharePoint/sp-dev-docs/issues/8266) - SPFx 1.15 - Form Customiser does not work in View History
-- [#8272](https://github.com/SharePoint/sp-dev-docs/issues/8272) - SPFx 1.15 - Getting error when use form customier to view existing list item in Classic mode
+- [#8266](https://github.com/SharePoint/sp-dev-docs/issues/8266) - SPFx 1.15 - Form Customizer doesn't work in View History
+- [#8272](https://github.com/SharePoint/sp-dev-docs/issues/8272) - SPFx 1.15 - Getting error when use form customizer to view existing list item in Classic mode
 - [#8279](https://github.com/SharePoint/sp-dev-docs/issues/8279) - New icons in production environments
-- [#8301](https://github.com/SharePoint/sp-dev-docs/issues/8301) - Error When Revisiting Custom Teams ?app=portals App
+- [#8301](https://github.com/SharePoint/sp-dev-docs/issues/8301) - Error When Revisiting Custom Teams `?app=portals` App
 - [#8372](https://github.com/SharePoint/sp-dev-docs/issues/8372) - Applying permissions on Form Customizer
 - [#8379](https://github.com/SharePoint/sp-dev-docs/issues/8379) - SPFx `ListViewCommandSet` - `this.context.listView.selectedRows` is wrong in grouped lists
 - [#8467](https://github.com/SharePoint/sp-dev-docs/issues/8467) - Buttons (`onClick` events) in `BaseDialog` no longer working - ListView Command Set
-- [#8483](https://github.com/SharePoint/sp-dev-docs/issues/8483) - Multi-paged Webpart Property Panes - Pagination doesn't work as expected, stopping users from accessing pages
+- [#8483](https://github.com/SharePoint/sp-dev-docs/issues/8483) - Multi-paged web part property panes - Pagination doesn't work as expected, stopping users from accessing pages
 - [#8484](https://github.com/SharePoint/sp-dev-docs/issues/8484) - Web part property pane breaks when using React and office-ui-fabric-react in property pane field label
-- [#8482](https://github.com/SharePoint/sp-dev-docs/issues/8482) - React version mismatch causing SPFX list extensions to fail in O365
-- [#8487](https://github.com/SharePoint/sp-dev-docs/issues/8487) - SharePoint React 17 Upgrade causing "Invalid Hook call" error in SPFx Webpart
-- [#7324](https://github.com/SharePoint/sp-dev-docs/issues/7324) - SPFx license does not permit commercial use
+- [#8482](https://github.com/SharePoint/sp-dev-docs/issues/8482) - React version mismatch causing SPFx list extensions to fail in O365
+- [#8487](https://github.com/SharePoint/sp-dev-docs/issues/8487) - SharePoint React 17 Upgrade causing "Invalid Hook call" error in SPFx web part
+- [#7324](https://github.com/SharePoint/sp-dev-docs/issues/7324) - SPFx license doesn't permit commercial use
 - [#8331](https://github.com/SharePoint/sp-dev-docs/issues/8331) - Mechanism to version the preconfiguredEntries in the manifest
 - [#8510](https://github.com/SharePoint/sp-dev-docs/issues/8510) - SPFx sudden Minified React error #321
 - [#8496](https://github.com/SharePoint/sp-dev-docs/issues/8496) - React version mismatch causes property pane not displaying