diff --git a/README.md b/README.md
index c0ae2e5..d52f2f9 100644
--- a/README.md
+++ b/README.md
@@ -102,7 +102,7 @@ If files get large, buffering them through the NestJS server becomes a bottlenec
 - This makes the backend infinitely more scalable and cheaper to run, while cloud storage handles the heavy lifting.
 
 ### Input Validation
-Currently, identifier formatting (UUID vs. Case Number) is handled via a helper function in the service layer. For production, I'd create a custom class validator so it fails at the entry point instead (i.e. "Fail Fast" principle).
+Currently, identifier formatting (UUID vs. Case Number) is handled via a helper function in the service layer. For production, I'd create a custom class validator so it fails at the entry point instead (i.e. "Fail Fast" principle) and apply it to the DTO.
 
 ### Worker Isolation
 My queue implementation is a good first step (passing heavy work to a child process instead of blocking the main thread), but in production I'd look at completely isolating the workers — perhaps into their own container. This keeps NestJS as a lightweight entry point, while being able to spin up many separate workers for processing multiple PDFs simultaneously. Other improvements: