diff --git a/aio/content/guide/http.md b/aio/content/guide/http.md
index e261b3451a6..e4f52097d72 100644
--- a/aio/content/guide/http.md
+++ b/aio/content/guide/http.md
@@ -653,8 +653,20 @@ There are many more interceptors in the complete sample code.
### Interceptor order
Angular applies interceptors in the order that you provide them.
-If you provide interceptors _A_, then _B_, then _C_, requests flow in _A->B->C_ and
-responses flow out _C->B->A_.
+For example, consider a situation in which you want to handle the authentication of your HTTP requests and log them before sending them to a server. To accomplish this task, you could provide an `AuthInterceptor` service and then a `LoggingInterceptor` service.
+Outgoing requests would flow from the `AuthInterceptor` to the `LoggingInterceptor`.
+Responses from these requests would flow in the other direction, from `LoggingInterceptor` back to `AuthInterceptor`.
+The following is a visual representation of the process:
+
+
+
+
+
+
+
+ The last interceptor in the process is always the `HttpBackend` that handles communication with the server.
+
+
You cannot change the order or remove interceptors later.
If you need to enable and disable an interceptor dynamically, you'll have to build that capability into the interceptor itself.
diff --git a/aio/content/images/guide/http/interceptor-order.svg b/aio/content/images/guide/http/interceptor-order.svg
new file mode 100644
index 00000000000..e85d2a6f483
--- /dev/null
+++ b/aio/content/images/guide/http/interceptor-order.svg
@@ -0,0 +1,50 @@
+
+