Merge pull request #58 from nivenly/Nov-updates-clarification

Added a quick clarification

content/en/blog/2023/2023-11-14-updates.md

@@ -102,7 +102,7 @@ Nivenly has received a project application from Pachli, a fork of the Tusky Andr
 
 Pachli’s complete application is visible [here](https://nivenly.org/docs/applications/pachli/). We’re sure both members and non-members have questions about Pachli! For members, since your questions are part of the governance process please put your questions [in the member only area of our Discourse](https://nivenly.discourse.group/c/nivenly-community/5). For non-members, please feel free to ask questions as well in [our Discourse’s public area](https://nivenly.discourse.group/c/nivenly-projects/7). To help us, and the head maintainer of the project, keep track of the question threads we’ve created both of the members-only and general public threads to kick off the discussions.
 ### FIRES (formerly known as FFS)
-Nivenly is also sponsoring Fediverse Intelligence Recommendations & Replication Endpoint Server (FIRES), which is led and being built by Emelia Smith ([@thisismissem](https://hachyderm.io/@thisismissem)). For those who have been following her work, this is a rename of the same project formerly referred to as Fediverse Filter Server (FFS). Nivenly’s support for FIRES is two fold: both the initial technical proposal as well as the initial reference implementation. (Updated to add: we've been asked a couple of times if FIRES is the same project as FSEP. These are independent projects with separate maintainers that operate in the same space. To borrow from a familiar concept, this is no different than the Ghost and Wordpress blogging platforms. Both are in the same space, blogging, but are completely separate projects run by different people.)
+Nivenly is also sponsoring Fediverse Intelligence Recommendations & Replication Endpoint Server (FIRES), which is led and being built by Emelia Smith ([@thisismissem](https://hachyderm.io/@thisismissem)). For those who have been following her work, this is a rename of the same project formerly referred to as Fediverse Filter Server (FFS). Nivenly’s support for FIRES is two fold: both the initial technical proposal as well as the initial reference implementation. (Updated to add: we've been asked a couple of times if FIRES is the same project as FSEP. These are independent projects with separate maintainers that operate in the same space. To borrow from a familiar concept, this is no different than the Ghost and Wordpress blogging platforms. Both are in the same space, blogging, but are completely separate projects run by different people.) 
 
 First: what is FIRES? FIRES is in part a response to feedback that there needed to be more nuance in moderation than simply allow and deny lists. Instead, the primary goal of FIRES is to provide the ability to subscribe to moderation advisories and recommendations that change over time. The moderation data will also be structured instead of unstructured - basically instead of a single text field, as is the experience today, the data will be highly structured and capture the full history of changes to moderation recommendations and advisories. This allows machines to better interact with the data of moderation recommendations and advisories, such that tools and user interfaces can be built to expose more data to moderators and end users alike.