♻️ proof & fix numerous msdocs, typos, formating, and gramatical errors

Author: andrewconnell

docs/declarative-customization/column-formatting.md

@@ -7,7 +7,7 @@ ms.localizationpriority: high
 
 # Use column formatting to customize SharePoint
 
-You can use column formatting to customize how fields in SharePoint lists and libraries are displayed. To do this, you construct a JSON object that describes the elements that are displayed when a field is included in a list view, and the styles to be applied to those elements. The column formatting does not change the data in the list item or file; it only changes how it’s displayed to users who browse the list. Anyone who can create and manage views in a list can use column formatting to configure how view fields are displayed.
+You can use column formatting to customize how fields in SharePoint lists and libraries are displayed. To do this, you construct a JSON object that describes the elements that are displayed when a field is included in a list view, and the styles to be applied to those elements. The column formatting doesn't change the data in the list item or file; it only changes how it’s displayed to users who browse the list. Anyone who can create and manage views in a list can use column formatting to configure how view fields are displayed.
 
 For example, a list with the fields Title, Effort, Assigned To, and Status with no customizations applied might look like this:
 
@@ -24,17 +24,17 @@ A list with the appearance of the **Effort**, **Assigned To**, and **Status** fi
 
 Both column formatting and [SharePoint Framework Field Customizer](../spfx/extensions/get-started/building-simple-field-customizer.md) extensions enable you to customize how fields in SharePoint lists are displayed. The Field Customizer is more powerful because you can use it to write any code that you want to control how a field is displayed.
 
-Column formatting is more easily and broadly applied. However, it is less flexible, because it does not allow for custom code; it only allows for certain predefined elements and attributes.
+Column formatting is more easily and broadly applied. However, it's less flexible, because it doesn't allow for custom code; it only allows for certain predefined elements and attributes.
 
 The following table compares column formatting and the Field Customizer.
 
 | Field type        | Column formatting          | Field Customizer  |
 | ------------- |:-------------| :-----|
 | Conditional formatting based on item values and value ranges      | Supported | Supported |
-| Action links       | Support for static hyperlinks that do not launch script      |  Support for any hyperlink, including those that invoke custom script   |
+| Action links       | Support for static hyperlinks that don't launch script      |  Support for any hyperlink, including those that invoke custom script   |
 | Data visualizations | Support for simple visualizations that can be expressed using HTML and CSS      |   Support for arbitrary data visualizations  |
 
-If you can accomplish your scenario by using column formatting, it’s typically quicker and easier to do that than to use a Field Customizer. Anyone who can create and manage views in a list can use column formatting to create and publish customizations. Use a Field Customizer for more advanced scenarios that column formatting does not support.
+If you can accomplish your scenario by using column formatting, it’s typically quicker and easier to do that than to use a Field Customizer. Anyone who can create and manage views in a list can use column formatting to create and publish customizations. Use a Field Customizer for more advanced scenarios that column formatting doesn't support.
 
 ## Get started with column formatting
 
@@ -174,7 +174,7 @@ The following image shows a field with conditional date formatting applied:
 
 ![Status field with the Overdue text colored red](../images/sp-columnformatting-overdue.png)
 
-This example colors the current field red when the value inside an item's DueDate is before the current date/time. Unlike some of the previous examples, this example applies formatting to one field by looking at the value inside another field. Note that DueDate is referenced using the `[$FieldName]` syntax. FieldName is assumed to be the internal name of the field. This example also takes advantage of a special value that can be used in date/time fields - `@now`, which resolves to the current date/time, evaluated when the user loads the list view.
+This example colors the current field red when the value inside an item's DueDate is before the current date/time. Unlike some of the previous examples, this example applies formatting to one field by looking at the value inside another field. Note that `DueDate` is referenced using the `[$FieldName]` syntax. FieldName is assumed to be the internal name of the field. This example also takes advantage of a special value that can be used in date/time fields - `@now`, which resolves to the current date/time, evaluated when the user loads the list view.
 
 > [!NOTE]
 > If you have spaces in the field name, those are defined as `_x0020_`. For example, a field named "Due Date" should be referenced as `$Due_x0020_Date`.
@@ -555,7 +555,7 @@ The following image shows an example of constructing a simple sentence from the
 
 ![Screenshot of a field reads "North America, APAC, and Europe"](../images/sp-columnformatting-multi-value-1.png)
 
-This examples uses operator `loopIndex` and `length` to identify the last member of the field, and attribute `forEach` to duplicate HTML elements.
+This example uses operator `loopIndex` and `length` to identify the last member of the field, and attribute `forEach` to duplicate HTML elements.
 
 ```json
 {
@@ -589,11 +589,12 @@ This examples uses operator `loopIndex` and `length` to identify the last member
 ```
 
 ### Complex HTML elements formatting
+
 The following image shows an example of building a list of users with pictures, email addresses and a simple counter for the number of members at the top.
 
 ![List with name "Owners" and 3 rows where each user in the field has a profile picture, name and email displayed, and a small gray counter of owners at top left corner that has a different color when it says 0.](../images/sp-columnformatting-multi-value-2.png)
 
-This examples uses operator `loopIndex` to control the margins all rows but the first one, and attribute `forEach` to build the list of members.
+This example uses operator `loopIndex` to control the margins all rows but the first one, and attribute `forEach` to build the list of members.
 
 ```json
 {
@@ -746,7 +747,7 @@ You can use predefined icons from Fluent UI. For details, see the [Fluent UI web
 
 ## Creating custom JSON
 
-Creating custom column formatting JSON from scratch is simple if user understands the schema, Monaco Editor is integrated in the formatting pane with pre-filled JSON column schema reference to assist in creation of column formatting, Monaco editor has validation and autocomplete to help in crafting right JSON. User can start adding JSON after the first line that defines the schema ___location.
+Creating custom column formatting JSON from scratch is simple if user understands the schema, Monaco Editor is integrated in the formatting pane with pre-filled JSON column schema reference to help creation of column formatting, Monaco editor has validation and autocomplete to help in crafting right JSON. User can start adding JSON after the first line that defines the schema ___location.
 
 > [!TIP]
 > At any point, select **Ctrl**+**Space** for property/value suggestions.

docs/declarative-customization/customize-default-site-design.md

@@ -20,7 +20,6 @@ To customize a default site template, apply a new template script using PowerShe
 | WebTemplate    | 68 | Communication site template |
 | WebTemplate    | 69 | Channel site template |
 
-
 The following example shows how to use the **IsDefault** switch to apply the Contoso company theme to the default site templates. The site script referenced by ID contains the JSON script to apply the correct theme.
 
 ```powershell
@@ -32,8 +31,6 @@ C:\> Add-SPOSiteDesign `
   -IsDefault
 ```
 
-<br/>
-
 ```javascript
 RestRequest("/_api/Microsoft.SharePoint.Utilities.WebTemplateExtensions.SiteScriptUtility.CreateSiteDesign", {info:{Title:"Contoso company theme", Description:"Applies standard company theme to site", SiteScriptIds:["89516c6d-9f4d-4a57-ae79-36b0c95a817b"],  WebTemplate:"68", IsDefault: true}});
 ```
@@ -42,7 +39,6 @@ RestRequest("/_api/Microsoft.SharePoint.Utilities.WebTemplateExtensions.SiteScri
 
 The default site template for a communication site is the **Topic** template. The default for a team site is the **Team collaboration** template. When you apply a new default site template, it updates the Microsoft-provided default templates.
 
-
 ## Restore the default site templates
 
 To restore a site template to the defaults, remove the site template script that you applied. In the previous example, if the site template created had the ID `db752673-18fd-44db-865a-aa3e0b28698e`, you would remove it as shown in the following example.
@@ -51,8 +47,6 @@ To restore a site template to the defaults, remove the site template script that
 C:\> Remove-SPOSiteDesign db752673-18fd-44db-865a-aa3e0b28698e
 ```
 
-<br/>
-
 ```javascript
 RestRequest("/_api/Microsoft.SharePoint.Utilities.WebTemplateExtensions.SiteScriptUtility.DeleteSiteDesign", {id:"db752673-18fd-44db-865a-aa3e0b28698e"});
 ```

docs/declarative-customization/formatting-advanced.md

@@ -14,9 +14,9 @@ The following screenshot shows a list with a Flow button added to the Action col
 
 ![screenshot of the sample](../images/sp-columnformatting-flow.png)
 
-You can use column formatting to create buttons that, when selected, run Flows on the corresponding list item.  For flows that are [solution-aware](/power-automate/overview-solution-flows), the Flow Launch Panel will be displayed after choosing the button and you must select Run Flow to start the flow. For flows that are not solution-aware, The Flow Launch Panel will be displayed after choosing the button and the Flow will just run.
+You can use column formatting to create buttons that, when selected, run Flows on the corresponding list item. For flows that are [solution-aware](/power-automate/overview-solution-flows), the Flow Launch Panel will be displayed after choosing the button and you must select Run Flow to start the flow. For flows that aren't solution-aware, The Flow Launch Panel will be displayed after choosing the button and the Flow will just run.
 
-To use the sample below, you must substitute the ID of the Flow you want to run.  This ID is contained within the `actionParams` property of the `customRowAction` attribute inside the `button` element.
+To use the sample below, you must substitute the ID of the Flow you want to run. This ID is contained within the `actionParams` property of the `customRowAction` attribute inside the `button` element.
 
 To obtain the ID of a flow that is solution-aware:
 
@@ -28,7 +28,7 @@ To obtain the ID of a flow that is solution-aware:
 1. Select Export > Get flow identifier.
 1. Copy the ID.
 
-To obtain the ID of a flow that is not solution-aware:
+To obtain the ID of a flow that isn't solution-aware:
 
 1. Select **Flow > See your flows** in the SharePoint list where the Flow is configured.
 1. Select the Flow you want to run.
@@ -82,7 +82,7 @@ On hover - Metadata on the column "Status" is made available in column formattin
 
 ![Preview Image 2](../images/HoverImage-2.png)
 
-You can use formatting to define custom call out that can be commissioned basis user defined actions like click or hover.
+You can use formatting to define custom call out that can be commissioned basis user-defined actions like click or hover.
 
 This example uses `customCardProps`, `openOnEvent`, `directionalHint` and `isBeakVisible`:
 
@@ -271,23 +271,23 @@ A special json property `inlineEditField` is used with value as the field intern
 
 ![Inline Editing using inlineEditField property](../images/sp-columnformatting-inline-editing.gif)
 
-This allows the users to edit items in-place, within the view, without navigating away to grid based editing or to a item edit form.
+This allows the users to edit items in-place, within the view, without navigating away to grid-based editing or to an item edit form.
 
 ### Supported Field Types
 
 List of supported field types for inline editing:
 
 - Single line text
-- Multi line text (without RTF)
+- Multiline text (without RTF)
 - Number
 - DateTime
 - Choice and MultiChoice
-- User and Multi user
+- User and Multiuser
 - Lookup
 
 ### Hover Borders and Customizations
 
-The inline editing adds a hover border on the elements to indicate these elements have an associated action. The default border is `neutralSecondary` , and on click, the editor appears with a `themePrimary` border. These border colors can be overriden via setting style on the same element with `inlineEditField` by using some special attributes - `--inline-editor-border-width`, `--inline-editor-border-style`, `--inline-editor-border-radius`, and `--inline-editor-border-color`.
+The inline editing adds a hover border on the elements to indicate these elements have an associated action. The default border is `neutralSecondary`, and on click, the editor appears with a `themePrimary` border. These border colors can be overridden via setting style on the same element with `inlineEditField` by using some special attributes - `--inline-editor-border-width`, `--inline-editor-border-style`, `--inline-editor-border-radius`, and `--inline-editor-border-color`.
 
 ```json
 {
@@ -305,7 +305,7 @@ The inline editing adds a hover border on the elements to indicate these element
 
 ## Set multiple field values of an Item using customRowAction
 
-With the new `setValue` and `customRowAction` properties, formatters can render action buttons which modify the item internally without opening editors or forms. `setValue` also allows setting multiple field values of the item at once.
+With the new `setValue` and `customRowAction` properties, formatters can render action buttons that modify the item internally without opening editors or forms. `setValue` also allows setting multiple field values of the item at once.
 
 The below JSON will set value of `FieldInternalName_1`, `FieldInternalName_2`, and `FieldInternalName_3`with the values provided:
 
@@ -327,38 +327,42 @@ The below JSON will set value of `FieldInternalName_1`, `FieldInternalName_2`, a
 ### Supported Field Types
 
 - Single line text
-- Multi line text (without RTF)
+- Multiline text (without RTF)
 - Number
 - DateTime
 - Choice and MultiChoice
-- User and Multi user
+- User and Multiuser
 
 ### Value Field values in `actionInput`:
 
 - Text values:
   - a valid string like `"Choice 1"`
-  - value from other columns : `[$ColumnName]`
+  - value from other columns: `[$ColumnName]`
   - an [expression](./formatting-syntax-reference.md#expressions) such as:
 
-    `"if([$column]> 10, "Choice A", "Choice B")"`
+      ```
+      "if([$column]> 10, "Choice A", "Choice B")"
+      ```
 
     or
 
-    `{operator: "+", operands" : ["Choice", "A"]}`
+      ```
+      {operator: "+", operands" : ["Choice", "A"]}
+      ```
 
 - Number:
   - a valid number
-  - value from other columns : `[$ColumnName]`
+  - value from other columns: `[$ColumnName]`
   - an [expression](./formatting-syntax-reference.md#expressions)
 - Date values:
   - a date string
   - `@now` token
-  - [expressions](./formatting-syntax-reference.md#expressions) which return a date using builtin date functions
-  - `addDays` and `addMinutes`, two new functions to support [expressions](./formatting-syntax-reference.md#expressions) like 7 days from today
+  - [expressions](./formatting-syntax-reference.md#expressions) that return a date using built-in date functions
+  - `addDays` and `addMinutes`, two new functions to support [expressions](./formatting-syntax-reference.md#expressions) like seven days from today
   - an empty string `""` clears the field value
 - Multi-Choice and Multi-Person:
   - Multi value fields are special, as they need an array value to save multiple values.
-  - `appendTo`, `removeFrom`, and `replace`, three functions which can operate on multivalue fields.
+  - `appendTo`, `removeFrom`, and `replace`, three functions that can operate on multivalue fields.
     - `appendTo([$MultiChoiceField], 'MyValue')`
     - `removeFrom([$MultiUserField], @me)`: removes all occurrences that match the second parameter
     - `replace([$MultiChoiceField], 'Choice 1', 'Choice 3')`: replaces all occurrences of second parameter with third.