Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix typo and grammar errors #764

Merged
merged 4 commits into from
Oct 31, 2023
Merged

fix typo and grammar errors #764

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
02ae083
Update README.md
VaibhavWakde52 Oct 31, 2023
8f80d24
Update task.md
VaibhavWakde52 Oct 31, 2023
4f3e9d5
Update getting-started.md
VaibhavWakde52 Oct 31, 2023
0aa15da
Apply suggestions from code review
0x2b3bfa0 Oct 31, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion docs/guides/getting-started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion docs/resources/task.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down