Merge pull request #514 from microsoft/olgapo-movingREST

moved deprecation to /articles

Author: OlgaPodo

graph/Guidelines-deprecated.md

@@ -1,8 +1,10 @@
 
 > # DEPRECATION NOTICE TO READERS
-> <mark>This document is being deprecated and merged with the  [Microsoft Graph REST API Guidelines](./graph/Guidelines_deprecated.md), with a removal date of 07/01/2024.</mark> Please refer to the notes below for the latest guidance.
-> 
+>
+> <mark>This document is being deprecated and merged with the  [Microsoft Graph REST API Guidelines](GuidelinesGraph.md), with a removal date of 07/01/2024.</mark> Please refer to the notes below for the latest guidance.
+>
 > ## **Guidance for Microsoft Graph service teams**
+>
 > Graph service teams should reference the companion document, [Microsoft Graph REST API Guidelines](GuidelinesGraph.md) when building or modifying their services. This document and the associated pattern catalog provides a refined set of guidance targeted specifically for Microsoft Graph services.
 >
 ---

graph/GuidelinesGraph.md

@@ -384,7 +384,7 @@ Microsoft Graph APIs in the GA version guarantee API stability and consistency f
 
 On the beta endpoint, breaking changes and deprecation of APIs are allowed with consideration of dependencies and customer impact. It is a best practice to test new element versions on the beta endpoint at first and then promote API changes to the GA endpoint.
 
-Detailed requirements for versioning and deprecation are described in the [Deprecation guidelines](./deprecation.md).
+Detailed requirements for versioning and deprecation are described in the [Deprecation guidelines](./articles/deprecation.md).
 
 ## Recommended API design patterns