From 548c18a2d66d67060c424c404a539998dc74a191 Mon Sep 17 00:00:00 2001 From: Charlie Chu Date: Mon, 5 Dec 2016 15:06:15 +0800 Subject: [PATCH] Fix typo --- aspnetcore/fundamentals/routing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/fundamentals/routing.md b/aspnetcore/fundamentals/routing.md index 7d9df6315c..2ac1cb93ae 100644 --- a/aspnetcore/fundamentals/routing.md +++ b/aspnetcore/fundamentals/routing.md @@ -87,7 +87,7 @@ Routing provides the `Route` class as the standard implementation of `IRouter`. Most applications will create routes by calling `MapRoute` or one of the similar extension methods defined on `IRouteBuilder`. All of these methods will create an instance of `Route` and add it to the route collection. > [!NOTE] -> `MapRoute` doesn't take a route handler parameter - it only adds routes that will be handled by the `DefaultHandler`. Since the default handler is an `IRouter`, it may decide not to handle the request. For example, ASP.NET MVC is typically configured as a default handler that only handles requests that match an available controller and action. To learn more about routing to MVC, see [ðŸ"§ Routing to Controller Actions](../mvc/controllers/routing.md). +> `MapRoute` doesn't take a route handler parameter - it only adds routes that will be handled by the `DefaultHandler`. Since the default handler is an `IRouter`, it may decide not to handle the request. For example, ASP.NET MVC is typically configured as a default handler that only handles requests that match an available controller and action. To learn more about routing to MVC, see [Routing to Controller Actions](../mvc/controllers/routing.md). This is an example of a `MapRoute` call used by a typical ASP.NET MVC route definition: