fixed typos: syncronize -> synchronize
Aaron Beckerman committed
Aug 11, 2010 at 02:09 UTC
b7ce6278ea391972915d9945e90fdc9af82a2629
1 file changed
+9
-9
remotes/index.html
+9
-9
@@ -15,9 +15,9 @@ layout: reference
15
so far have been done locally, just updating a local database.
16
To collaborate with other developers in Git, you have to put all that
17
data on a server that the other developers have access to. The way Git
18
- does this is to syncronize your data with another repository. There
18
+ does this is to synchronize your data with another repository. There
19
is no real difference between a server and a client - a Git repository
20
- is a Git repository and you can syncronize between any two easily.
20
+ is a Git repository and you can synchronize between any two easily.
21
</p>
22
23
<p>Once you have a Git repository, either one that you set up on your
@@ -54,12 +54,12 @@ layout: reference
54
55
<p>Unlike centralized version control systems that have a client that is
56
very different from a server, Git repositories are all basically equal and
57
- you simply syncronize between them. This makes it easy to have more than
57
+ you simply synchronize between them. This makes it easy to have more than
58
one remote repository - you can have some that you have read-only access to
59
and others that you can write to as well.</p>
60
61
<p>So that you don't have to use the full URL of a remote repository every
62
- time you want to syncronize with it, Git stores an alias or nickname for
62
+ time you want to synchronize with it, Git stores an alias or nickname for
63
each remote repository URL you are interested in. You use the
64
<code>git remote</code> command to manage this list of remote repos that
65
you care about.</p>
@@ -180,12 +180,12 @@ github git@github.com:schacon/hw.git (push)
180
<div class="block">
181
182
<p>Git has two commands to update itself from a remote repository.
183
- <code>git fetch</code> will syncronize you with another repo, pulling down any data
183
+ <code>git fetch</code> will synchronize you with another repo, pulling down any data
184
that you do not have locally and giving you bookmarks to where each branch on
185
- that remote was when you syncronized. These are called "remote branches" and are
185
+ that remote was when you synchronized. These are called "remote branches" and are
186
identical to local branches except that Git will not allow you to check them out -
187
however, you can merge from them, diff them to other branches, run history logs on
188
- them, etc. You do all of that stuff locally after you syncronize.
188
+ them, etc. You do all of that stuff locally after you synchronize.
189
</p>
190
191
<p>The second command that will fetch down new data from a remote server is
@@ -238,11 +238,11 @@ From github.com:schacon/hw
238
</p>
239
240
<p>If you have more than one remote repository, you can either fetch from specific
241
- ones by running <code>git fetch [alias]</code> or you can tell Git to syncronize
241
+ ones by running <code>git fetch [alias]</code> or you can tell Git to synchronize
242
with all of your remotes by running <code>git fetch --all</code>.
243
244
<p class="nutshell">
245
- <b>In a nutshell</b> you run <code>git fetch [alias]</code> to syncronize your
245
+ <b>In a nutshell</b> you run <code>git fetch [alias]</code> to synchronize your
246
repository with a remote repository, fetching all the data it has that you do
247
not into branch references locally for merging and whatnot.
248
</p>