From 2e8b36c923b16ca993684bbf3b83f0ce652843b7 Mon Sep 17 00:00:00 2001 From: Anton Dosov Date: Mon, 7 Oct 2024 10:25:43 +0200 Subject: [PATCH] Update dev_docs/shared_ux/chrome_recently_accessed/chrome_recently_accessed.mdx Co-authored-by: Tim Sullivan --- .../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 8298f8b584071..3affd360054d8 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 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. +- 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. See below for instructions on how to update the link when state changes. DON'Ts: