diff --git a/_sips/process-specification.md b/_sips/process-specification.md
index 39d357f74..e69e169a2 100644
--- a/_sips/process-specification.md
+++ b/_sips/process-specification.md
@@ -49,7 +49,7 @@ from an idea to the inclusion in the language.
   review in detail a particular SIP. The same person cannot be both a SIP Author
   and a SIP Reviewer for the same SIP.
 - SIP Manager: one of the SIP Reviewers who is responsible for the all the
-  communications related to the SIP, throughout its entire life-cycle. This includes requesting a vote on the SIP from the whole Committee, presenting the SIP to the Committee at the plenary meetings, merging or closing the corresponding PR, reporting to the community and tooling ecosystem on the vote outcome, and announcing when it is available for testing.
+  communications related to the SIP, throughout its entire life-cycle. This includes requesting a vote on the SIP from the whole Committee, presenting the SIP to the Committee at the plenary meetings, merging or closing the corresponding PR, reporting to the community on the vote outcome, and announcing when it is available for testing.
 
 ## Stages
 
@@ -223,7 +223,7 @@ to the Scala 3 compiler repository. There is no set timeline for this phase.
 
 Often, proposals not only need to be implemented in the compiler, but also in
 several other tools (IDEs, syntax highlighters, code formatters, etc.). As soon
-as a proposal reaches the implementation stage, its Manager notifies the
+as a proposal reaches the implementation stage, the Chairperson notifies the
 impacted tools that they should start implementing support for it. A list of
 tools of the ecosystem is maintained in [this document][tooling ecosystem].