diff --git a/docs/architecture/decisions/0025-caching b/docs/architecture/decisions/0025-caching
index 1b4699134..455df6590 100644
--- a/docs/architecture/decisions/0025-caching
+++ b/docs/architecture/decisions/0025-caching
@@ -67,5 +67,5 @@ Here are notes for implementing caching using whitenoise should we decide to pic
     Before you can continue, work with Cameron to setup the DNS in AWS (use the following documentation linked below):
     https://cloud.gov/docs/services/external-domain-service/
     - Once the DNS is setup, you *should* be able to continue.  We did not test this.
-2- Enable caching with Whitenoise (see https://whitenoise.readthedocs.io/en/latest/django.html#add-compression-and-caching-support)
-3- Take performance measurements before/after caching is enabled to determine cost-benefits of implementing caching. (NOTE: ![lighthouse](https://developer.chrome.com/blog/lighthouse-load-performance) might be useful for this)
+2- Enable caching in the code with Whitenoise (see https://whitenoise.readthedocs.io/en/latest/django.html#add-compression-and-caching-support)
+3- Take performance measurements before/after caching is enabled to determine cost-benefits of implementing caching. (NOTE: ![lighthouse](https://developer.chrome.com/blog/lighthouse-load-performance) might be useful for this step)