diff --git a/current/en-us/6. routing/1. configuration.md b/current/en-us/6. routing/1. configuration.md
index 60bb355..4bb8087 100644
--- a/current/en-us/6. routing/1. configuration.md	
+++ b/current/en-us/6. routing/1. configuration.md	
@@ -569,7 +569,7 @@ export class App {
 }
 ```
 
-Alternatively, you can also use `addPipelineStep(name, step)` with predefined step names from `PipelineSlotName` enum export. 
+Alternatively, you can also use `addPipelineStep(name, step)` with predefined step names from `PipelineSlotName` enum export.
 
 ```JavaScript Using PipelineSlotName export
 import { PipelineSlotName } from 'aurelia-router';
@@ -644,7 +644,7 @@ import { RouterEvent } from 'aurelia-router';
 
 export class App {
   static inject = [EventAggregator];
-  
+
   constructor(ea) {
     ea.subscribe(RouterEvent.Complete, (event) => {
       console.log(event.instruction);
@@ -662,7 +662,7 @@ import {
 
 export class App {
   static inject = [EventAggregator];
-  
+
   constructor(ea: EventAggregator) {
     ea.subscribe(RouterEvent.Complete, (event: { instruction: NavigationInstruction; result: PipelineResult }) => {
       console.log(event.instruction);
@@ -1174,7 +1174,12 @@ export class App {
 
 ## Reusing an Existing View Model
 
-Since the view model's navigation lifecycle is called only once, you may have problems recognizing that the user switched the route from `Product A` to `Product B` (see below). To work around this issue implement the method `determineActivationStrategy` in your view model and return hints for the router about what you'd like to happen. Available return values are `replace` and `invoke-lifecycle`. Remember, "lifecycle" refers to the navigation lifecycle.
+For route transitions across different view-models, aurelia will always create a new instance of the new view model. But when the same view-model is used for two routes (see below), the view model is not replaced by default and only the view model's navigation lifecycle is called. You may have problems recognizing that the user switched the route from Product A to Product B. To work around this issue, you can implement the method `determineActivationStrategy` in your view model. This will return hints for the router about what you'd like to happen. Available return values are:
+
+* replace
+* invoke-lifecycle.
+
+`replace` does not re-use the existing view-model, i.e. you get a new instance of product. This is less performant but if your view model builds up local state, you will have a clean start. `invoke-lifecycle` means, invoke the navigation lifecycle. Aurelia then re-uses the View-Model and (only) issues canDeactivate, deactivate, canActivate, activate callbacks on the same instance - e.g. new Product() - when switching from one route to another. This is efficient, but might surprise developers, because the view-model instance is not in a clean state.
 
 ```JavaScript Router View Model Activation Control
 //app.js
@@ -1226,4 +1231,4 @@ export class Product implements RoutableComponentDetermineActivationStrategy {
 ```
 
 > Info
-> Alternatively, if the strategy is always the same and you don't want that to be in your view model code, you can add the `activationStrategy` property to your route config instead.
+> Alternatively, if the strategy is always the same and you don't want that to be in your view model code, you can add the `activationStrategy` property to your route config instead.
\ No newline at end of file