docs: fix three 'Microsoft' typos across playbook READMEs

[MukundaKatta]

Fixes #14109. Three 'Microsft'/'Micrsoft' typos in README files:

- Playbooks/Sync-Sentinel-Incident-Comments-To-M365Defender/readme.md
- Microsft Threat Protection
+ Microsoft Threat Protection

- Playbooks/Update-VIPUsers-Watchlist-from-AzureAD-Group/readme.md
- Microsft Graph API permissions
+ Microsoft Graph API permissions

- Solutions/Recorded Future/Playbooks/readme.md
- Micrsoft guide
+ Microsoft guide

Docs-only, three single-character fixes.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Fixes three misspellings of “Microsoft” in playbook README documentation (per #14109), ensuring product names and guidance read correctly.

Changes:

• Corrects “Micrsoft/Microsft” → “Microsoft” in three README files.
• Updates the affected sentences where the typos appeared.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
Solutions/Recorded Future/Playbooks/readme.md	Fixes “Micrsoft” typo in a link description.
Playbooks/Update-VIPUsers-Watchlist-from-AzureAD-Group/readme.md	Fixes “Microsft” typo in Graph permissions instructions.
Playbooks/Sync-Sentinel-Incident-Comments-To-M365Defender/readme.md	Fixes “Microsft” typo in API selection guidance.

[Copilot]

The PR description says this is a ‘single-character fix’, but this line change also alters leading whitespace/formatting (the previous line began with indentation + a |). If that | was intentional (e.g., part of a table layout), this could change the rendered markdown. Please either restore the original formatting (keeping only the typo fix) or confirm via markdown preview that rendering is unchanged.

[Copilot]

There’s a typo in the updated line: ‘mu organization’ should be ‘my organization’.

Suggested change

	From the options that open on the right, select APIs mu organization uses and search for and then click Microsoft Threat Protection.
	From the options that open on the right, select APIs my organization uses and search for and then click Microsoft Threat Protection.

[Copilot]

This link uses the legacy docs.microsoft.com domain. Microsoft’s canonical documentation host is learn.microsoft.com (the old domain typically redirects). Consider updating the URL to the equivalent learn.microsoft.com link to avoid future link rot and keep docs consistent.

Suggested change

	To assign Microsoft Graph API permissions, first you will have to connect to Azure AD PowerShell module - https://docs.microsoft.com/powershell/module/azuread/?view=azureadps-2.0#connect-to-your-directory
	To assign Microsoft Graph API permissions, first you will have to connect to Azure AD PowerShell module - https://learn.microsoft.com/powershell/module/azuread/?view=azureadps-2.0#connect-to-your-directory

[v-maheshbh]

Hi @MukundaKatta
Kindly review the above-mentioned suggestions and proceed accordingly.

Thanks!

[MukundaKatta]

Thanks @v-maheshbh, addressed two of the three Copilot suggestions:

• Fixed mu organization -> my organization (98f19f0).
• Switched docs.microsoft.com -> learn.microsoft.com (df28f5e).

Skipped the Recorded Future readme line 140 suggestion — the diff is purely Micrsoft -> Microsoft on a non-table line, no whitespace or | change. Looks like a false positive from Copilot's partial-mode review.