aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Muré <batolettre@gmail.com>2019-12-27 20:12:11 +0100
committerMichael Muré <batolettre@gmail.com>2020-03-01 12:47:47 +0100
commit710d85664e6cf933d2b1691871a4246b8e7eceb3 (patch)
tree83bc003dbbeb457f3576d41fa0efb6fb2bffdf58
parent19f3c214288647b61bc730bb0b1d400fc59c74b0 (diff)
downloadgit-bug-710d85664e6cf933d2b1691871a4246b8e7eceb3.tar.gz
doc: fix typos
-rw-r--r--doc/howto-github.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/howto-github.md b/doc/howto-github.md
index cd1855b0..44f24927 100644
--- a/doc/howto-github.md
+++ b/doc/howto-github.md
@@ -18,7 +18,7 @@ Check that `git-bug` is properly installed by running `git bug version`. If ever
## Configuration
-1. From within the git repository you care about, run `git bug bridge configure` and follow the wizard's steps:
+1. From within the git repository you care about, run `git bug bridge configure` and follow the wizard's steps:
1. Choose `github`.
1. Type a name for the bridge configuration. As you can configure multiple bridges, this name will allow you to choose when there is an ambiguity.
1. Setup the remote Github project. The wizard is smart enough to inspect the git remote and detect the potential project. Otherwise, enter the project URL like this: `https://github.com/MichaelMure/git-bug`
@@ -56,6 +56,6 @@ The command line tools are really meant for programmatic usage or to integrate `
![termui recording](../misc/termui_recording.gif)
-For a richer UI more user friendly UI, `git-bug` propose a web UI (read-only at the moment). You can start it with `git bug webui`:
+For a richer and more user friendly UI, `git-bug` proposes a web UI (read-only at the moment). You can start it with `git bug webui`:
![web UI screenshot](../misc/webui2.png)