Fix typos

Author: MattiSG

content/deployment/reference/server-specifications.md

@@ -15,9 +15,9 @@ Approximately 750 MB of storage is required for the engine itself, with the rem
 
 ## Storage
 
-Recommended storage: 10 GB, with resizable partitioning to enable growth over time.
+Recommended storage: 10 GB, with resizeable partitioning to enable growth over time.
 
-Storage usage typically grows at a rate of 0.5 MB per tracked terms per month on average for latin scripts. This growth rate varies depending on the type of service being tracked:
+Storage usage typically grows at a rate of 0.5 MB per tracked terms per month on average for Latin scripts. This growth rate varies depending on the type of service being tracked:
 
 - Services with large legal teams and heavy website layouts: ~1 MB per terms per month
 - Smaller services: ~0.1-0.3 MB per terms per month

content/federation/reference/criteria.md

@@ -15,7 +15,7 @@ A **collection** can **join** the Open Terms Archive **federation** if it abides
 6. Public and open-licensed **snapshots**, as evidenced by the `LICENSE` file in the snapshots repository.
 7. Public and open-licensed **versions**, as evidenced by the `LICENSE` file in the versions repository.
 8. Regular, public, and open-licensed **dataset** releases, as evidenced by the `LICENSE` file in the datasets.
-9. Publicly accessible API with median response time under 20ms, as evidenced by uptime tracking logs.
+9. Publicly accessible API with median response time under 20 ms, as evidenced by uptime tracking logs.
 10. Abide by all Open Terms Archive software and data licenses.
 
 For detailed instructions on joining the federation, refer to the [How to Join the Federation guide]({{< relref "federation/how-to/join" >}}).

content/terms/how-to/terminate-a-service.md

@@ -6,7 +6,7 @@ weight: 6
 
 # How to terminate a service
 
-If the service provider stops offering a service, the associated terms will become unavailable. To mark that service termination in Open Terms Archive and ensure tracking tentatives are stopped, while maintaining the possibility to explore the history:
+If the service provider stops offering a service, the associated terms will become unavailable. To mark that service termination in Open Terms Archive and ensure tracking attempts are stopped, while maintaining the possibility to explore the history:
 
 1. Move the existing terms declaration to the service [history file](#terms-declaration-history).
 2. Update the declaration to stop tracking all terms, by removing every `<terms type>` entries from the  `terms` key in the declaration: