aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/NVIDIA_Highlights_FAQ.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/NVIDIA_Highlights_FAQ.md b/doc/NVIDIA_Highlights_FAQ.md
index e97f9f0..3b34f03 100644
--- a/doc/NVIDIA_Highlights_FAQ.md
+++ b/doc/NVIDIA_Highlights_FAQ.md
@@ -48,7 +48,7 @@ This document covers the reasons for integrating Highlights, an explanation for
* The button should be prominently displayed to allow users to easily find the feature.
* When implementing your UI element follow the “NVIDIA HIGHLIGHTS BUTTON PROPER USAGE” guidelines document in the _GFE-SDK_ package adhering to the sizes, clear space, and specific colors prescribed there. The package also provides the necessary vector graphics assets files to do so.
-## When should I should I allow the user to open the Highlights Summary?
+## When should I allow the user to open the Highlights Summary?
* When the user has plenty of time to casually interact with their highlights. A short countdown timer before next round starts, where the level reloads and the user is back in the action, would not give the user time.
* When the summary can be repeatedly accessible, allowing the user to open it, close it, and decide to re-open to work with any remaining highlights. If the user accidentally closes it, they shouldn’t be locked out of getting back to their remaining highlights.