wording changes

Author: andrelandgraf

docs/decisions/039-image-optimization.md

@@ -8,13 +8,18 @@ Status: accepted
 
 As documented in [018-images.md](./018-images.md), the Epic Stack previously
 didn't implement image optimization. Both static app images and dynamic user
-images were served as is. However, optimizing images greatly influences web
-performance and reduces load times and network load. On the other hand, one of
-the guiding principles of the Epic Stack is to limit services (including the
-self-managed variety). A great middle ground is to integrate a simple image
-optimization solution directly into the web server. This allows each Epic Stack
-app to immediately utilize image optimization and serve better web experiences
-without prescribing a service.
+images were served as is. However, optimizing images significantly improves web
+performance by reducing both the browser load time and the byte size of each
+image. On the other hand, one of the guiding principles of the Epic Stack is to
+limit services (including the self-managed variety). A great middle ground is to
+integrate a simple image optimization solution directly into the web server.
+This allows each Epic Stack app to immediately utilize image optimization and
+serve better web experiences without prescribing a service.
+
+On-demand image optimization with a image optimization endpoint should be
+sufficient for most applications and provide value right out of the gate.
+However, it is also important that upgrading to a dedicated service shouldn't be
+overly complicated and require a ton of changes.
 
 ### Using openimg