Skip to content

Commit

Permalink
Correct some small README.md formatting typos (#213)
Browse files Browse the repository at this point in the history
  • Loading branch information
magnetikonline authored Apr 1, 2022
1 parent dcb4ec9 commit bf7ccf1
Showing 1 changed file with 10 additions and 8 deletions.
18 changes: 10 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,7 @@ steps:
```
Matching an unstable pre-release:
```yaml
steps:
- uses: actions/checkout@v3
Expand All @@ -62,7 +63,7 @@ steps:
See [action.yml](action.yml)
## Basic:
## Basic
```yaml
steps:
Expand All @@ -74,7 +75,7 @@ steps:
```
## Check latest version:
## Check latest version
The `check-latest` flag defaults to `false`. Use the default or set `check-latest` to `false` if you prefer stability and if you want to ensure a specific Go version is always used.

Expand All @@ -92,7 +93,7 @@ steps:
- run: go run hello.go
```

## Matrix Testing:
## Matrix testing

```yaml
jobs:
Expand All @@ -115,18 +116,19 @@ jobs:

The `go-version` input supports the following syntax:

Specific versions: `1.15`, `1.16.1`, `1.17.0-rc.2`, `1.16.0-beta.1`
SemVer's version range syntax: `^1.13.1`, `>=1.18.0-rc.1`
For more information about semantic versioning please refer [semver](https://github.com/npm/node-semver) documentation
- Specific versions: `1.15`, `1.16.1`, `1.17.0-rc.2`, `1.16.0-beta.1`
- SemVer's version range syntax: `^1.13.1`, `>=1.18.0-rc.1`

For more information about semantic versioning, please refer to [semver](https://github.com/npm/node-semver) documentation.

# License

The scripts and documentation in this project are released under the [MIT License](LICENSE)

# Contributions

Contributions are welcome! See [Contributor's Guide](docs/contributors.md)
Contributions are welcome! See [Contributor's Guide](docs/contributors.md)

## Code of Conduct

:wave: Be nice. See [our code of conduct](CONDUCT)
:wave: Be nice. See [our code of conduct](CONDUCT)

0 comments on commit bf7ccf1

Please sign in to comment.