From ab40a462782879eb50388592d0b9d9b363315c5a Mon Sep 17 00:00:00 2001 From: Rob Date: Sat, 26 May 2018 12:52:34 +0200 Subject: [PATCH] Small fixes in documentation --- docs/_documentation/tutorials/tipcalc/the-core-project.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/_documentation/tutorials/tipcalc/the-core-project.md b/docs/_documentation/tutorials/tipcalc/the-core-project.md index cef833286..0660e75ff 100644 --- a/docs/_documentation/tutorials/tipcalc/the-core-project.md +++ b/docs/_documentation/tutorials/tipcalc/the-core-project.md @@ -314,7 +314,7 @@ We won't go into depth here about what IoC - Inversion of Control - is. Instead, we will just say that: -- Within each MvvmCross application, there is a very special object, whici is a `singleton`. +- Within each MvvmCross application, there is a very special object, which is a `singleton`. - This `singleton` lives within the `Mvx` static class. - The application startup code can use the `Mvx.Register...` methods to let `Mvx` know how to resolve certain requests during the lifetime of the app. - After the registration has been done, then when any code asks for an `interface` implementation, it can do that by using the `Mvx.Resolve` methods. @@ -324,7 +324,7 @@ One common pattern the app is also using is 'constructor injection': - Our `TipViewModel` uses this pattern. - It presents a constructor like: `public TipViewModel(ICalculationService calculationService)`. - When the app is running a part of the MvvmCross framework called the `ViewModelLocator` is used to find and create ViewModels. -- when a `TipViewModel` is needed, the `ViewModelLocator` uses a call to `Mvx.IocConstruct` to create one. +- When a `TipViewModel` is needed, the `ViewModelLocator` uses a call to `Mvx.IocConstruct` to create one. - This `Mvx.IocConstruct` call creates the `TipViewModel` using the `ICalculationService` implementation that it finds using `Mvx.Resolve` This is obviously only a very brief introduction.