Oh wow, the new copy is much better! Good job! I think you changed the word "features" to "benefits," but didn't change the list of features to benefits. To ge

Oh wow, the new copy is much better! Good job! I think you changed the word "features" to "benefits," but didn't change the list of features to benefits. To get to the benefit, ask "why?" two or three times in a row: - Why do devs want "simplified development?" - Why is that?... And why is that? (It seems your first level "why's" are are under the headers. Again, the simple fix is to change the order: make the benefit the header, then write your feature below that^^) Each time "why?" is asked will get you to a bigger benefit/desire. (You're doing the work you want your reader to do in their head for them.)