Update CONTRIBUTING.adoc

CONTRIBUTING.adoc

@@ -14,7 +14,7 @@ If you _really_ cannot use Nix and still want to contribute to Plutus then xref:
 
 === Installing and setting up Nix
 
-For instructions on how to install and configure nix (including how to enable access to our binary caches), refer to link:https://github.com/input-output-hk/iogx/blob/main/doc/nix-setup-guide.md[this document]. 
+For instructions on how to install and configure nix (including how to enable access to our binary caches), refer to link:https://github.com/input-output-hk/iogx/blob/main/doc/nix-setup-guide.md[this document].
 
 If you already have nix installed and setup, you may enter the development shell by running `nix develop`.
 
@@ -204,20 +204,20 @@ There are various tools for visualizing the resulting profile, e.g. https://hack
 We have a set of supported GHC major versions, which are built in CI and which we commit to keeping working.
 
 We also have a primary development version.
-This is the version we use in the default dev shell, and the one we use day-to-day. 
+This is the version we use in the default dev shell, and the one we use day-to-day.
 The primary development version should be whichever version the Cardano node is using (or migrating towards using).
 Supported versions older than the primary development version are deprecated, and we can drop them as soon as the Cardano node has moved to a later GHC version.
 
 At the moment, our supported GHC versions are:
 - 8.10 (deprecated)
 - 9.6 (primary)
-- 9.8 
+- 9.8
 
 === Plugin support
 
 Making `plutus-tx-plugin` work on multiple GHC versions can be painful, because it uses a lot of GHC internals.
 Since the plugin is not in the dependency closure of the Cardano node, we don't _need_ to support all the GHC versions, which is helpful.
-We mostly commit to supporting our primary development version, but we _may_ support other versions as well if it is easy. 
+We mostly commit to supporting our primary development version, but we _may_ support other versions as well if it is easy.
 
 The plugin and its dependents should be marked as unbuildable with cabal conditionals on any non-supported major GHC versions.
 This makes cabal behave reasonably well (it will ignore them and not try and fail to build them).
@@ -650,14 +650,13 @@ These perform some of the same checks as Hydra, but Github Actions is often more
 == Project roles and responsibilities
 
 - The regular contributors to the Haskell code, all of whom can review and merge PRs are:
-    - @michaelpj
+    - @ana-pantilie
+    - @bezirg
     - @effectfully
     - @kwxm
-    - @bezirg
-    - @thealmarty
+    - @Unisay
     - @zliu41
-- The maintainer of the documentation is @joseph-fajen.
 - The maintainer of the Agda code is @jmchapman, @effectfully can help with small issues.
-- If you have a technical dispute that you need help resolving, you can ask @michaelpj.
-- For problems with the developer environment setup, builds, or CI, you can ask @zeme-iohk, @Pacman99, or @michaelpj.
-- The regular contributors take turns releasing our software, but if you have a specific problem ask @zliu41 or @michaelpj.
+- If you have a technical dispute that you need help resolving, you can ask @zliu41.
+- For problems with the developer environment setup, builds, or CI, you can ask @zeme-iohk or @zliu41.
+- The regular contributors take turns releasing our software, but if you have a specific problem ask @zliu41.