deprecation dates fix

Author: OlgaPodo

graph/GuidelinesGraph.md

@@ -205,8 +205,8 @@ Limitations of \$query requests made to Microsoft Graph:
 
 ### Resource Modeling Patterns
 
-You can model complex resources for your APIs using OData Entity Type or Complex Type. The main difference between these types is that Entity type declares a key property to uniquely identify its objects and  Complex Type does not. In Microsoft Graph this key property is called "id" for server-created key values. If there is a natural name for the key property then the workload can use that.
-Since objects of complex types on Graph don’t have unique identifiers, they are not directly addressable via URIs and therefore you must not use Complex Type to model addressable resources, such as individually addressable items within a collection. Complex types are better suited to represent composite properties of API entities.
+You can model structured resources for your APIs using OData Entity Type or Complex Type. The main difference between these types is that Entity type declares a key property to uniquely identify its objects and  Complex Type does not. In Microsoft Graph this key property is called "id" for server-created key values. If there is a natural name for the key property then the workload can use that.
+Since objects of complex types on Graph don’t have unique identifiers, they are not directly addressable via URIs and therefore you must not use Complex Type to model addressable resources, such as individually addressable items within a collection, for more information refer to [Microsoft REST API Guidelines](https://github.com/microsoft/api-guidelines/blob/graph/Guidelines.md#93-collection-url-patterns). Complex types are better suited to represent composite properties of API entities.
 
 ```XML
  <EntityType Name="Author">
@@ -384,7 +384,7 @@ breaking change.
 -   Addition of a required request header
 -   Addition of a EnumType members for non-evolvable enumerations
 -   Addition of a Nullable="false" properties to existing types
--   Addition of a parameter not marked as [Nullable](http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_Nullable) to existing actions or functions
+-   Addition of a parameter not marked as [Nullable](http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_Nullable) to existing actions
 -   Addition of a parameter not marked as [Optional](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#OptionalParameter) to an existing function
 -    Changes to top-level error codes
 -    Introduction of server-side pagination to existing collections

graph/deprecation.md

@@ -21,11 +21,11 @@ to annotate any usages of that type.
     <Annotation Term="Org.OData.Core.V1.Revisions">
       <Collection>
         <Record>
-          <PropertyValue Property = "Date" Date="2020-08-20"/>
-          <PropertyValue Property = "Version" String="2020-08/Tasks_And_Plans"/>
+          <PropertyValue Property = "Date" Date="2022-03-30"/>
+          <PropertyValue Property = "Version" String="2022-03/Tasks_And_Plans"/>
           <PropertyValue Property = "Kind" EnumMember="Org.OData.Core.V1.RevisionKind/Deprecated"/>
-          <PropertyValue Property = "Description" String="The Outlook tasks API is deprecated and will stop returning data on August 20, 2022. Please use the new To Do API."/>
-          <PropertyValue Property = "RemovalDate" Date="2022-08-20"/>
+          <PropertyValue Property = "Description" String="The Outlook tasks API is deprecated and will stop returning data on June 30, 2024. Please use the new To Do API."/>
+          <PropertyValue Property = "RemovalDate" Date="2024-06-30"/>
         </Record>
       </Collection>
     </Annotation>
@@ -35,13 +35,13 @@ to annotate any usages of that type.
 
 When the request URL contains a reference to a deprecated model element, the gateway will add a [Deprecation
 header](https://tools.ietf.org/html/draft-dalal-deprecation-header-02) (with the
-date the element was marked as deprecated) and a Sunset header (with the date 2
+date the element was marked as deprecated) and a Sunset header (with the date of 2
 years beyond the Deprecation date) to the response.
 
 **Deprecation header example:**
 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Deprecation: Thursday, 30 June 2022 11:59:59 GMT
-Sunset: Wed, 30 Mar 2022 23:59:59 GMT
-Link: https://docs.microsoft.com/en-us/graph/changelog#2022-03-30_name ; rel="deprecation"; type="text/html"; title="name",https://docs.microsoft.com/en-us/graph/changelog#2020-06-30_state ; rel="deprecation"; type="text/html"; title="state"
+Deprecation: Wed, 30 Mar 2022 11:59:59 GMT
+Sunset:  Thursday, 30 June 2024 23:59:59 GMT
+Link: https://docs.microsoft.com/en-us/graph/changelog#2022-03-30_name ; rel="deprecation"; type="text/html"; title="name",https://docs.microsoft.com/en-us/graph/changelog#2022-03-30_state ; rel="deprecation"; type="text/html"; title="state"
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~