Formatting fixes

Co-authored-by: Matt Craddock <[email protected]>

Author: manics

docs/source/specification.md

@@ -4,8 +4,8 @@
 
 The specification is presented in terms of the capabilities that a team running a TRE should aim for across all aspects of TRE provision.
 
-This page explains what the specification is and how it’s structured. 
-It also describes how the importance of components is categorised. 
+This page explains what the specification is and how it’s structured.
+It also describes how the importance of components is categorised.
 Consult the {ref}`FAQs <faqs>` for more on what the specification _is not_.
 
 :::{note}
@@ -81,9 +81,9 @@ Any particular TRE implementation should be able to {ref}`score itself against e
 
 ## Roles
 
-A TRE needs to consider many different stakeholders. 
-SATRE provides specific roles which may or may not match titles used in your organisation. 
-However each of these are important to the successful operation of a TRE. 
+A TRE needs to consider many different stakeholders.
+SATRE provides specific roles which may or may not match titles used in your organisation.
+However each of these are important to the successful operation of a TRE.
 Roles are grouped into:
 
 {ref}`1. Project Roles <project_roles>`
@@ -99,4 +99,4 @@ Roles are grouped into:
 : Roles that uphold the governance of TREs. Such governance responsibilities typically involve establishing policies and procedures to ensure the responsible use of data, protecting the privacy and confidentiality of research participants, and promoting transparency and accountability in research activities.
 
 {ref}`5. Public Roles <public_roles>`
-: Roles that concern members of the public with regard to TREs and TRE research.
+: Roles that concern members of the public with regard to TREs and TRE research.