diff --git a/WIRING.md b/WIRING.md
index 48a3ca152..bddb1614c 100644
--- a/WIRING.md
+++ b/WIRING.md
@@ -208,7 +208,7 @@ and forth between each other. There are two implementations of each API, one
 that uses HTTP requests and one that does not. The HTTP implementation is
 used in multi-process mode, so processes on separate computers may still
 communicate, whereas in single-process or Monolith mode, the direct
-implementation is used. HTTP is preferred here to kaffka streams as it allows
+implementation is used. HTTP is preferred here to kafka streams as it allows
 for request responses.
 
 Running `dendrite-monolith-server` will set up direct connections between
@@ -222,8 +222,8 @@ name>/<name>/<name>.go`.
 
 As an example, the `appservices` component allows other Dendrite components
 to query external application services via its internal API. A component
-would call the desired function in `/appservices/api/query.go`. This would
-send an internal HTTP request, which would be handled by a function in
-`/appservices/query/query.go`. In single-process mode, no internal HTTP
-request occurs, instead functions are simply called directly, thus requiring
-no changes on the calling component's end.
\ No newline at end of file
+would call the desired function in `/appservices/api/query.go`. In
+multi-process mode, this would send an internal HTTP request, which would
+be handled by a function in `/appservices/query/query.go`. In single-process
+mode, no internal HTTP request occurs, instead functions are simply called
+directly, thus requiring no changes on the calling component's end.