edit

Author: knzai

_posts/2024-09-01-svg-ccc.md

@@ -55,7 +55,7 @@ Note: OG is "OpenGraph" support. See section in [Tradeoffs](#tradeoffs). Late I
 
 ## Tradeoffs
 ### No progressive rendering
-Unlike JPGs, AVIFs don't do [progressive rendering](https://docs.imgix.com/apis/rendering/format/jpg-progressive) so they won't fill in until they are completely downloaded. Given the much smaller size you can acheive with AVIF I feel like that more than negates that, since the whole image might download before the JPG even got to it's first pass anyway.
+Unlike JPGs, AVIFs don't do [progressive rendering](https://docs.imgix.com/apis/rendering/format/jpg-progressive) so they won't fill in until they are completely downloaded. I feel like the much smaller overall size more than negates that, since the whole image might download before the JPG even got to its first pass anyway.
 ### Missing OpenGraph 
 Neither AVIFs or composite SVG work everywhere you can share an OpenGraph/preview tile images (and that's not super easy to track, unlike browser support, since it's based on every individual site or apps support). If you care enough about optimizing your site's images to be reading this post, you are already used to having different sizes and formats for different uses.  And since the OpenGraph tile image doesn't actually load on your site, you can just use your default large png that you were likely already using for your largest responsive layout.
 ### Difficulty managing multiple responsive images (SVG composite)