Correct accessibility page: widget strikethrough scope and spoken-status examples

Author: one-kash

src/pages/features/accessible-calendar-android.mdx

@@ -15,15 +15,15 @@ Turn on TalkBack and many calendar apps become a guessing game: unlabeled button
 <Cards items={[
   {title: 'Headings to jump between', body: <>Screen titles and the sections in Settings and the drawer are marked as headings, so you jump straight to what you want.</>},
   {title: 'Labeled controls', body: <>Every icon-only button carries a label, so nothing reads as just "button."</>},
-  {title: 'Spoken status', body: <>Sync, a failed save, a sign-in error, an empty search. KashCal announces the change instead of updating silently.</>},
+  {title: 'Spoken status', body: <>Sync progress, going offline, a failed save, a sign-in error. KashCal announces the change instead of updating silently.</>},
   {title: 'Event status, out loud', body: <>A cancelled event says "cancelled," a declined one says "declined." You hear an event's status, not just see it.</>},
   {title: 'Which view you are in', body: <>The drawer announces the active view, not just highlights it.</>},
   {title: 'Actions, not gestures', body: <>Delete a subscription from a menu action, not a swipe a screen reader can't reach.</>},
 ]} />
 
 ## Color is never the only signal
 
-For KashCal users who are colorblind or have low vision, color alone isn't enough to go on. Cancelled and declined events are crossed out, in the app and in the home-screen widgets, so their status shows without relying on color, and a screen reader reads that status aloud.
+For KashCal users who are colorblind or have low vision, color alone isn't enough to go on. A cancelled event is crossed out, in the app and on the home-screen widgets, and a declined event is crossed out in the app, so their status shows without relying on color. A screen reader reads that status aloud too.
 
 ## Accessibility is part of the build