Fix spellings

Author: wolf99

docs/azrepos-users-and-tokens.md

@@ -64,7 +64,7 @@ credential. This may change in the future.
 
 Normally you won't need to worry about managing which user accounts Git
 Credential Manager is using as this is configured automatically when you first
-authenticate for a particular Azure DevOps organziation.
+authenticate for a particular Azure DevOps organization.
 
 In advanced scenarios (such as using multiple accounts) you can interact with
 and manage remembered user accounts using the 'azure-repos' provider command:
@@ -181,7 +181,7 @@ fabrikam:
 ```
 
 In the above example, the `~/myrepo` repository has a single Git remote named
-`origin` that points to the `contoso` Azure DevOps organziation. There is no
+`origin` that points to the `contoso` Azure DevOps organization. There is no
 user account specifically associated with the `origin` remote, so the global
 user account binding for `contoso` will be used (the global binding is
 inherited).

docs/bitbucket-development.md

@@ -73,7 +73,7 @@ It is possible to test with Bitbucket Server by running it locally using the fol
 
     ❯ atlas-run-standalone --product bitbucket
 
-See the devloper documentation for [atlas-run-standalone](https://developer.atlassian.com/server/framework/atlassian-sdk/atlas-run-standalone/).
+See the developer documentation for [atlas-run-standalone](https://developer.atlassian.com/server/framework/atlassian-sdk/atlas-run-standalone/).
 
 This will download and run a standalone instance of Bitbucket Server which can be accessed using the credentials `admin`/`admin` at
 

docs/enterprise-config.md

@@ -21,9 +21,9 @@ than having to modify the Git installation configuration files.
 ## User Freedom
 
 We believe the user should _always_ be at liberty to configure
-Git and GCM exactly as they wish. By prefering environment variables and Git
+Git and GCM exactly as they wish. By preferring environment variables and Git
 configuration files over system admin values, these only act as _default values_
-that can always be overriden by the user in the usual ways.
+that can always be overridden by the user in the usual ways.
 
 ## Windows
 

docs/environment.md

@@ -380,7 +380,7 @@ This is especially relevant to OAuth credentials. Bitbucket.org access tokens ex
 
 Enabling this option will improve performance when using Oauth2 and interacting with Bitbucket.org if, on average, commits are done less frequently than every 2 hours.
 
-Enabling this option will decrease performance when using Basic Auth by requiring the user the re-enter credentials everytime.
+Enabling this option will decrease performance when using Basic Auth by requiring the user the re-enter credentials every time.
 
 Value|Refresh Credentials Before Returning
 -|-

docs/multiple-users.md

@@ -12,9 +12,9 @@ Git hosting providers (like GitHub or Bitbucket) _do_ have a concept of "user".
 
 ## People, identities, credentials, oh my
 
-You (a physical person) may have one or more user accounts (identities) with one or more Git hosting providers. Since most Git hosts don't put a "user" part in their URLs, by default, Git will treat the user part for a remote as the empty string. If you have multiple identites on one domain, you'll need to insert a unique user part per-identity yourself.
+You (a physical person) may have one or more user accounts (identities) with one or more Git hosting providers. Since most Git hosts don't put a "user" part in their URLs, by default, Git will treat the user part for a remote as the empty string. If you have multiple identities on one domain, you'll need to insert a unique user part per-identity yourself.
 
-There are good reasons for having multiple identities on one domain. You might use one GitHub identity for your personal work, another for your open source work, and a third for your employer's work. You can ask Git to assign a different credential to different repositories hosted on the same provider. HTTPS URLs include an optional "name" part before an `@` sign in the domain name, and you can use this to force Git to distiguish multiple users. This should likely be your username on the Git hosting service, since there are cases where GCM will use it like a username.
+There are good reasons for having multiple identities on one domain. You might use one GitHub identity for your personal work, another for your open source work, and a third for your employer's work. You can ask Git to assign a different credential to different repositories hosted on the same provider. HTTPS URLs include an optional "name" part before an `@` sign in the domain name, and you can use this to force Git to distinguish multiple users. This should likely be your username on the Git hosting service, since there are cases where GCM will use it like a username.
 
 ## Setting it up