Typo is not in my vocabulary

src/pages/en/blog/2023-11-30-quilt-update.md

@@ -33,6 +33,6 @@ Since the main team is busy toiling away on [Enigma](https://github.com/QuiltMC/
 
 Now: what is that `2.0` update that the team is so caught up with? Enigma is our *deobfuscator*, the program that we use to create mappings for Minecraft. It allows you to see and navigate Minecraft's obfuscated code, as well as apply names you come up with. This month we've been working on the final improvements to its plugin system, shipping two big changes. First, Iota added new parsing features for profiles, with allow you to pass in data to plugins. In QM we use this to pass in information on Minecraft classes to [our plugin](https://github.com/QuiltMC/quilt-enigma-plugin). Iota's [pull request](https://github.com/QuiltMC/enigma/pull/158) allows you to use a JSON list instead of an unwieldy string object, making parsing simpler for plugins and allowing JSON validation to act on lists.
 
-Secondly, I worked on a [huge pull request](https://github.com/QuiltMC/enigma/pull/163) which overhauled the *name proposal API*, which allows plugins to automatically . This means that an Enigma plugin is able to analyse compiled Java code, and guess — or _propose_ — new names based on it. This is incredibly useful for repetitive code, and reduces the workload for the humans who work on QM. We also added tons of documentation, and a priority system that decides which plugin takes priority if two plugins propose a name for the same entry. Additionally, we fixed some crashes, squashed some bugs, removed some Recaf mapping format support, updated some other APIs, and cleaned up and documented internals as always.
+Secondly, I worked on a [huge pull request](https://github.com/QuiltMC/enigma/pull/163) which overhauled the *name proposal API*, which allows plugins to automatically propose names for mappings. This means that an Enigma plugin is able to analyse compiled Java code, and guess — or _propose_ — new names based on it. This is incredibly useful for repetitive code, and reduces the workload for the humans who work on QM. We also added tons of documentation, and a priority system that decides which plugin takes priority if two plugins propose a name for the same entry. Additionally, we fixed some crashes, squashed some bugs, removed some Recaf mapping format support, updated some other APIs, and cleaned up and documented internals as always.
 
 Currently, Enigma `2.0` is in the home stretch! Iota is busy porting our plugin and refining the updates to the API, and I'm moving Enigma's configuration backend to our own in-house [Quilt Config](https://github.com/quiltmc/quilt-config) API. Once those three items are complete, we should be ready to ship! Barring sudden disasters, of course.