From 3c1def84f2e6ba17a4cc18e7e4834407a0f79cf3 Mon Sep 17 00:00:00 2001 From: Ahmad Bamieh Date: Wed, 26 May 2021 17:31:24 +0300 Subject: [PATCH] Update src/core/server/deprecations/README.mdx Co-authored-by: Alison Goryachev --- src/core/server/deprecations/README.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/core/server/deprecations/README.mdx b/src/core/server/deprecations/README.mdx index 2176556fe6e48..ffa94abe279c0 100644 --- a/src/core/server/deprecations/README.mdx +++ b/src/core/server/deprecations/README.mdx @@ -168,7 +168,7 @@ The deprecations service expects a `200` status code to recognize the corrective ## How do I test my deprecations? We recommend testing the route for your api corrective actions via unit and plugin functional tests. -To check the deprecation in the UI pleae check the UA page. +To check the deprecation in the UI please check the UA page. To test that your logic registering the deprecations with the deprecations service during `setup` is valid we recommend adding unit tests to check that the `getDeprecations` is returning the expected array of deprecations at different scenarios.