authorgravatar for hello@nektro.netMeghan Denny <hello@nektro.net> 2021-08-25 16:21:32 -07:00
committergravatar for hello@nektro.netMeghan Denny <hello@nektro.net> 2021-08-25 16:21:32 -07:00
log8766d1a8d0bb090822c413c017b90d07133e2013
treed684273865a72bffcb7090f5dcad5c52db17d0e0
parentb852cb0b8aff7bf346c2dad8979cd112140c7fcc

docs/tutorial- fix typos

1 files changed, 2 insertions(+), 2 deletions(-)

docs/tutorial.md+2-2
......@@ -88,7 +88,7 @@ pub fn build(b: *Builder) void {
8888```
8989
9090---
91## Contributing to dependency upstream\
91## Contributing to dependency upstream
9292When using Git dependencies, Zigmod streamlines the process of contributing back fixes and improvements to your upstream. This is due to the fact that Zigmod will preserve the `.git` folder when cloning so that you may work with it.
9393
9494Suppose we have the package https://github.com/octocat/zig-hello.
......@@ -97,7 +97,7 @@ Zigmod will `git clone` its contents to `.zigmod/deps/git/github.com/octocat/zig
9797
9898Then fork the repository on `github.com` or wherever it is hosted and add a local remote so that you have something to push to. `git remote add fork https://github.com/you/zig-hello`.
9999
100Then push your local changes with `git push origin master` and create your pull request.
100Then push your local changes with `git push fork master` and create your pull request.
101101
102102---
103103## Using Zigmod in Github Actions