Skip to content

Commit 03819d6

Browse files
d-ornenmarkcda
authored andcommitted
grammar, style fixes
fix doc
1 parent 371c3ba commit 03819d6

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
# deployer
22

3-
Deployer is a relative simple, yet powerful localhost CI/CD instrument. It allows you to:
3+
Deployer is a relatively simple, yet powerful localhost CI/CD instrument. It allows you to:
44

55
- have your own actions and pipelines repositories (`Actions Registry` and `Pipelines Registry`) in a single JSON file
66
- create actions and pipelines from TUI or using JSON/YAML/TOML configuration files
77
- configure actions for specific project
88
- satisfy requirements for your system to run pipelines
99
- check compatibility over actions and projects
10-
- run actions and pipelines at remote hosts (you need to setup your remote with SSH key and install `deployer`)
10+
- run actions and pipelines on remote hosts (you need to setup your remote access using SSH key, also you need to install `deployer` on remote host)
1111
- use variables for commands from `env`-files and HashiCorp Vault KV2-storage
1212
- run pipelines with different cache requirements in different build folders
13-
- run pipelines inside containered environments (Docker by default) with cache strategies
13+
- run pipelines inside containerized environments (Docker by default) with cache strategies
1414
- store common content in Deployer's storage, add and patch additional files for build on the fly
1515
- and share your project build/deploy settings very quickly and without any dependencies.
1616

@@ -43,7 +43,7 @@ That's it! Now you have `/home/username/.cargo/bin/deployer` binary. Modify the
4343

4444
## Usage
4545

46-
All project configuration store in `deploy-config.json` or `.deploy-config.json` file.
46+
All project configuration is stored in `deploy-config.json` or `.deploy-config.json` file.
4747

4848
First of all, let's create a simple action.
4949

@@ -92,7 +92,7 @@ The full JSON is:
9292
}
9393
```
9494

95-
If you're interesting in UPX, consider to visit it [home page](https://upx.github.io/).
95+
If you're not familiar with UPX, consider visiting it's [home page](https://upx.github.io/).
9696

9797
So, let's create a pipeline that will build the binary from the Rust code with preinstalled `cargo-rel@0.1` action and then compress this binary with `upx-compress@0.1.0`.
9898

@@ -233,7 +233,7 @@ deployer init
233233
deployer with rust-default@0.1.0
234234
```
235235

236-
Deployer will consider you to specify some things (e.g., targets - for this project and `rust-default@0.1.0` Pipeline it will be `target/release/deployer`). After all you will get this `deploy-config.json`:
236+
Deployer will ask you to specify some things (e.g., targets - for this project and `rust-default@0.1.0` Pipeline it will be `target/release/deployer`). After all you will get this `deploy-config.json`:
237237

238238
```json
239239
{

0 commit comments

Comments
 (0)