Proper format before refactor

The point of this refactor is to simplify the HTTP Task build process. This makes it easier to build more implementations on top later in the development, and it improves the code base's vocabulary.

Currently, a lot of the Elm types have names like 'Snackbar' or 'Context' and they're even threatening to devolve into terms like 'Vnackbar'. Hopefully, many of these types should either be removed or gain renewed names.

src/Internal/Api/GetEvent/Api.elm

@@ -29,6 +29,7 @@ getEventInputV1 data context =
             ]
         |> R.toTask SO1.clientEventDecoder
 
+
 getEventInputV2 : GetEventInputV1 -> Context { a | accessToken : (), baseUrl : (), sentEvent : () } -> Task X.Error GetEventOutputV1
 getEventInputV2 data context =
     context

src/Matrix/Room.elm

@@ -230,6 +230,7 @@ Keep in mind that this function is not safe to use if you're sending exactly the
 
     -- NOT SAFE
     Cmd.batch [ sendOneEvent data , sendOneEvent data ]
+
 -}
 sendOneEvent : { content : D.Value, eventType : String, room : Room, stateKey : Maybe String, onResponse : VaultUpdate -> msg } -> Cmd msg
 sendOneEvent =