Clarified FEGA-CEGA comms.

docs/topics/technical-operational/index.md

@@ -44,10 +44,15 @@ It is useful to establish SOPs for common node operational tasks to enable consi
 
 Standard interactions between Central EGA and Federated EGA node Helpdesk staff have been developed into a set of SOPs. Follow these SOPs below.
 
-#### Shared FEGA<->CEGA SOPs
+#### Shared FEGA &harr; CEGA SOPs
+
+The following SOPs must be followed as part of current FEGA &harr; CEGA node interactions during the submission process:
+
 - [Federated EGA Request from submitter to submit to FEGA node](https://docs.google.com/document/d/1c5YfLqGjCmRlG0NF9lsuU6IWUrCq4u8Ug3Ye5xMrxtI/edit?usp=sharing)
 - [Federated EGA Metadata Check and Release Protocol](https://docs.google.com/document/d/1v7l_ODdh-yxyhWl8Y8R3IZC2hEy5x8KgjBQmFyEyGgw/edit?usp=sharing)
 
+Here you can find more information about [data/metadata flow within the Federated EGA network](topics/data-metadata-management/#3-understand-data-definitions-and-flow).
+
 Central EGA Helpdesk have developed a set of SOPs to harmonise both user-facing processes and internal processes. Explore some examples of these SOPs below (and organised **[here](https://drive.google.com/drive/folders/14yFvXOxRyGl-ENogIB5TdogIUdL-gmfk?usp=sharing)**). Please note these are example SOPs and will need to be adapted to how your node operates!
 
 #### Example User-facing Process SOPs