diff --git a/architecture/networking/routes.adoc b/architecture/networking/routes.adoc
index 64c1dc553e0b..f38e79732422 100644
--- a/architecture/networking/routes.adoc
+++ b/architecture/networking/routes.adoc
@@ -303,8 +303,13 @@ Path based routes specify a path component that can be compared against
 a URL (which requires that the traffic for the route be HTTP based) such
 that multiple routes can be served using the same host name, each with a
 different path. Routers should match routes based on the most specific
-path to the least; however, this depends on the router implementation. The
-following table shows example routes and their accessibility:
+path to the least; however, this depends on the router implementation. 
+The host name and path are passed through to the backend server so it should be
+able to successfully answer requests for them. 
+For example: a request to http://example.com/foo/ that goes to the router will
+result in a pod seeing a request to http://example.com/foo/.
+
+The following table shows example routes and their accessibility:
 
 .Route Availability
 [cols="3*", options="header"]
@@ -351,6 +356,7 @@ the router does not terminate TLS in that case and cannot read the contents
 of the request.
 ====
 
+
 [[secured-routes]]
 == Secured Routes
 Secured routes specify the TLS termination of the route and, optionally,