From dbf1a6ca505d82c86b163fed302d6aec4e88ff4e Mon Sep 17 00:00:00 2001 From: Greg Eades Date: Tue, 11 Jul 2023 11:36:03 -0400 Subject: [PATCH] Update 130-The-Widget-Tree.md: correct typos --- pages/130-The-Widget-Tree.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/130-The-Widget-Tree.md b/pages/130-The-Widget-Tree.md index 85ac5a3..7608a4a 100644 --- a/pages/130-The-Widget-Tree.md +++ b/pages/130-The-Widget-Tree.md @@ -226,7 +226,7 @@ Keep in mind, to improve performance, you always want to rely on as few Stateful ### Inherited Widgets -I will not go in detail on Inherited Widgets [\[38\]](https://api.flutter.dev/flutter/widgets/InheritedWidget-class.html) here. When using the BLoC library [\[39\]](https://felangel.github.io/bloc/#/), which I will teach you in the chapter [Architecting a Flutter-App](https://github.com/devonfw-forge/devonfw4flutter/wiki/200-Architecting-a-Flutter-App), you will most likely never create an Inherited Widgets yourself. But in short: They are a way to expose data from the top of the Widget Tree to all their descendants. And they are used as the underlying technology of the BLoC library. +I will not go in detail on Inherited Widgets [\[38\]](https://api.flutter.dev/flutter/widgets/InheritedWidget-class.html) here. When using the BLoC library [\[39\]](https://felangel.github.io/bloc/#/), which I will teach you in the chapter [Architecting a Flutter-App](https://github.com/devonfw-forge/devonfw4flutter/wiki/200-Architecting-a-Flutter-App), you will most likely never create Inherited Widgets yourself. But in short: they are a way to expose data from the top of the Widget Tree to all their descendants. And they are used as the underlying technology of the BLoC library.

Next Chapter: Asynchronous Flutter >

Back to Top