From 6e8107bd809f96c75b622de4064a3ab856432bad Mon Sep 17 00:00:00 2001
From: Vivek Sharma <40730402+V9vek@users.noreply.github.com>
Date: Tue, 11 Jan 2022 20:57:25 +0530
Subject: [PATCH] Update Navigation README.md (#1685)

---
 tutorials/Navigation/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tutorials/Navigation/README.md b/tutorials/Navigation/README.md
index cf10cf591a..c9878749c4 100644
--- a/tutorials/Navigation/README.md
+++ b/tutorials/Navigation/README.md
@@ -159,7 +159,7 @@ The second point may be especially useful in Desktop. When a child is pushed to
 
 The third point is about instances retaining, like AndroidX `ViewModels`, and is mostly used in Android. It allows to retain (keep in memory) some data when Android configuration change occurs and the whole navigation stack is recreated. The most important advantage of instance retaining in this pattern is that it is encapsulated in children as implementation details.
 
-The forth point is not that obvious but might be very important. Separating navigation and business logic from the user interface may improve testability. E.g. it becomes possible to test non-UI code in integration with just plain JUnit tests. And the UI can be tested in isolation as well using another testing frameworks.
+The fourth point is not that obvious but might be very important. Separating navigation and business logic from the user interface may improve testability. E.g. it becomes possible to test non-UI code in integration with just plain JUnit tests. And the UI can be tested in isolation as well using another testing frameworks.
 
 You can find some integration tests in the TodoApp example: