From 106c21b7e03460bcc570b6978d986e4042742c6d Mon Sep 17 00:00:00 2001 From: Alaa Masoud Date: Thu, 17 Dec 2015 17:36:11 +0300 Subject: [PATCH] Removed duplicate word --- aspnet/fundamentals/middleware.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnet/fundamentals/middleware.rst b/aspnet/fundamentals/middleware.rst index 0d1de0eb35..1dd20e0e32 100644 --- a/aspnet/fundamentals/middleware.rst +++ b/aspnet/fundamentals/middleware.rst @@ -91,7 +91,7 @@ You configure the HTTP pipeline using the `extensions `_ itself exposes a single ``Use`` method, so technically they're not all *extension* methods. -We've already seen several examples of how to build a request pipeline with ``Use``. ``Map*`` extensions are used as a convention for branching the pipeline. The current implementation supports branching based based on the request's path, or using a predicate. The ``Map`` extension method is used to match request delegates based on a request's path. ``Map`` simply accepts a path and a function that configures a separate middleware pipeline. In the following example, any request with the base path of ``/maptest`` will be handled by the pipeline configured in the ``HandleMapTest`` method. +We've already seen several examples of how to build a request pipeline with ``Use``. ``Map*`` extensions are used as a convention for branching the pipeline. The current implementation supports branching based on the request's path, or using a predicate. The ``Map`` extension method is used to match request delegates based on a request's path. ``Map`` simply accepts a path and a function that configures a separate middleware pipeline. In the following example, any request with the base path of ``/maptest`` will be handled by the pipeline configured in the ``HandleMapTest`` method. .. literalinclude:: middleware/sample/src/MiddlewareSample/Startup.cs :language: c#