commit 7843e456395d8e283ad29f06d132fdb2b5774b12
parent 87a196d720a9cc04902fd14f448ef8d569a85234
Author: kst
Date: 2020-07-18 05:31Z
tutorial: fix typos
Diffstat:
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/TUTORIAL b/TUTORIAL
@@ -14,7 +14,7 @@ servers with minor modifications.
tl;dr
-----
-If you are not interested in the details, I wrote a minimal frontend called
+If you are not interested in the details, I wrote a minimal front-end called
"git repo manager" [2]. It should take care of all the details for you.
creating a repo
@@ -58,7 +58,7 @@ The
$ git update-server-info
command needs to be run after every update to the repository. This could be
-automated using the post-update githook [5]. Since the sample post-update hook
+automated using the post-update git hook [5]. Since the sample post-update hook
in
~/public_html/my_repo.git/hooks
@@ -97,7 +97,7 @@ using
if you have a correct SSH keypair setup.
-web frontend
+web front-end
------------
Now that we have already figured out the push and clone access of our
@@ -192,18 +192,18 @@ Now you should see something like this when you do a git push
remote: [my_repo] stagit HTML pages... done!
...
-a minimal frontend
+a minimal front-end
------------------
Since the process of creating repositories and recompiling stagit pages can be
-very tedious, I wrote up a simple frontend called git repo manager (grm) to
+very tedious, I wrote up a simple front-end called git repo manager (grm) to
deal with the chore, see the readme [9] if you want to use grm to automate this
process.
If you want to host git repositories on your own server, you could use the git
daemon [10] to better manage the visibility of your repositories. The remote
-address exposed by the git daemon will have git:// prefix. Check out the the
-master branch of grm [11] if you want to use git daemon instead.
+address exposed by the git daemon will have git:// prefix. Check out the master
+branch of grm [11] if you want to use git daemon instead.
accepting patches
-----------------
@@ -211,7 +211,7 @@ accepting patches
Hosting git repositories this way means there will be no fancy features such as
issues and pull requests, but git have built-in support for email workflows [12].
-Other people could format their commits to patches using
+Contributors could format their commits to patches using
$ git format-patch
