fix pre-commit issues

Author: Umair Ayub

docs/safe-haven-services/tre-gpu-service/faq.md

@@ -26,6 +26,7 @@ The service provides a **BeeGFS CSI driver** provisioner, which allows for `Read
 ## How many GPUs can I use in a pod?
 
 The maximum number of GPUs you can request per pod is limited by both the node capacity and your project quota.
+
 - Each node has 8 GPUs, so technically a pod could use up to 8 GPUs if available.
 - However, your project quota may be lower. For example, if your project is allocated 4 GPUs, the maximum a single pod can request is 4 GPUs.
 

docs/safe-haven-services/tre-gpu-service/policies.md

@@ -19,7 +19,7 @@ Submitting jobs with `name` only would allow several jobs to have the same name,
 
 ## Kubernetes Job Time to Live
 
-All completed Kubernetes jobs will have a Time to Live (TTL) applied via `spec.ttlSecondsAfterFinished` automatically. A completed job (in success or error state) will be deleted from the service once this period has elapsed since execution has completed. This will reduce excessive object accumulation on the service. The default TTL for jobs using the service is one week (604800 seconds). 
+All completed Kubernetes jobs will have a Time to Live (TTL) applied via `spec.ttlSecondsAfterFinished` automatically. A completed job (in success or error state) will be deleted from the service once this period has elapsed since execution has completed. This will reduce excessive object accumulation on the service. The default TTL for jobs using the service is one week (604800 seconds).
 
 !!! important
     This policy is automated and does not require users to change their job specifications.
@@ -29,7 +29,7 @@ All completed Kubernetes jobs will have a Time to Live (TTL) applied via `spec.t
 
 ## Kubernetes Active Deadline Seconds
 
-All Kubernetes user pods submitted to the service will have an Active Deadline Seconds (ADS) applied via `spec.spec.activeDeadlineSeconds` automatically. A pod will be terminated once this period has elapsed after execution has begun. This will reduce the number of unused pods remaining on the service. The default ADS for pods using the service is five days (432000 seconds). 
+All Kubernetes user pods submitted to the service will have an Active Deadline Seconds (ADS) applied via `spec.spec.activeDeadlineSeconds` automatically. A pod will be terminated once this period has elapsed after execution has begun. This will reduce the number of unused pods remaining on the service. The default ADS for pods using the service is five days (432000 seconds).
 
 !!! important
     This policy is automated and does not require users to change their job or pod specifications.

docs/safe-haven-services/tre-gpu-service/training/L1.1_building-and-testing-containers.md

@@ -73,4 +73,4 @@ The security posture of containers and the build process may be of interest to I
 
 Trivy can be run manually on the built image but it is easier to have it run automatically whenever you update your container image. An example GitHub Actions workflow to run Trivy and publish the outputs can be found [in our documentation](https://github.com/EPCCed/tre-container-samples/blob/main/.github/workflows/main.yaml).
 
-The Trivy report can be downloaded as an artefact from the job summary page. 
+The Trivy report can be downloaded as an artefact from the job summary page.

docs/safe-haven-services/tre-gpu-service/training/L3_Accessing_the_BeeGFS_Inside_the_EPCC_TRE.md

@@ -8,7 +8,12 @@ This approach ensures secure, performant, and flexible access to shared datasets
 
 ### Key Point
 
-`BeeGFS is deployed within the SHS. Therefore, the same restrictions apply: BeeGFS storage is fully isolated from the internet. You cannot download data directly from public sources (e.g., GitHub, external APIs), and copying, recording, or extracting any files from BeeGFS outside of the SHS is strictly prohibited unless explicitly approved through the appropriate Information Governance processes. It is also prohibited to use the BeeGFS to share data with other users or with projects to which you have access.`
+`BeeGFS is deployed within the SHS. Therefore, the same restrictions apply: BeeGFS storage is
+fully isolated from the internet. You cannot download data directly from public sources
+(e.g., GitHub, external APIs), and copying, recording, or extracting any files from BeeGFS
+outside of the SHS is strictly prohibited unless explicitly approved through the appropriate
+Information Governance processes. It is also prohibited to use the BeeGFS to share data with
+other users or with projects to which you have access.`
 
 ### Storage Overview