From d3a9465e2cbe0f3bbd2b64c5183dffc0ecbdc00f Mon Sep 17 00:00:00 2001 From: Jon Cox Date: Wed, 24 Jan 2024 22:13:01 +0000 Subject: [PATCH] Documentation: Fixed a small typo. (#2723) --- .../Documentation.docc/Articles/WhatIsNavigation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Sources/ComposableArchitecture/Documentation.docc/Articles/WhatIsNavigation.md b/Sources/ComposableArchitecture/Documentation.docc/Articles/WhatIsNavigation.md index 258c87688762..307038ce9de7 100644 --- a/Sources/ComposableArchitecture/Documentation.docc/Articles/WhatIsNavigation.md +++ b/Sources/ComposableArchitecture/Documentation.docc/Articles/WhatIsNavigation.md @@ -274,7 +274,7 @@ few bugs in `NavigationStack`, but on average it is a lot more stable. #### Cons of stack-based navigation - * Stack-based navigation is not a concise tool. It makes it possible to expressive navigation + * Stack-based navigation is not a concise tool. It makes it possible to express navigation paths that are completely non-sensical. For example, even though it only makes sense to navigate to an edit screen from a detail screen, in a stack it would be possible to present the features in the reverse order: