diff --git a/.github/spellignore.txt b/.github/spellignore.txt
index e7949b6a..c5d64e21 100644
--- a/.github/spellignore.txt
+++ b/.github/spellignore.txt
@@ -142,6 +142,7 @@ RSE
 RSE's
 rse-specialisations
 RTPs
+scalable
 scipy
 SeniorCC
 SRU
diff --git a/competencies.md b/competencies.md
index bf171140..7e62c44d 100644
--- a/competencies.md
+++ b/competencies.md
@@ -1029,7 +1029,11 @@ Like the Data-focused RSE, they have a deep understanding of \ac{RDM} topics.
 #### Project/community manager RSEs
 
 When research software projects become larger, they need someone who manages
-processes and people. This gap can be filled by people who invest in the (\gls{PM}), (\gls{USERS}), and (\gls{TEAM}) skills, as exemplified in @subsec:examplecareer.
+processes and people.
+In practice, this concerns change management for code and documentation
+and community work to safeguard usability and adaptability,
+but also handling project governance and scalable decision-making processes.
+This gap can be filled by people who invest in the (\gls{PM}), (\gls{USERS}), and (\gls{TEAM}) skills, as exemplified in @subsec:examplecareer.
 Building a community around a research project is an
 important building block in building sustainable software [@Segal2009], so these RSEs play
 an important role, even if they do not necessarily touch much of the code themselves.
@@ -1081,12 +1085,12 @@ on the other hand knowledge about setup and configuration of particular server s
 e.g., setup of virtual machines on hypervisors or the planning and setup of compute server clusters for \ac{ML}.
 As an interface between the researchers and the infrastructure, they take care of user management, access permissions, and configuration of required services.
 
-#### Maintenance RSEs
-The constantly evolving software environment can hinder or prevent reproducibility.
-In this changing environment, a significant amount of effort in (research) software development
-needs to be spent on maintenance to ensure that software remains useful or even installable.
-With regard to which additional competency is required,
-these are people having experience with software stacks that are not part of the general curricula any more (e.g., \gls{COBOL} or \gls{Fortran}).
+#### Legacy RSEs
+Research software may be used and evolved over generations of research without change management or governance processes, while software ecosystems (e.g., programming languages, frameworks, operating systems) constantly evolve.
+This may lead to the emergence of legacy code that is actively used.
+To safeguard continued usability and adoption,
+these RSEs have experience in working with legacy code,
+and are competent in the application of software stacks that are no longer part of the general curricula (e.g., \gls{COBOL} or \gls{Fortran}).
 
 #### HPC-RSE