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 a couple of minor typos #908

Merged
merged 1 commit into from
Mar 14, 2023
Merged

Fix a couple of minor typos #908

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 doc/cloudbuild.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ See this [example change](https://github.com/AArnott/Library.Template/commit/5d1
By specifying certain `cloudBuild` options in your `version.json` file,
you can activate features for some cloud build systems, as follows:

### Automatically match cloud build numbers to to your git version
### Automatically match cloud build numbers to your git version

Cloud builds tend to associate some calendar date or monotonically increasing
build number to each build. These build numbers are not very informative, if at all.
Expand Down
2 changes: 1 addition & 1 deletion doc/nbgv-cli.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,7 +128,7 @@ By default, the `prepare-release` command writes information about created and u
Alternatively the information can be written to the output as `json`.
The output format to use can be set using the `--format` command line parameter.

For example, running the follwoing command on `master`
For example, running the following command on `master`

```
nbgv prepare-release --format json
Expand Down