Skip to content

Commit 8240df8

Browse files
authored
Merge branch 'LibraryCarpentry:gh-pages' into gh-pages
2 parents 163d304 + f8fd707 commit 8240df8

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

_episodes/02-getting-started.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -131,11 +131,7 @@ $ cd hello-world
131131

132132
### Using Git
133133

134-
One of the main barriers to getting started with Git is the language. Although some of the language used in Git is
135-
fairly self-explanatory, other terms are not so clear. The best way to get to learn the language - which consists of a
136-
number of verbs such as `add`, `commit` and `push` (preceded by the word 'git') - is by using it, which is what we will be doing during this
137-
lesson. These commands will be explained as we proceed from setting up a new version-controlled project to publishing
138-
our own website.
134+
One of the main barriers to getting started with Git is understanding the terminology necessary to executing commands. Although some of the language used in Git aligns with common-use words in English, other terms are not so clear. The best way to learn Git terminology - which consists of a number of verbs such as add, commit and push (preceded by the word 'git') - is to use it, which is what we will be doing during this lesson. We will explain these commands as we proceed from setting up a new version-controlled project to publishing our own website.
139135

140136
On a command line interface, Git commands are written as `git verb options`,
141137
where `verb` is what we actually want to do and `options` is additional optional information which may be needed for the `verb`. So let's get started with our setup.

0 commit comments

Comments
 (0)