From a88a14dbbb43c2d935e2d047541d2e4304f6e93f Mon Sep 17 00:00:00 2001
From: Nadezhda Tacheva <73842592+ntacheva@users.noreply.github.com>
Date: Tue, 16 Jan 2024 13:48:07 +0200
Subject: [PATCH] update enhanced keyboard support info

---
 accessibility/keyboard-navigation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/accessibility/keyboard-navigation.md b/accessibility/keyboard-navigation.md
index 8e9def0248..341111077c 100644
--- a/accessibility/keyboard-navigation.md
+++ b/accessibility/keyboard-navigation.md
@@ -27,7 +27,7 @@ Most of the components in the library represent a single `Tab` stop. Once users
 The Telerik UI for Blazor components may provide enhanced, standard, or no keyboard support.
 
 * *Standard keyboard support* implies similar keyboard navigation capabilities as standard HTML elements. For example, the Button components support `Enter` and `Space` for clicking them. All components with standard keyboard support are reachable through the `Tab` key and provide focus styles.
-* *Enhanced keyboard support* builds on top of the standard key combinations and provides additional shortcuts for improved flexibility and user experience.
+* *Enhanced keyboard support* builds on top of the standard key combinations and provides additional built-in shortcuts for improved flexibility and user experience.
 * The components with no keyboard support serve a purely visualization purpose, are just content containers, provide no interaction, or provide only mouse and touch interaction by design.
 
 ## Right-to-Left Support