diff --git a/changelogs/client_server/newsfragments/2318.clarification b/changelogs/client_server/newsfragments/2318.clarification
new file mode 100644
index 00000000..8b912430
--- /dev/null
+++ b/changelogs/client_server/newsfragments/2318.clarification
@@ -0,0 +1 @@
+Fix typos, formatting, wording. Contributed by @HarHarLinks.
diff --git a/changelogs/internal/newsfragments/2318.clarification b/changelogs/internal/newsfragments/2318.clarification
new file mode 100644
index 00000000..8b912430
--- /dev/null
+++ b/changelogs/internal/newsfragments/2318.clarification
@@ -0,0 +1 @@
+Fix typos, formatting, wording. Contributed by @HarHarLinks.
diff --git a/config/_default/hugo.toml b/config/_default/hugo.toml
index fd403e34..a33f803b 100644
--- a/config/_default/hugo.toml
+++ b/config/_default/hugo.toml
@@ -65,7 +65,7 @@ description = "Home of the Matrix specification for decentralised communication"
 # Everything below this are Site Params
 
 [params]
-copyright = "The Matrix.org Foundation CIC"
+copyright = "The Matrix.org Foundation C.I.C."
 
 [params.version]
 # must be one of "unstable", "current", "historical"
diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md
index 5f74ad40..d2427880 100644
--- a/content/client-server-api/_index.md
+++ b/content/client-server-api/_index.md
@@ -3320,7 +3320,7 @@ PUT /rooms/!roomid:domain/state/m.room.bgd.color
 ### Redactions
 
 Since events are extensible it is possible for malicious users and/or
-servers to add keys that are, for example offensive or illegal. Since
+servers to add keys that are, for example, offensive or illegal. Since
 some events cannot be simply deleted, e.g. membership events, we instead
 'redact' events. This involves removing all keys from an event that are
 not required by the protocol. This stripped down event is thereafter
@@ -3418,7 +3418,7 @@ This specification describes the following relationship types:
 * [Event replacements](#event-replacements).
 * [Event annotations](#event-annotations-and-reactions).
 * [Threads](#threading).
-* [References](#reference-relations)
+* [References](#reference-relations).
 
 #### Aggregations of child events
 
diff --git a/content/client-server-api/modules/threading.md b/content/client-server-api/modules/threading.md
index 9f87920a..e3365a0d 100644
--- a/content/client-server-api/modules/threading.md
+++ b/content/client-server-api/modules/threading.md
@@ -107,7 +107,7 @@ flag to `true`.
 ```
 
 {{% boxes/note %}}
-Clients which are acutely aware of threads (they do not render threads, but are otherwise
+Clients which are aware of threads (they do not render threads, but are otherwise
 aware of the feature existing in the spec) can treat rich replies to an event with a `rel_type`
 of `m.thread` as a threaded reply, for conversation continuity on the threaded client's side.
 
diff --git a/data/api/client-server/room_send.yaml b/data/api/client-server/room_send.yaml
index 5c3d0019..7393d440 100644
--- a/data/api/client-server/room_send.yaml
+++ b/data/api/client-server/room_send.yaml
@@ -31,7 +31,7 @@ paths:
 
         The body of the request should be the content object of the event; the
         fields in this object will vary depending on the type of event. See
-        [Room Events](/client-server-api/#room-events) for the m. event specification.
+        [Room Events](/client-server-api/#room-events) for the `m.` event specification.
 
         Homeservers MUST allow clients to send `m.room.redaction` events with this
         endpoint for all room versions. In rooms with a version older than 11 they
diff --git a/data/event-schemas/schema/core-event-schema/event.yaml b/data/event-schemas/schema/core-event-schema/event.yaml
index 422ecd53..8238642b 100644
--- a/data/event-schemas/schema/core-event-schema/event.yaml
+++ b/data/event-schemas/schema/core-event-schema/event.yaml
@@ -8,7 +8,7 @@ properties:
     type: object
   type:
     description: The type of event. This SHOULD be namespaced similar to Java package
-      naming conventions e.g. 'com.example.subdomain.event.type'
+      naming conventions e.g. `com.example.subdomain.event.type`
     type: string
 required:
   - type
diff --git a/layouts/_partials/events/render-event.html b/layouts/_partials/events/render-event.html
index 30a20974..b4988ae1 100644
--- a/layouts/_partials/events/render-event.html
+++ b/layouts/_partials/events/render-event.html
@@ -49,7 +49,7 @@
   </tr>
 {{ if $state_key }}
   <tr>
-   <th>State key</th>
+   <th>State key:</th>
    <td>{{ $state_key.description | markdownify }}</td>
  </tr>
 {{ end }}