fix: fix link again

close #488

Author: 3cp

current/en-us/2. tutorials/1. creating-a-todo-app.md

@@ -121,7 +121,7 @@ Here's what's amazing. This is all the ${context.language.name} code for the app
 
 ## Rendering the App
 
-As a brief recap, remember that almost nothing we've done so far is Aurelia-specific. Almost all the code we've written is just vanilla ${context.language.name}. There is `src/main${context.language.fileExtension}` file which is the starting point of your app, it conventionally use `src/app${context.language.fileExtension}` as the root UI component by default. For more information, read [App Configuration and Startup](../docs/fundamentals/app-configuration-and-startup).
+As a brief recap, remember that almost nothing we've done so far is Aurelia-specific. Almost all the code we've written is just vanilla ${context.language.name}. There is `src/main${context.language.fileExtension}` file which is the starting point of your app, it conventionally use `src/app${context.language.fileExtension}` as the root UI component by default. For more information, read [App Configuration and Startup](/docs/fundamentals/app-configuration-and-startup).
 
 In order to render, we need to create a view for the `app` component. This introduces the next convention of Aurelia. To create a view for any class, simply create an HTML file with the same name as the ${context.language.name} module but change the file extension to `.html`. Inside that view, you can place an HTML 5 template with *data binding expressions* declaring how the view should render an instance of the class. Let's start with a very basic view of our `app`, overwrite `src/app.html` provided by the skeleton.