From 826bfc4ea53af9777f3bc441f2c200dd27ef3b4a Mon Sep 17 00:00:00 2001 From: Thomas Schattschneider Date: Tue, 17 Feb 2026 13:30:09 +0100 Subject: [PATCH] Docs: Fix phrasing in case-study/index.md --- src/content/app-architecture/case-study/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/app-architecture/case-study/index.md b/src/content/app-architecture/case-study/index.md index 29cd792a7f7..254b039e200 100644 --- a/src/content/app-architecture/case-study/index.md +++ b/src/content/app-architecture/case-study/index.md @@ -155,8 +155,8 @@ The example in this case-study demonstrates how one application abides by our recommended architectural rules, but there are many other example apps that could've been written. The UI of this app leans heavily on view models and `ChangeNotifier`, but it could've easily been written -with streams, or with other libraries like provided by the [`riverpod`][], -[`flutter_bloc`][], and [`signals`][] packages. +with streams, or with other libraries such as [`riverpod`][], +[`flutter_bloc`][], and [`signals`][]. The communication between layers of this app handled everything with method calls, including polling for new data. It could've instead used streams to expose data from a repository to