From 56cb9c634f6d1023faaabb90551181ef0992a43d Mon Sep 17 00:00:00 2001 From: andrewlock Date: Sun, 28 May 2017 16:30:02 +0100 Subject: [PATCH] Fix typo in filters.md (#3426) `ReesultFilterAttribute` -> `ResultFilterAttribute` --- aspnetcore/mvc/controllers/filters.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/mvc/controllers/filters.md b/aspnetcore/mvc/controllers/filters.md index acd31a8706..b547907154 100644 --- a/aspnetcore/mvc/controllers/filters.md +++ b/aspnetcore/mvc/controllers/filters.md @@ -302,7 +302,7 @@ When the `OnResultExecuted` method runs, the response has likely been sent to th For an `IAsyncResultFilter` a call to `await next()` on the `ResultExecutionDelegate` executes any subsequent result filters and the action result. To short-circuit, set `ResultExecutingContext.Cancel` to true and do not call the `ResultExectionDelegate`. -The framework provides an abstract `ReesultFilterAttribute` that you can subclass. The [AddHeaderAttribute](#add-header-attribute) class shown earlier is an example of a result filter attribute. +The framework provides an abstract `ResultFilterAttribute` that you can subclass. The [AddHeaderAttribute](#add-header-attribute) class shown earlier is an example of a result filter attribute. ## Using middleware in the filter pipeline