Fixed typos in my last commit

Author: Linda-Editor

graph/patterns/facets.md

@@ -17,7 +17,7 @@ In this solution, a child variant is identified by the presence of one or more f
 
 ## When to use this pattern
 
-The facet pattern is useful when there is a number of variants and they are not mutually exclusive. It also makes it syntactically easier to query resources by using OData $filter expression because it doesn't require casting.
+The facets pattern is useful when there is a number of variants and they are not mutually exclusive. It also makes it syntactically easier to query resources by using the OData `$filter` expression because it doesn't require casting.
 
 You can consider related patterns such as [type hierarchy](./subtypes.md) and [flat bag of properties](./flat-bag.md).
 
@@ -27,7 +27,7 @@ When introducing a new facet, you need to ensure that the new facet doesn't chan
 
 ## Example
 
-The driveItem resource represents a file, folder, image, or other item stored in a drive and is modeled by using entity type with multiple facets.
+The driveItem resource represents a file, folder, image, or other item stored in a drive and is modeled by using an entity type with multiple facets.
 
 ```XML
 

graph/patterns/long-running-operations.md

@@ -7,7 +7,7 @@ Microsoft Graph API Design Pattern
 ## Problem
 
 The API design requires modeling operations on resources, which takes a long time
-to complete so that API clients don't need to wait and can continue doing other
+to complete, so that API clients don't need to wait and can continue doing other
 work while waiting for the final operation results. The client should be able to
 monitor the progress of the operation and have an ability to cancel it if
 needed.
@@ -48,7 +48,6 @@ presentation makes things simpler for our users and tooling chain.
 
 In general, Microsoft Graph API guidelines for long running operations follow [Microsoft REST API
 Guidelines](https://github.com/microsoft/api-guidelines/blob/vNext/Guidelines.md#13-long-running-operations).
-
 There are some deviations from the base guidelines where Microsoft Graph API standards require that you do one of the following:
 
 - For the RELO pattern, you should return the Location header that indicates the location of the resource.
@@ -214,15 +213,15 @@ Retry-After: 30
 ```
 
 The client waits the recommended 30 seconds and then invokes another request to get
-the results of the operation.
+the results of the operation:
 
 ```
 GET https://graph.microsoft.com/v1.0/storage/operations/123
 ```
 
 
 The server responds with a "status:succeeded" operation that includes the resource
-location.
+location:
 
 ```
 HTTP/1.1 200 OK

graph/patterns/operations.md

@@ -17,7 +17,7 @@ If the operation doesn't have any side effects and MUST return a single instance
 
 The operations pattern is well suited to use cases that cannot be modeled as a single HTTP method on a resource and require either multiple round trips to complete a single logical operation or produce one or multiple side effects.
 
-You can consider related patterns such as [long running operations](./long-running-operations) and [change tracking](./change-tracking).
+You can consider related patterns such as [long running operations](./long-running-operations.md) and [change tracking](./change-tracking.md).
 
 ## Issues and considerations