Make pre-commit happy

Author: myurasov-nv

cloudci/CLOUDCI.md

@@ -5,7 +5,7 @@
 Upon looking at the current CI setup and challenges, it seems that adding a cloud-based CI, could help with: Os
 
 - Faster turnaround times on MRs due to ability to scale up and down as needed
-- Testing on a variety of GPUs, inluding ones, users are likely to run on (Isaac Lab is often used in the cloud) - A10G, L4, L40, T4, etc.
+- Testing on a variety of GPUs, including ones, users are likely to run on (Isaac Lab is often used in the cloud) - A10G, L4, L40, T4, etc.
 - Cost effectiveness (more on that below)
 
 Initially, it can be implemented on AWS (A10G, L4, L40S, T4, H100, B100, GB200), and later expanded to GCP (T4, L4, RTX PRO 6000, B200, GB200) and Azure (A10,, H100) as needed.
@@ -30,7 +30,7 @@ Those costs are charged only if the instance is running. If it is stopped, only
 
 ## Architecture
 
-Cloud CI setup will be very loosely based on the Isaac Automator (https://github.com/NVIDIA-Omniverse/IsaacAutomator), but will be simplified to avoid the need to support any unneded functionality.
+Cloud CI setup will be very loosely based on the Isaac Automator (https://github.com/NVIDIA-Omniverse/IsaacAutomator), but will be simplified to avoid the need to support any unneeded functionality.
 
 There will be 3 main components:
 
@@ -61,4 +61,4 @@ Since this can be based on existing Isaac Automator code, the timeline can be re
 |--------------------|----------|-----------------------------------------|
 | Prototype          | 2 weeks  | Cloud CI workflow working "somehow"  |
 | Testing & Polishing| 2 weeks  | Other members of Isaac Arena team are happy with it         |
-| Final Integration  | 1 week   | MR is merged and CI is run (as neede or regularly) usinng the cloud CI tools |
+| Final Integration  | 1 week   | MR is merged and CI is run (as needed or regularly) using the cloud CI tools |