From 8766d1a8d0bb090822c413c017b90d07133e2013 Mon Sep 17 00:00:00 2001 From: Meghan Denny Date: Wed, 25 Aug 2021 16:21:32 -0700 Subject: [PATCH] docs/tutorial- fix typos --- docs/tutorial.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tutorial.md b/docs/tutorial.md index 55de8c784373cca283f5bc3e4b87c5abf4139b0a..5449fdd8479978af7d7bcf722d8c95a646276242 100644 --- a/docs/tutorial.md +++ b/docs/tutorial.md @@ -88,7 +88,7 @@ pub fn build(b: *Builder) void { ``` --- -## Contributing to dependency upstream\ +## Contributing to dependency upstream When 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. Suppose 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 Then 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`. -Then push your local changes with `git push origin master` and create your pull request. +Then push your local changes with `git push fork master` and create your pull request. --- ## Using Zigmod in Github Actions -- 2.54.0