diff --git a/README.mkd b/README.mkd
index b8b7e8c97c532146a4a41f29a19ee2a7e0ef7223..a756e2511a0e185e12ddfc0fbbf98689eb175326 100644
--- a/README.mkd
+++ b/README.mkd
@@ -8,7 +8,7 @@ It is a description of how things currently work, but should be seen as a starti
 
 GHC is an open source project, and we would love you to contribute to it.  For example
 * You can file a bug report.
-* You can help charactise or minimise a bug, so there is a small repro case.
+* You can help characterise or minimise a bug, so there is a small repro case.
 * You can offer a patch that fixes a bug, or improves documentation
 * You can review a merge request
 * You can improve the user manual or documentation in the code.
@@ -29,7 +29,7 @@ But being a member of the GHC Team carries extra power, as well as extra respons
 * Ability to merge patches into GHC's main trunk, subject to GHC’s code review policies. See GHC's [Contributing a Patch](https://gitlab.haskell.org/ghc/ghc/-/wikis/Contributing-a-Patch) documentation for more information about this process.
 * Standing invitation to the GHC weekly meeting.
 
-**Responsibilies**
+**Responsibilities**
 * Actively contribute to GHC, through patches, code review, design discussions, infrastructure.  "Actively contribute" means at least with a tempo of every month or two.  e.g. making a small intervention once a year is not really enough to be a member of the team.
 * Monitor, and when appropriate contribute to, the [`ghc-devs` mailing list](https://mail.haskell.org/mailman/listinfo/ghc-devs).
 * Willingness to proactively review merge requests, when the expertise fits.
diff --git a/team.mkd b/team.mkd
index bdfa916bf8a5fc4807f08c71f66d142970c51a91..856eba2dddbb9dbafd8b8d8e637f2e743eb0519b 100644
--- a/team.mkd
+++ b/team.mkd
@@ -34,7 +34,7 @@ If you don't want to be a member of the team, make a PR to remove yourself.
 | Krzysztof Gogolewski  | @monoidal           |                                                       |
 | Luite Stegeman        | @luite              | JS backend, GHCi, bytecode, performance               |
 | Matt Pickering        | @mpickering         | infrastructure, monitoring, profiling, typed template haskell   |
-| Matthew Craven        | @clyring            |                                                       |
+| Matthew Craven        | @clyring            | semantics of Core and primitives; runtime performance |
 | Melanie Brown         | @mixphix            |                                                       |
 | Moritz Angermann      | @angerman           | macOS; Cross Compilation; LLVM, Native CodeGens (Arm, RiscV); Mobile (iOS, Android); System Integration; CI |
 | Rodrigo Mesquita      | @alt-romes          | linear types, code-gen, runtime-retargetability/toolchains, pattern-match checking |