diff --git a/knowledge-base/extend-busyindicator-coverage-flyout-net-maui.md b/knowledge-base/extend-busyindicator-coverage-flyout-net-maui.md
index 6ba83ee8..d7fb9a07 100644
--- a/knowledge-base/extend-busyindicator-coverage-flyout-net-maui.md
+++ b/knowledge-base/extend-busyindicator-coverage-flyout-net-maui.md
@@ -35,7 +35,7 @@ This knowledge base article also answers the following questions:
 
 ## Solution
 
-To cover the Flyout area of the Microsoft Shell along with the application's content page using BusyIndicator, you need to define a separate BusyIndicator or an overlay specifically for the Flyout. The Flyout area is not part of the application's main visual tree but is a separate page, requiring its own BusyIndicator implementation.
+To cover the Flyout area of the Microsoft Shell along with the application's content page using BusyIndicator, define a separate BusyIndicator or an overlay specifically for the Flyout. The Flyout area is not part of the application's main visual tree but a separate page requiring its own BusyIndicator implementation.
 
 To achieve this, access your Shell definition and override the `FlyoutContent` to include a BusyIndicator. This allows you to show the BusyIndicator or an overlay specifically for the Flyout menu.