From 9aec2540bc2ac5c23999408e5172aa9ad1d7447d Mon Sep 17 00:00:00 2001
From: maneesha <829690+maneesha@users.noreply.github.com>
Date: Wed, 8 May 2024 10:28:10 -0400
Subject: [PATCH] remove dismissive language

Remove language where terms are defined as "simply" something.
---
 episodes/02-getting-started.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/episodes/02-getting-started.md b/episodes/02-getting-started.md
index 1fad374b..87607b8b 100644
--- a/episodes/02-getting-started.md
+++ b/episodes/02-getting-started.md
@@ -133,7 +133,7 @@ On a command line interface, Git commands are written as `git verb options`,
 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.
 
 We will now create an empty git repository to track changes to our project. To do this we will use the git **init** command,
-which is simply short for *initialise*.
+which is short for *initialise*.
 
 ```bash 
 $ git init
@@ -148,7 +148,7 @@ The `hello-world` directory is now a git repository.
 If we run the `ls` command now (`ls` lists the content of the `hello-world`
 directory), the repository might seem empty; however, adding the `-a` flag
 for all files via `ls -a` will show all hidden files, which in this case
-includes the new hidden directory `.git`. Flags can simply be thought of as command line options that can be added to shell commands.
+includes the new hidden directory `.git`. Flags can be thought of as command line options that can be added to shell commands.
 
 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
 we are trying to get git to do something, rather than some other program.