Commit 20a06798 authored by Mark Pundsack's avatar Mark Pundsack

Tweak grammar

parent 00906b5b
...@@ -167,7 +167,7 @@ There are also two edge cases worth mentioning: ...@@ -167,7 +167,7 @@ There are also two edge cases worth mentioning:
1. If no `stages` is defined in `.gitlab-ci.yml`, then by default the `build`, 1. If no `stages` is defined in `.gitlab-ci.yml`, then by default the `build`,
`test` and `deploy` are allowed to be used as job's stage by default. `test` and `deploy` are allowed to be used as job's stage by default.
2. If a job doesn't specify `stage`, the job is assigned the `test` stage. 2. If a job doesn't specify a `stage`, the job is assigned the `test` stage.
### types ### types
...@@ -178,9 +178,9 @@ Alias for [stages](#stages). ...@@ -178,9 +178,9 @@ Alias for [stages](#stages).
>**Note:** >**Note:**
Introduced in GitLab Runner v0.5.0. Introduced in GitLab Runner v0.5.0.
GitLab CI allows you to add to `.gitlab-ci.yml` variables that are set in build GitLab CI allows you to add variables to `.gitlab-ci.yml` that are set in the
environment. The variables are stored in the git repository and are meant to build environment. The variables are stored in the git repository and are meant
store non-sensitive project configuration, for example: to store non-sensitive project configuration, for example:
```yaml ```yaml
variables: variables:
...@@ -253,8 +253,8 @@ rspec: ...@@ -253,8 +253,8 @@ rspec:
- binaries/ - binaries/
``` ```
The cache is provided on best effort basis, so don't expect that cache will be The cache is provided on a best-effort basis, so don't expect that the cache
always present. For implementation details please check GitLab Runner. will be always present. For implementation details, please check GitLab Runner.
#### cache:key #### cache:key
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment