Skip to content

Commit 7a3f17f

Browse files
author
Dmitri Tikhonov
committed
Fixed typo: "walk through," not "walk though."
1 parent 5c7a9a3 commit 7a3f17f

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

book/04-git-server/sections/gitweb.asc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ $ git instaweb --httpd=webrick --stop
3131

3232
If you want to run the web interface on a server all the time for your team or for an open source project you're hosting, you'll need to set up the CGI script to be served by your normal web server.
3333
Some Linux distributions have a `gitweb` package that you may be able to install via `apt` or `yum`, so you may want to try that first.
34-
We'll walk though installing GitWeb manually very quickly.
34+
We'll walk through installing GitWeb manually very quickly.
3535
First, you need to get the Git source code, which GitWeb comes with, and generate the custom CGI script:
3636

3737
[source,console]

book/04-git-server/sections/smart-http.asc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Setting up Smart HTTP is basically just enabling a CGI script that is provided w
66
This CGI will read the path and headers sent by a `git fetch` or `git push` to an HTTP URL and determine if the client can communicate over HTTP (which is true for any client since version 1.6.6).
77
If the CGI sees that the client is smart, it will communicate smartly with it, otherwise it will fall back to the dumb behavior (so it is backward compatible for reads with older clients).
88

9-
Let's walk though a very basic setup. We'll set this up with Apache as the CGI server. If you don't have Apache setup, you can do so on a Linux box with something like this:(((Apache)))
9+
Let's walk through a very basic setup. We'll set this up with Apache as the CGI server. If you don't have Apache setup, you can do so on a Linux box with something like this:(((Apache)))
1010

1111
[source,console]
1212
----

book/07-git-tools/sections/submodules.asc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -199,7 +199,7 @@ Now we have a copy of a project with submodules in it and will collaborate with
199199

200200
===== Pulling in Upstream Changes
201201

202-
The simplest model of using submodules in a project would be if you were simply consuming a subproject and wanted to get updates from it from time to time but were not actually modifying anything in your checkout. Let's walk though a simple example there.
202+
The simplest model of using submodules in a project would be if you were simply consuming a subproject and wanted to get updates from it from time to time but were not actually modifying anything in your checkout. Let's walk through a simple example there.
203203

204204
If you want to check for new work in a submodule, you can go into the directory and run `git fetch` and `git merge` the upstream branch to update the local code.
205205

0 commit comments

Comments
 (0)