Fix a few typos (#848)

Author: Blake-Madden

TerminalDocs/customize-settings/profile-appearance.md

@@ -382,7 +382,7 @@ Users can choose different opacity values for focused and unfocused windows allo
 
 :::row:::
 :::column span="":::
-When this is set to `true`, the window will have an acrylic background. When it's set to `false`, the window will have a plain, untextured background. Depending on the `Enable Unfocused Acrylic` global setting the transparency applies to unfocused windows aswell as focused windows when set to `true` or only applies to focused windows when set to `false`.
+When this is set to `true`, the window will have an acrylic background. When it's set to `false`, the window will have a plain, untextured background. Depending on the `Enable Unfocused Acrylic` global setting the transparency applies to unfocused windows as well as focused windows when set to `true` or only applies to focused windows when set to `false`.
 
 **Property name:** `useAcrylic`
 

TerminalDocs/group-policy.md

@@ -26,7 +26,7 @@ You can find the latest administrative templates (ADMX and ADML files) in the as
 
 ### Add the administrative template to Active Directory
 
-1. On a domain controller (a server that responds to security authentication requests within a Windows Server domain) or a [workstation with RSAT](/windows-server/remote/remote-server-administration-tools), go to the **PolicyDefinition** folder (also known as the Central Store) on any domain controller for your domain. For older versions of Windows Server, you might need to create the PolicyDefinition folder. For more information, see [How to create an manage the Central Store for Group Policy Administrative Templates in Windows](/troubleshoot/windows-client/group-policy/create-and-manage-central-store)
+1. On a domain controller (a server that responds to security authentication requests within a Windows Server domain) or a [workstation with RSAT](/windows-server/remote/remote-server-administration-tools), go to the **PolicyDefinition** folder (also known as the Central Store) on any domain controller for your domain. For older versions of Windows Server, you might need to create the PolicyDefinition folder. For more information, see [How to create and manage the Central Store for Group Policy Administrative Templates in Windows](/troubleshoot/windows-client/group-policy/create-and-manage-central-store)
 2. Copy the `WindowsTerminal.admx` file to the **PolicyDefinition** folder.
 (`%systemroot%\sysvol\domain\policies\PolicyDefinitions`)
 3. Copy the `WindowsTerminal.adml` file to the matching language folder in your language folder in your Policy Definition folder. Create the folder if it does not already exist.

TerminalDocs/tutorials/shell-integration.md

@@ -94,7 +94,7 @@ How you enable these marks in your shell varies from shell to shell. Below are t
 
 If you've never changed your PowerShell prompt before, you should check out [about_Prompts](/powershell/module/microsoft.powershell.core/about/about_prompts) first.
 
-We'll need to edit your `prompt` to make sure we tell the Terminal about the CWD, and mark up the prompt with the appropriate marks. PowerShell also lets us include the error code from the previous command in the `133;D` sequence, which will let the terminal automatically colorize the mark based if the command succeeeded or failed.
+We'll need to edit your `prompt` to make sure we tell the Terminal about the CWD, and mark up the prompt with the appropriate marks. PowerShell also lets us include the error code from the previous command in the `133;D` sequence, which will let the terminal automatically colorize the mark based if the command succeeded or failed.
 
 Add the following to your [PowerShell profile](/powershell/module/microsoft.powershell.core/about/about_profiles):