From a49d013bab5c03342e653b0d71025f28588e65c8 Mon Sep 17 00:00:00 2001
From: holzheim <jan.holzheim@online.de>
Date: Tue, 4 Apr 2023 10:32:06 +0200
Subject: [PATCH] Removed notes and some corrections

---
 00_GettingStarted/README.md | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/00_GettingStarted/README.md b/00_GettingStarted/README.md
index 34fa570..c4d1ce9 100644
--- a/00_GettingStarted/README.md
+++ b/00_GettingStarted/README.md
@@ -2,8 +2,6 @@
 
 In this section you will find information about the **software** and **tools** we will use during the course and how to **install** them and how to **set everything up**.
 
-(Description of the needed tools, like IDE (Visual Studio Code), Docker, etc.)
-
 ## **I**ntegrated **D**evelopment **E**nvironment (**IDE**)
 
 ### What is an IDE?
@@ -118,8 +116,8 @@ Follow the instructions to download the repository to your local machine and sta
 
 7. In the `Docker Desktop` GUI go to the *Containers* tab. You should see now, that there are two containers launched under the group name *i2r*.
 
-    ![Docker Desktop GUI with group of containers running](images/docker_group_running.png)*`Docker Desktop` GUI: Inside the Containers tab you should find the started group of containers.* 
-    - Another option to inspect the containers is using the terminal. (Note: If you are still in the terimal you executed the *docker compose up*, make sure to start a new terminl, but let the old terminal running.)
+    ![Docker Desktop GUI with group of containers running](images/docker_group_running.png)*`Docker Desktop` GUI: Inside the Containers tab you should find the started group of containers.*
+    - Another option to inspect the containers is using the terminal. (Note: If you are still in the terminal you executed the *docker compose up*, make sure to start a new terminal, but let the old terminal running.)
 
         ```bash
         docker ps --all
@@ -147,7 +145,7 @@ Follow the instructions to download the repository to your local machine and sta
 
     ![GIF: Terminal output for *roscore*](images/roscore.gif)
 
-    If that worked out, you can again close the the started *ROS Master* by typing *`Ctrl` + `C`*. That shuts down the *Master* node. To leave the *bash* session inside of the *i2r-ros-1 container* just type *`Ctrl` + `D`*.
+    If that worked out, you can close the started *ROS Master* by typing *`Ctrl` + `C`*. That shuts down the *Master* node. To leave the *bash* session inside of the *i2r-ros-1 container* just type *`Ctrl` + `D`*.
 
     ![GIF: Terminal output kill master and leave container session.](images/kill_master_leave_container.gif)
 10. To stop the started group of containers named *i2r* you can either use the `Docker Desktop` GUI from the *Container* tab like shown below.
@@ -158,7 +156,7 @@ Follow the instructions to download the repository to your local machine and sta
 
     ![GIF: Terminal output container group from terminal.](images/stopping_container_group.gif)
 
-11. If all the previous steps worked you have successfully installed the envrionment we will be using during in `Introduction to Robotics` to work with `ROS`. 
+11. If all the previous steps worked you have successfully installed the envrionment we will be using during in `Introduction to Robotics` course to work with `ROS`.
 
     If you want to restart a container just make sure that:
 
@@ -177,5 +175,4 @@ Follow the instructions to download the repository to your local machine and sta
 
 If you run into any issues during the installation process of these softwares, you are welcome to ask me ([Contact Data](https://www.gut.rwth-aachen.de/cms/Geotechnik/Das-Institut/Team/~peawz/Jan-Holzheim/lidx/1/), via mail, phone or in presence).
 
-(Remark: Add notice to Tutorials)
 
-- 
GitLab