Skip to content

Commit 71b65b2

Browse files
authored
Merge pull request #165 from LibraryCarpentry/rm-simply
remove dismissive language
2 parents b3bf02c + 9aec254 commit 71b65b2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

episodes/02-getting-started.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ On a command line interface, Git commands are written as `git verb options`,
133133
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.
134134

135135
We will now create an empty git repository to track changes to our project. To do this we will use the git **init** command,
136-
which is simply short for *initialise*.
136+
which is short for *initialise*.
137137

138138
```bash
139139
$ git init
@@ -148,7 +148,7 @@ The `hello-world` directory is now a git repository.
148148
If we run the `ls` command now (`ls` lists the content of the `hello-world`
149149
directory), the repository might seem empty; however, adding the `-a` flag
150150
for all files via `ls -a` will show all hidden files, which in this case
151-
includes the new hidden directory `.git`. Flags can simply be thought of as command line options that can be added to shell commands.
151+
includes the new hidden directory `.git`. Flags can be thought of as command line options that can be added to shell commands.
152152

153153
Note that whenever we use git via the command line, we need to preface each command (or verb) with `git`, so that the computer knows
154154
we are trying to get git to do something, rather than some other program.

0 commit comments

Comments
 (0)