diff --git a/docs/Getting started/02.folder_structure.md b/docs/Getting_started/02.folder_structure.md
similarity index 100%
rename from docs/Getting started/02.folder_structure.md
rename to docs/Getting_started/02.folder_structure.md
diff --git a/docs/Tutorials/01.https-to-backend.md b/docs/Tutorials/01.https-to-backend.md
index a04d0f2..c39ad8b 100644
--- a/docs/Tutorials/01.https-to-backend.md
+++ b/docs/Tutorials/01.https-to-backend.md
@@ -6,7 +6,7 @@ sidebar_position: 1
 ---
 By default, requests to services will go to ingress-nginx service first and ingress-nginx will terminate the ssl and it will send http traffic to the backend service.
 
-![HTTPS and Ingress Nginx](https-and-ingress-nginx.png)
+![HTTPS and Ingress Nginx](../../static/img/docs_images/https-and-ingress-nginx.png)
 
 While some people consider this architecture secure enough, some users prefer to secure the communication between ingress-nginx and pods as well. In this tutorial you will learn how to do it.
 
diff --git a/docs/Getting started/01.installation.md b/docs/intro.md
similarity index 99%
rename from docs/Getting started/01.installation.md
rename to docs/intro.md
index 7268178..9734945 100644
--- a/docs/Getting started/01.installation.md	
+++ b/docs/intro.md
@@ -1,5 +1,5 @@
 ---
-slug: isntallation
+slug: intro
 title: Installation
 sidebar_label: Installation
 sidebar_position: 1
diff --git a/src/pages/index.tsx b/src/pages/index.tsx
index cbc0edb..f4880f9 100644
--- a/src/pages/index.tsx
+++ b/src/pages/index.tsx
@@ -69,4 +69,4 @@ function Home() {
   );
 }
 
-export default Home;
\ No newline at end of file
+export default Home;
diff --git a/docs/Tutorials/https-and-ingress-nginx.png b/static/img/docs_images/https-and-ingress-nginx.png
similarity index 100%
rename from docs/Tutorials/https-and-ingress-nginx.png
rename to static/img/docs_images/https-and-ingress-nginx.png