From a340d2abe3a6a67e493e963c537552b8c18195c4 Mon Sep 17 00:00:00 2001 From: Anton Dosov Date: Fri, 4 Oct 2024 16:10:55 +0200 Subject: [PATCH] improve --- .../chrome_recently_accessed/chrome_recently_accessed.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev_docs/shared_ux/chrome_recently_accessed/chrome_recently_accessed.mdx b/dev_docs/shared_ux/chrome_recently_accessed/chrome_recently_accessed.mdx index 156c8aacecd59..55c8dd06f34b1 100644 --- a/dev_docs/shared_ux/chrome_recently_accessed/chrome_recently_accessed.mdx +++ b/dev_docs/shared_ux/chrome_recently_accessed/chrome_recently_accessed.mdx @@ -20,7 +20,7 @@ The `ChromeRecentlyAccessed` service should be used thoughtfully to provide user DOs: - Register important resources that users may want to revisit. Like a dashboard, a saved search, or another specific object. -- Update the link when the state of the resource changes. For example, if a user changes the time range of a dashboard, update the link to reflect the latest state where possible. +- Update the link when the state of the current resource changes. For example, if a user changes the time range while on a dashboard, update the recently viewed link to reflect the latest viewed state where possible. DON'Ts: