Fix typos

Author: bl-ue

azure/Guidelines.md

@@ -172,7 +172,7 @@ Evolutionary changes do not require prior approval (but still need a version bum
 
 #### Changing the API without changing the version
 
-Because the API version represents a contract that a developer can rely on when generating SDKs to communicate with the service, there are a limited set of situations where changing the API is permissable without a version bump.  The only changes universally allowed:
+Because the API version represents a contract that a developer can rely on when generating SDKs to communicate with the service, there are a limited set of situations where changing the API is permissible without a version bump.  The only changes universally allowed:
 
 1. Adding a new (optional) value to an extensible enum.
 

graph/dictionary/client-guidance.md

@@ -42,7 +42,7 @@ SDKs need to provide support for dictionary types so SDK consummers get a deligh
 
 - Dictionaries support OData annotations (values prefixed with **@OData**), such annotations should not be inserted directly in the dictionary but rather in the additional properties manager.
 - Dictionary types can inherit another dictionary type, this inheritance must be respected.
-- Dictionary values can be of union types, if the target langauge doesn't support union types, a wrapper type should be generated as backward compatible solution with properties for each type of the union.
+- Dictionary values can be of union types, if the target language doesn't support union types, a wrapper type should be generated as backward compatible solution with properties for each type of the union.
 
 ### Dotnet
 

graph/dictionary/index.md

@@ -22,7 +22,7 @@ Before using a dictionary type in your API definition make sure your scenario fi
 
 ## JSON payload example
 
-The following example illustrates the resulting JSON for a property of dictionary type. The parent object has been ommitted for brievety.
+The following example illustrates the resulting JSON for a property of dictionary type. The parent object has been omitted for brievety.
 
 ```json
 {
@@ -48,7 +48,7 @@ In this set of examples we're modeling a **roles** property of dictionary type o
 GET https://graph.microsoft.com/v1.0/users/10/roles/author
 ```
 
-Reponse:
+Response:
 
 ```json
 {
@@ -62,7 +62,7 @@ Reponse:
 GET https://graph.microsoft.com/v1.0/users/10/roles
 ```
 
-Reponse:
+Response:
 
 ```json
 {
@@ -84,7 +84,7 @@ Reponse:
 GET https://graph.microsoft.com/v1.0/users/10
 ```
 
-Reponse:
+Response:
 
 ```json
 {
@@ -134,7 +134,7 @@ PATCH https://graph.microsoft.com/v1.0/users/10/roles
 ```
 
 > Note: setting one of the keys to **null** deletes it from the dictionary.
-> Note: the domain values for the existing author and maintainer entries will get udpated.
+> Note: the domain values for the existing author and maintainer entries will get updated.
 > Note: the reviewer entry will be inserted in the dictionary.
 
 ### Updating an entry in the dictionary