Terminology (#6)

* minor entrust terminology updates

* terminology updates to better align with ENTRUST Blueprint

Author: beforan

app/d20.2/audience/page.mdx

@@ -1,23 +1,23 @@
 # Training Package Audience
 
-As described in the [overview](/d20.2), this training package has been developed primarily with **TRE Administrators** in mind.
+As described in the [overview](/d20.2), this training package has been developed primarily with **TRE Operators** in mind.
 
 However, there are adjacent audiences for whom some of the referenced material is relevant, discussed below.
 
-Since this resource presents its content through a lens for TRE Administrators, there is also value in clarifying the roles considered to be performed within the label of "TRE Administrator".
+Since this resource presents its content through a lens for TRE Operators, there is also value in clarifying the roles considered to be performed within the label of "TRE Operator".
 
 ## Relevant audiences
 
-- **Federation Administrators**, people responsible for co-ordinating a Federation of TREs
+- **Federation Operators**, people responsible for co-ordinating a Federation of TREs
   - For the purposes of this training package, this would include managing the configuration of Projects and their TRE and User memberships in a Federation-centralised Submission Service
-  - This role may be performed by a TRE Administrator, e.g. within the "Front Door" TRE of a Federation, and as such is within the scope of this training package for TRE Administrators.
-- **TRE Administrators**, people responsible for managing and operating a TRE.
+  - This role may be performed by a TRE Operator, e.g. within the "Front Door" TRE of a Federation, and as such is within the scope of this training package for TRE Operators.
+- **TRE Operators**, people responsible for managing and operating a TRE.
   - The material covers different aspects of TRE Administration that may be handled by different roles:
     - **Installers**, responsible for deploying and configuring the technical infrastructure and tools
     - **Administrators**, responsible for managing projects within the TRE
       - In the context of this training package and Five Safes TES, TRE Administrators will interact with the deployed tooling
-    - **Egress Officers**, responsible for approving or rejecting project outputs for egress from the TRE.
+    - **Output Controllers**, responsible for approving or rejecting project outputs for egress from the TRE.
 - **Researchers**, people who want to submit analyses to TREs within a Federation in which they are an approved member of a Project, using this tooling.
-  - This training package does not focus on this audience, however some Researcher activities are described within the material, to provide TRE Administrators with context and understanding of the process from a Researcher's perspective:
+  - This training package does not focus on this audience, however some Researcher activities are described within the material, to provide TRE Operators with context and understanding of the process from a Researcher's perspective:
     - How to submit and run analyses
     - How to retrieve approved outputs.

app/d20.2/concepts/page.mdx

@@ -9,7 +9,7 @@ import {
 
 # Concepts & Standards
 
-There are a number of concepts and standards that TRE Administrators should be familiar with in the context of Federated Workflow Processing.
+There are a number of concepts and standards that TRE Operators should be familiar with in the context of Federated Workflow Processing.
 
 ## Concepts
 

app/d20.2/five-safes-tes/project-setup/page.mdx

@@ -7,11 +7,11 @@ import { ChevronRightCircleIcon } from "lucide-react";
 
 A number of steps are required to set up a Five Safes TES Project in the Federation
 
-1. A **Federation Administrator** adds a Project to the **Submission Layer**, along with Users and TREs who are members of the Project.
+1. A **Federation Operator** adds a Project to the **Submission Layer**, along with Users and TREs who are members of the Project.
    - These member TREs and Users are unconfirmed at this stage.
-1. A **TRE Administrator** for each TRE needs to connect their **TRE Agent** to the **Submission Layer**.
+1. A **TRE Operator** for each TRE needs to connect their **TRE Agent** to the **Submission Layer**.
    - Each connected TRE's **Agent** synchronises with the **Submission Layer**, pulling down its list of Member Projects and their Users.
-1. A **TRE Administrator**, for each TRE, uses the **Agent** to register their approval (or not) of each Project relevant to them, as well as each Project's individual User memberships.
+1. A **TRE Operator**, for each TRE, uses the **Agent** to register their approval (or not) of each Project relevant to them, as well as each Project's individual User memberships.
    - Only when a TRE has confirmed involvement in a Project will they receive submissions for that Project
    - Only Users approved by a TRE for a Project will be allowed to make submissions for that Project to that TRE.
    - TRE's may withdraw (or reinstate) individual User or Project approvals at any time.
@@ -30,7 +30,7 @@ Additional guidance from the documentation is provided below, under each relevan
 <Steps>
 ### Submission Project Setup
 
-Here, a **Federation Administrator** sets up the **Project** in the **Submission Layer**.
+Here, a **Federation Operator** sets up the **Project** in the **Submission Layer**.
 
 > [!NOTE]
 >
@@ -74,7 +74,7 @@ There are also guides for adding additional Users to an existing Project:
 
 ### TRE Agent Connection
 
-A **TRE Administrator** for each TRE needs to connect their **TRE Agent** to the **Submission Layer**.
+A **TRE Operator** for each TRE needs to connect their **TRE Agent** to the **Submission Layer**.
 
 The following guide covers both the Submission Layer and TRE Agent sides of this process:
 
@@ -93,7 +93,7 @@ It also covers how to add a TRE to an existing Project in the Submission Layer.
 
 ### TRE Project and User Approval
 
-A **TRE Administrator**, for each TRE, uses the **Agent** to register their approval (or not) of each Project relevant to them, as well as each Project's individual User memberships.
+A **TRE Operator**, for each TRE, uses the **Agent** to register their approval (or not) of each Project relevant to them, as well as each Project's individual User memberships.
 
 <Cards.Card
   className="mt-2"

app/d20.2/page.mdx

@@ -1,6 +1,6 @@
 # Overview
 
-Welcome to this online resource, which aims to provide training material for **TRE Administrators**, around **Federated Workflow Processing**.
+Welcome to this online resource, which aims to provide training material for **TRE Operators**, around **Federated Workflow Processing**.
 
 ---
 
@@ -21,7 +21,7 @@ This page gives an overview of the material as a project deliverable for [EOSC-E
 This resource forms the EOSC-ENTRUST **First Training Package** for **Digital Objects and Workflows**, which is a project deliverable for EOSC-ENTRUST [**Work Package 20**](#wp20).
 
 The deliverable (D20.2) is described by the project as "An online resource explaining how to deploy workflows via the new TRE tooling",
-and as such is provided as a website primarily targeting TRE Administrators in order for them to understand the "new TRE tooling" (Five Safes TES), along with how to deploy it, how to deploy workflows on it, and what analyses can reasonably be deployed.
+and as such is provided as a website primarily targeting TRE Operators in order for them to understand the "new TRE tooling" (Five Safes TES), along with how to deploy it, how to deploy workflows on it, and what analyses can reasonably be deployed.
 
 There is an accompanying deliverable document which gives further context to the material herein, as well as its development, which will be linked once published.