Adopt PR feedback

Co-authored-by: Luke Wagner <mail@lukewagner.name>

Author: lann

wit-0.3.0-draft/worlds.wit

@@ -35,20 +35,20 @@ world service {
 
 /// The `wasi:http/middleware` world captures HTTP services that forward HTTP
 /// Requests to another handler.
-/// 
+///
 /// Components may implement this world to allow them to participate in handler
-/// "chains" where a Request flows through handlers on its way to some terminal
-/// `service` and corresponding Responses flow in the opposite direction.
+/// "chains" where a `request` flows through handlers on its way to some terminal
+/// `service` and corresponding `response` flows in the opposite direction.
 world middleware {
   include service;
   import handler;
 }
 
 /// This interface defines a handler of HTTP Requests.
-/// 
+///
 /// In a `wasi:http/service` this interface is exported to respond to an
 /// incoming HTTP Request with a Response.
-/// 
+///
 /// In `wasi:http/middleware` this interface is both exported and imported as
 /// the "downstream" and "upstream" directions of the middleware chain.
 interface handler {
@@ -62,10 +62,10 @@ interface handler {
 }
 
 /// This interface defines an HTTP client for sending "outgoing" requests.
-/// 
+///
 /// Most components are expected to import this interface to provide the
 /// capability to send HTTP requests to arbitrary destinations on a network.
-/// 
+///
 /// The type signature of `client.send` is the same as `handler.handle`. This
 /// duplication is currently necessary because some Component Model tooling
 /// (including WIT itself) is unable to represent a component importing two