Fix a few typos

2 files changed, 17 insertions, 16 deletions

diff --git a/Documentation/core-repos.md b/Documentation/core-repos.md
index df519440..41197f05 100644
--- a/Documentation/core-repos.md
+++ b/Documentation/core-repos.md
@@ -25,7 +25,7 @@
 
 |Repository                                                        |Description |
 |------------------------------------------------------------------|------------|
-|[Dev Community](https://developercommunity.visualstudio.com/spaces/61/index.html) |Report isssues to .NET Framework Developer Community|
+|[Dev Community](https://developercommunity.visualstudio.com/spaces/61/index.html) |Report issues to .NET Framework Developer Community|
 |[microsoft/dotnet-framework-docker](https://github.com/microsoft/dotnet-framework-docker) |.NET Framework Docker images|
 
 ## .NET Standard
diff --git a/Documentation/microsoft-team.md b/Documentation/microsoft-team.md
index cfab31f8..103cb16c 100644
--- a/Documentation/microsoft-team.md
+++ b/Documentation/microsoft-team.md
@@ -24,17 +24,17 @@ After you join the teams:
 ## Configure your GitHub account as a Microsoft employee (recommended)
 
 * Publicly associate yourself with dotnet and Microsoft orgs
-    * For Microsoft, go to https://github.com/orgs/Microsoft/people
-    * For dotnet, go to https://github.com/orgs/dotnet/people
-    * Search for your GitHub handle in the list
-    * Choose `Public` from the drop-down list of organization visibility
-    * Note: Everyone will now see an org badge on your GH profile in the Organizations section
+  * For Microsoft, go to <https://github.com/orgs/Microsoft/people>.
+  * For dotnet, go to <https://github.com/orgs/dotnet/people>.
+  * Search for your GitHub handle in the list.
+  * Choose `Public` from the drop-down list of organization visibility.
+  * Note: Everyone will now see an org badge on your GH profile in the Organizations section.
 * Update your profile
-    * Go to https://github.com/settings/profile
-    * Match your **Name** on GitHub with full name in address book (so other employees can find you and contact you internally when needed)
-    * Set `@Microsoft` as your **Company**
-    * Upload your **picture**, ideally showing your face
-        * Hint: You can grab your GAL picture from https://microsoft-my.sharepoint.com
+  * Go to <https://github.com/settings/profile>.
+  * Match your **Name** on GitHub with full name in address book (so other employees can find you and contact you internally when needed).
+  * Set `@Microsoft` as your **Company**,
+  * Upload your **picture**, ideally showing your face.
+    * Hint: You can grab your GAL picture from <https://microsoft-my.sharepoint.com>.
 
 ## Install Microsoft open source tools (recommended)
 
@@ -48,9 +48,10 @@ The browser extension is recommended. The VS code extension is optional.
 ## Get write permissions to repos (optional)
 
 Join teams to gain write access to repos:
- * Request team membership via https://repos.opensource.microsoft.com/teams
- * Ask someone if you don't know which team(s) to join.
- * Select `Request to join this team` on the right side - it will send email request to maintainers of the team
+
+* Request team membership via <https://repos.opensource.microsoft.com/teams>.
+* Ask someone if you don't know which team(s) to join.
+* Select `Request to join this team` on the right side - it will send email request to maintainers of the team.
 
 ## Security best practices
 
@@ -60,7 +61,7 @@ The following best practices are required for org owners, and recommended for re
 
 * Do register a [security key(s)](https://www.yubico.com/works-with-yubikey/catalog/github/) as a two factor method.
 * Do register an authenticator app -- registering a one-time-password with an app like 1Password is recommended (not tied to your phone).
-* Do store recorvery codes in a safe place, like [OneDrive Vault](https://www.microsoft.com/microsoft-365/onedrive/personal-vault), 2FA-protected OneNote or in a password vault like 1Password.
+* Do store recovery codes in a safe place, like [OneDrive Vault](https://www.microsoft.com/microsoft-365/onedrive/personal-vault), 2FA-protected OneNote or in a password vault like 1Password.
 * Do register your GitHub account with your 2FA-protected Facebook account for GitHub account recovery. This is the absolute last recovery option and is considered secure (even if your Facebook account is breached).
 * Do not use SMS for 2FA or as a recovery fallback.
 
@@ -71,7 +72,7 @@ A few more notes on hardware keys:
 * You should have at least one hardware key that does not travel with you, but is stored in a secure location (like at home) as a last resort in case you lose access to other factors.
 * If you have a FIDO2 key, it can be used with [mysignins](https://mysignins.microsoft.com/).
 * If you have USB-C and USB-A only devices, and want to use hardware keys for them, then you need [separate keys](https://www.yubico.com/works-with-yubikey/catalog/github/). This explains why the example below has three keys registered (one securely stored at home, and two keys for daily use for USB-C and USB-A only devices).
-* You can use Windows Hello to signin as a hardware key. This is fine to use, but doesn't replace the need for hardware key that you store in a secure location.Your Windows Hello key is not tied to you, but the machine. It won't survive hardware failures or re-installing Windows.
+* You can use Windows Hello to sign in as a hardware key. This is fine to use, but it doesn't replace the need for hardware key that you store in a secure location. Your Windows Hello key is not tied to you, but the machine. It won't survive hardware failures or re-installing Windows.
 
 A correctly configured account should look similar to the following: