Update typographical errors in tutorial readme files

Author: theck13

samples/tutorial/Tutorial1.md

@@ -373,7 +373,7 @@ You could also write:
     }
 ```
 
-And let's make an `onLogInTapped` event handler that enques one of those `updateName` actions.
+And let's make an `onLogInTapped` event handler that enqueues one of those `updateName` actions.
 
 ```kotlin
 object WelcomeWorkflow : StatefulWorkflow<Unit, State, Output, WelcomeScreen>() {

samples/tutorial/Tutorial5.md

@@ -464,7 +464,7 @@ class TodoNavigationWorkflowTest {
 The `RenderTester` allows easy "mocking" of child workflows and workers.
 However, this means that we are not exercising the full infrastructure
 (even though we could get a fairly high confidence from the tests).
-ometimes, it may be worth putting together integration tests that test a full tree of Workflows.
+Sometimes, it may be worth putting together integration tests that test a full tree of Workflows.
 This lets us test integration with the non-workflow world as well,
 such as external reactive data sources that your workflows might be observing via Workers.
 
@@ -482,12 +482,12 @@ the same runtime that `renderWorkflowIn` uses.
 When you create an Android app using Workflow,
 you will probably use `renderWorkflowIn`,
 which starts a runtime to host your workflows in an androidx ViewModel.
-Under the hood,this method is an overload of lower-level `renderWorkflowIn` function
+Under the hood, this method is an overload of lower-level `renderWorkflowIn` function
 that runs the workflow runtime in a coroutine and exposes a `StateFlow` of renderings.
 When writing integration tests for workflows,
 you can use this core function directly (maybe with a library like [Turbine](https://github.com/cashapp/turbine)),
 or you can use `workflow-testing`'s `WorkflowTester`.
-The `WorkflowTester` starts a workflow and lets you request renderingsand outputs manually
+The `WorkflowTester` starts a workflow and lets you request renderings and outputs manually
 so you can write tests that interact with the runtime from the outside.
 
 This will be a properly opaque test,