Update README.md

Author: Dev-Mom

README.md

@@ -14,8 +14,10 @@ A proof-of-concept C# console application for retrieving legacy 2010 & 2013 cust
 3. Declarative `*.xoml` and `*.xoml.wfconfig.xml` files do not appear to exist for workflows created from [OOB SharePoint 2010 or 2013 workflow templates](https://support.microsoft.com/en-us/office/overview-of-workflows-included-with-sharepoint-d74fcceb-3a64-40fb-9904-cc33ca49da56). *(If you can find them - I'll buy you a beverage of your choice!)*
 ### Notes about creating Power Automate flows:
 1. This project leverages the [Power Automate Management Web API](https://docs.microsoft.com/en-us/power-automate/web-api) to create a new Power Automate flow. 
-2. Per Microsoft's [documentation](https://docs.microsoft.com/en-us/power-automate/web-api), flows shown in the *My Flows* tab are not supported by these APIs. Instead you will find flows created via the API in your *[Solutions](https://flow.microsoft.com/en-us/blog/solutions-in-microsoft-flow/) > Default Solution* tab. *(I have opened a [GitHub issue](https://github.com/MicrosoftDocs/power-automate-docs/issues/323) inquiring about how to programmatically create Power Automate flows within solutions other than Default.)* 
-3. The meat and potatoes of the flow payload is in the `clientdata` property. To help determine appropriate content for this section, I recommend manually creating the desired Power Automate flow using the UI. Then, you can [leverage the API](https://docs.microsoft.com/en-us/power-automate/web-api#list-flows) to get the expected `clientdata` content for your manual workflow and copy/paste it into your payload. *(Also a great strategy for bulk-creating Power Automate flows in an environment!)*
+2. Per Microsoft's [documentation](https://docs.microsoft.com/en-us/power-automate/web-api), flows shown in the *My Flows* tab are not supported by these APIs. Instead you will find flows created via the API in your *[Solutions](https://flow.microsoft.com/en-us/blog/solutions-in-microsoft-flow/) > Default Solution* tab. 
+*(I have opened a [GitHub issue](https://github.com/MicrosoftDocs/power-automate-docs/issues/323) inquiring about how to programmatically create Power Automate flows within solutions other than Default.)* 
+3. The meat and potatoes of the flow payload is in the `clientdata` property. To help determine appropriate content for this section, I recommend manually creating the desired Power Automate flow using the UI. Then, you can [leverage the API](https://docs.microsoft.com/en-us/power-automate/web-api#list-flows) to get the expected `clientdata` content for your manual workflow and copy/paste it into your payload. 
+*(Also a great strategy for programmatically bulk-creating Power Automate flows in an environment!)*
 4. Once you successfully create a new Power Automate flow via the API, you will need to turn it on. Then, do a Ctrl+F5 to confirm your connections appear as expected. 
 ![Power Automate Screenshot](/SS1.png?raw=true)