From d23ade7a1c337baa1f5e4c3c428fb686c01978a7 Mon Sep 17 00:00:00 2001
From: Luke Latham <1622880+guardrex@users.noreply.github.com>
Date: Fri, 21 Sep 2018 13:23:01 -0500
Subject: [PATCH] Link fix

---
 aspnetcore/fundamentals/servers/aspnet-core-module.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/aspnetcore/fundamentals/servers/aspnet-core-module.md b/aspnetcore/fundamentals/servers/aspnet-core-module.md
index be0fe972de6b..9292cb6bb49a 100644
--- a/aspnetcore/fundamentals/servers/aspnet-core-module.md
+++ b/aspnetcore/fundamentals/servers/aspnet-core-module.md
@@ -93,7 +93,7 @@ Because ASP.NET Core apps run in a process separate from the IIS worker process,
 
 The following diagram illustrates the relationship between IIS, the ASP.NET Core Module, and an app:
 
-![ASP.NET Core Module](aspnet-core-module/_static/ancm-outprocess.png)
+![ASP.NET Core Module](aspnet-core-module/_static/ancm-outofprocess.png)
 
 Requests arrive from the web to the kernel-mode HTTP.sys driver. The driver routes the requests to IIS on the website's configured port, usually 80 (HTTP) or 443 (HTTPS). The module forwards the requests to Kestrel on a random port for the app, which isn't port 80/443.