I would suggest the following change:

Embedding Elm in some big JavaScript project is not very hard. It's like 
> three lines of JS, but it feels like no one knows about them! So I created 
> react-elm-components to make it much more obvious.


change to something like:

Elm is optimized for embedding into your existing JavaScript projects. With 
> about three lines of JS, you can have Elm components interoperating with 
> your app giving you the opportunity to experiment and experience the power 
> of Elm sooner! I have created react-elm-components to make this even 
> simpler.


Still needs work probably but basically consider the following: "some big 
project" is vague and sounds a bit dismissive of existing JS projects. "not 
very hard" is probably true but try not to assume what is hard for other 
people. "It's like three lines .." also sounds dismissive and like anyone 
should know this obvious thing. It's very obvious to us but not to the 
people you want to capture in this post. Finally, try front loading a bit 
of the Elm awesomeness! Why do I care to embed an Elm component? Probably 
because I want to experiment and Elm is just really great!

-- 
You received this message because you are subscribed to the Google Groups "Elm 
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to