fix typo and grammar errors (#764)

* Update README.md

* Update task.md

* Update getting-started.md

* Apply suggestions from code review

---------

Co-authored-by: Helio Machado <[email protected]>

Author: VaibhavWakde52

README.md

@@ -35,7 +35,7 @@ Supported cloud vendors [include][auth]:
 
 ## Why TPI?
 
-There are a several reasons to use TPI instead of other related solutions (custom scripts and/or cloud orchestrators):
+There are several reasons to use TPI instead of other related solutions (custom scripts and/or cloud orchestrators):
 
 1. **Reduced management overhead and infrastructure cost**:
    TPI is a CLI tool, not a running service. It requires no additional orchestrating machine (control plane/head nodes) to schedule/recover/terminate instances. Instead, TPI runs (spot) instances via cloud-native scaling groups[^scalers], taking care of recovery and termination automatically on the cloud provider's side. This design reduces management overhead & infrastructure costs. You can close your laptop while cloud tasks are running -- auto-recovery happens even if you are offline.

docs/guides/getting-started.md

@@ -105,7 +105,7 @@ With spot/preemptible instances (`spot >= 0`), auto-recovery logic and persisten
 
 -> **Note:** A large `workdir` may take a long time to upload.
 
-~> **Warning:** To take full advantage of spot instance recovery, a `script` should start by cheching the disk for results (recovered from a previous interrupted run).
+~> **Warning:** To take full advantage of spot instance recovery, a `script` should start by checking the disk for results (recovered from a previous interrupted run).
 
 -> **Note:** The [`id`](https://registry.terraform.io/providers/iterative/iterative/latest/docs/resources/task#id) returned by `terraform apply` (i.e. `[id=tpi-···]`) can be used to locate the created cloud resources through the cloud's web console or command–line tool.
 

docs/resources/task.md

@@ -325,7 +325,7 @@ resource "iterative_task" "example" {
 ```
 
 The container name may include a path component, in this case the specified subdirectory will be used
-to store task execution results. Otherwise, a subdirectory will be created with a name matchin the
+to store task execution results. Otherwise, a subdirectory will be created with a name matching the
 task's randomly generated id.
 
 If the container name is suffixed with a forward slash, (`container-name/`), the root of the container