Updates to Power Apps custom form tutorial (SharePoint#5941)

* Add "Customize a form for a SharePoint list"

Add "Customize a form for a SharePoint list".

Fix typo in SharePoint flow doc.

* Update subsection titles

* Update create-your-first-custom-form.md

Global notes:
1. Stay in present tense, not future.
2. For reference: Each numbered step always has to have an action associated with it. Otherwise, it is just a statement that is standalone or associated as a combined sentence with an action step. (for example, 1. Select Go. The Go pane appears.) Second sentence (non-action is associated with action step 1.)
3. Use 'select' v 'click' for all screen actions. 'Click' is meant for the exclusive territory of right-clicking and mouse clicks. We don't use 'right-click on.' One simply 'right-clicks' or 'selects.'
4. Always precede ___location of action, then action. For example, we'd write, "Alternatively, in the Tree View, right-click **Title_DataCard1**, and select **Unlock**", not "Alternatively, right-click **Title_DataCard1** in the Tree View, and select **Unlock**."
5. All references to UI are bolded (for example **Properties** pane, **Advanced** pane).
6. Is Tree View a proper noun phrase or generic? I've gone with the latter.
7. A plethora of commas because every discreet action in a sentence of multiple actions needs a comma following it.
8. Buttons don't need the button reference, tabs do. For example, Select **Unlock** v Select the **Unlock** button.
9. Avoid use of exclamation points. Overkill and has lost its meaning in this social media era where everything is an exclamation point or three.
Line 10: "...form-filling experience..."? Awkward. Let's remove it altogether. It's generally assumed that forms need to be filled out.
Line 42: Replaced 'look and feel' with 'appearance.' Let's avoid euphemisms in the writing as they don't localize well.
Line 69: Office 365 or Microsoft 365? Change back if accurate.
Line 73: Are we talking read-only or view-only? Let's be consistent throughout this section.

* Add minor clarification

* Formatting changes

* Update lists & doclib setup URL

* Add requested changes

- Use numbers in bullets
- Remove locales in links
- Mark formulas as in-line code snippets

* Fix numbering

* Add note about deprecated snippet preview

* Revert bizapps change

* Updates to make custom form refresh upon toggling owner

* Fix typo

* Edit tweaks for writing syntax

Co-authored-by: Steven Jia <[email protected]>
Co-authored-by: Jack Wight <[email protected]>

Author: 3 people

docs/business-apps/power-apps/get-started/create-your-first-custom-form.md

@@ -60,10 +60,14 @@ Before starting, make sure your SharePoint site is set up with the [required lis
 
     ![Set image border radius](../../../images/gs01-set-image-border-radius.png)
 
-1. To change the image of **Image1** from the sample image to the owner's profile photo, make sure you select **Image1**. In the formula bar, change the property to **Image**, and enter `SharePointIntegration.Selected.Owner.Picture` as the formula. The user photo from the owner's Microsoft 365 user profile appears in **Image1**.
+1. To change the image of **Image1** from the sample image to the project owner's profile photo, you can use the Office 365 Users connector to retrieve the photo by the owner's email. First, [connect your custom form to the Office 365 Users connector](https://docs.microsoft.com/powerapps/maker/canvas-apps/connections/connection-office365-users).
+
+1. To retrieve the project owner's profile photo by email, in the formula bar, change the property to **Image**, and enter `Office365Users.UserPhoto(DataCardValue5.Selected.Email)` as the formula. The user photo from the owner's Office 365 user profile appears in **Image1**. 
 
     ![Set image picture](../../../images/gs01-set-image-picture.png)
 
+    When you change the project owner, **Image1** will update to the user photo of the new owner.
+
 ### Set a field to be view-only
 
 To make the **Title** field view-only, follow these steps.
@@ -106,11 +110,11 @@ To hide the **Attachments** field if the project owner is Nestor Wilke, follow t
 
     ![Select visible field](../../../images/gs01-attachments-property-visible.png)
 
-1. In the formula bar, enter the following formula: `If(SharePointIntegration.Selected.Owner.DisplayName = "Nestor Wilke", false)`
+1. In the formula bar, enter the following formula: `If(SharePointIntegration.Selected.Owner.DisplayName = "Nestor Wilke", false, true)`
 
     ![View-only title](../../../images/gs01-attachments-conditional-visibility.png)
 
-    The **Attachments** data card is now hidden if the project owner is Nestor Wilke.
+    If the project owner is Nestor Wilke, then the **Attachments** data card is hidden. Otherwise, it is visible.
 
     You can write the same conditional logic in multiple ways. For more info, see [Operators and Identifiers in Power Apps](https://docs.microsoft.com/powerapps/maker/canvas-apps/functions/operators).
 
@@ -136,4 +140,4 @@ To hide the **Attachments** field if the project owner is Nestor Wilke, follow t
 
 Congratulations on creating your custom form.
 
-In the next topic, we will build on top of this custom form so that the user profile photo and the visibility of the **Attachments** data card automatically update when the owner is changed.
+In the next topic, we will create a standalone app using data from a SharePoint list.