diff --git a/05-Sidecar/01-ingress-proxy-forwarding/Gateway.yaml b/05-Sidecar/01-ingress-proxy-forwarding/Gateway.yaml
index cb147c2..456e384 100755
--- a/05-Sidecar/01-ingress-proxy-forwarding/Gateway.yaml
+++ b/05-Sidecar/01-ingress-proxy-forwarding/Gateway.yaml
@@ -12,24 +12,3 @@ spec:
         protocol: HTTP
       hosts:
         - "*"
----
-apiVersion: networking.istio.io/v1alpha3
-kind: VirtualService
-metadata:
-  name: helloworld-vs
-spec:
-  hosts:
-    - "*"
-  gateways:
-    - helloworld-gateway
-  http:
-    - match:
-        - uri:
-            exact: /helloworld
-      route:
-        - destination:
-            host: helloworld.default.svc.cluster.local
-            port:
-              number: 8080
-      rewrite:
-        uri: "/"
\ No newline at end of file
diff --git a/05-Sidecar/01-ingress-proxy-forwarding/README.md b/05-Sidecar/01-ingress-proxy-forwarding/README.md
index b551f03..0bc2a1d 100755
--- a/05-Sidecar/01-ingress-proxy-forwarding/README.md
+++ b/05-Sidecar/01-ingress-proxy-forwarding/README.md
@@ -1,50 +1,105 @@
-# Continues from
-
-- 01-hello_world_1_service_1_deployment
-
-# TO TRAFFIC PATH DIAGRAM
-
-`etc -> "POD" -> sidecar -> service container`
+---
+gitea: none
+include_toc: true
+---
 
 # Description
 
-This example configures the sidecar proxy on the pods created, to forward the traffic incoming from the port `8080` to the port `80`
+This example deploys the same infrastructure as the [previous example](../../01-Getting_Started/01-hello_world_1_service_1_deployment), configures the **sidecar** `envoy-proxy`/`istio-proxy`/`sidecar-proxy` on the pods created, to forward the traffic incoming from the port `8080` to the port `80`.
 
-## Files
+This example configures:
 
-- deployment.yaml
-- gateway.yaml
-- sidecar.yaml
+    Generic Kubernetes resources:
+    - 1 Service
+    - 1 Deployment
+    
+    Istio resources:
+    - 1 Gateway
+    - 1 Virtual Service
+    - 1 Sidecar configration
 
-> Added the `sidecar.yaml` file.
+# Based on
 
-## deployment.yaml
+- [01-hello_world_1_service_1_deployment](../../01-Getting_Started/01-hello_world_1_service_1_deployment)
 
-### Creates
+# Configuration
 
-#### Service
+`etc -> "POD" -> sidecar -> service container`
 
-- helloworld
+## Service
 
-#### Deployments
+Creates a service named `helloworld`.
 
-- helloworld-nginx  (Nginx container)
+This service listens for the port `8080` expecting `HTTP` traffic and will forward the incoming traffic towards the port `8080` from the destination pod.
 
-## gateway.yaml
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: helloworld
+  labels:
+    app: helloworld
+spec:
+  ports:
+    - port: 8080
+      name: http
+  selector:
+    app: helloworld
+```
 
-### Creates
+## Deployment
 
-#### Gateway
+Deploys a Nginx server that listens for the port `80`.
 
-##### helloworld-gateway
+We can notice how in the service we opened the port `8080` and in the deployment we are listening to the port `80`, more about this in the [Sidecar Section](#sidecar).
 
-###### Configuration
+```yaml
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: helloworld-nginx
+  labels:
+    app: helloworld
+spec:
+  replicas: 1
+  selector:
+    matchLabels:
+      app: helloworld
+  template:
+    metadata:
+      labels:
+        app: helloworld
+    spec:
+      containers:
+        - name: helloworld
+          image: nginx
+          resources:
+            requests:
+              cpu: "100m"
+          imagePullPolicy: IfNotPresent #Always
+          ports:
+            - containerPort: 80
+```
 
-```yml
-...
+
+## Gateway
+
+Deploys an Istio gateway that's listening to the port `80` for `HTTP` traffic.
+
+It doesn't filter for any specific host.
+
+The `selector` field is used to "choose" which Istio Load Balancers will have this gateway assigned to.
+
+The Istio `default` profile creates a Load Balancer in the namespace `istio-system` that has the label `istio: ingressgateway` set, allowing us to target that specific Load Balancer and assign this gateway resource to it.
+
+```yaml
+apiVersion: networking.istio.io/v1alpha3
+kind: Gateway
+metadata:
+  name: helloworld-gateway
 spec:
   selector:
-    istio: ingressgateway # use istio default controller
+    istio: ingressgateway
   servers:
     - port:
         number: 80
@@ -54,14 +109,25 @@ spec:
         - "*"
 ```
 
-#### VirtualService
+## VirtualService
 
-##### helloworld-vs
+The Virtual Service resources are used to route and filter the received traffic from the gateway resources, and route it towards the desired destination.
 
-###### Configuration
+On this example we select the gateway `helloworld-gateway`, which is the [gateway that 's described in the `Gateway` section](#gateway).
+
+On this resource, we are also not limiting the incoming traffic to any specific host, allowing for all the incoming traffic to go through the rules set.
+
+Here we created a rule that will be applied on `HTTP` related traffic when the destination path is exactly `/helloworld`.
+
+This traffic will be forwarded to the port `8080` of the destination service `helloworld` (the full path URL equivalent would be `helloworld.$NAMESPACE.svc.cluster.local`).
+
+Additionally, there will be an internal URL rewrite set, as if the URL is not modified, it would attempt to reach to the `/helloworld` path from the Nginx deployment, which currently has no content and would result in an error code `404` (Not found).
 
 ```yaml
-...
+apiVersion: networking.istio.io/v1alpha3
+kind: VirtualService
+metadata:
+  name: helloworld-vs
 spec:
   hosts:
     - "*"
@@ -73,27 +139,46 @@ spec:
             exact: /helloworld
       route:
         - destination:
-            host: helloworld.default.svc.cluster.local
+            host: helloworld
             port:
-              number: 8080
+              number: 80
       rewrite:
         uri: "/"
 ```
 
-- On this example, we are using the port `8080` as a destination.
+## Sidecar
 
-## sidecar.yaml
+This will configure the sidecar configuration from the `envoy-proxy` in each pod.
 
-### creates
+`workloadSelector` will be used to select the target pods, where, on this scenario, it will target the pods that have the label set `app: helloworld`.
 
-#### sidecar
+The ingress configuration set, will listen for the port `8080` from the pod, and forward it to the pod's port `80` through the loopback (127.0.0.1) IP.
 
-##### helloworld-sidecar
+On this scenario we are performing a simple `8080` to `80` redirect.
+
+> **Note:**\
+> A reminder that a `POD` is an object that groups container(s).
+
++ more notes:
+
+- workloadSelector:
+
+> `workloadSelector` is used to target the `PODS`, on which apply this sidecar configuration. \
+> Bear in mind that this configuration doesn't target kinds `Service`, nor `Deployment`, it's applied to a kind `Pod` or `ServiceEntry` \
+> If there is no `workloadSelector` specified, it will be used as default configuration for the namespace on which was created. \
+> More info in the [Istio documentation for workloadSelector](https://istio.io/latest/docs/reference/config/networking/sidecar/#WorkloadSelector)
+
+- ingress:
+
+> Configure the behavior of the ingress traffic.\
+> On this "grabs"/targets the ingress traffic with port 8080, and forwards it to the port IP `127.0.0.1` (loopback) respective to the destination pod, with the destination port set to 80, which is the port that the service is currently listening to.
 
-###### Configuration
 
 ```yaml
-...
+apiVersion: networking.istio.io/v1alpha3
+kind: Sidecar
+metadata:
+  name: helloworld-sidecar
 spec:
   workloadSelector:
     labels:
@@ -104,37 +189,31 @@ spec:
         protocol: HTTP
         name: ingressport
       defaultEndpoint: 127.0.0.1:80
-````
-
-workloadSelector:
-
-> `workloadSelector` is used to target the `PODS`, on which apply this sidecar configuration. \
-> Bear in mind that this configuration doesn't target kinds `Service`, nor `Deployment`, it's applied to a kind `Pod` or `ServiceEntry` \
-> If there is no `workloadSelector` specified, it will be used as default configuration for the namespace on which was created. \
-> More info in the [Istio documentation for workloadSelector](https://istio.io/latest/docs/reference/config/networking/sidecar/#WorkloadSelector)
-
-ingress:
-
-> Configure the behavior of the ingress traffic.\
-> On this "grabs"/targets the ingress traffic with port 8080, and forwards it to the port IP `127.0.0.1` (loopback) respective to the destination pod, with the destination port set to 80, which is the port that the service is currently listening to.
+```
 
 # Run example
 
 ## Deploy resources
 
 ```shell
-$ kubectl apply -f ./
-service/helloworld created
+kubectl apply -f ./
+```
+
+```text
 deployment.apps/helloworld-nginx created
 gateway.networking.istio.io/helloworld-gateway created
-virtualservice.networking.istio.io/helloworld-vs created
+service/helloworld created
 sidecar.networking.istio.io/helloworld-sidecar created
+virtualservice.networking.istio.io/helloworld-vs created
 ```
 
 ## Wait for the pods to be ready
 
 ```shell
-$ kubectl get deployment helloworld-nginx -w
+kubectl get deployment helloworld-nginx -w
+```
+
+```text
 NAME               READY   UP-TO-DATE   AVAILABLE   AGE
 helloworld-nginx   1/1     1            1           39s
 ```
@@ -143,30 +222,70 @@ helloworld-nginx   1/1     1            1           39s
 
 ### Get LB IP
 
+To perform the desired tests, we will need to obtain the IP Istio Load Balancer that we selected in the [Gateway section](#gateway).
+
+On my environment, the IP is the `192.168.1.50`.
+
 ```shell
-$ kubectl get svc istio-ingressgateway -n istio-system
+kubectl get svc -l istio=ingressgateway -A
+```
+```text
 NAME                   TYPE           CLUSTER-IP     EXTERNAL-IP    PORT(S)                                      AGE
 istio-ingressgateway   LoadBalancer   10.97.47.216   192.168.1.50   15021:31316/TCP,80:32012/TCP,443:32486/TCP   39h
 ```
 
 ### Curl
 
+We can perform a curl towards the destination.
+
+A reminder that the configuration set in the [service](#service) created, it's listening to the port `8080` and forwarding the traffic to the same pod (`8080`).
+
+As well on the Istio's [VirtualService](#virtualservice), we configured the destination port as `8080`.
+
+Yet, on the [Sidecar](#sidecar) configuration, we are redirecting the ingress traffic from the port `8080`, to the port `80`.
+
 ```shell
-$ curl 192.168.1.50/helloworld -s | grep "<title>.*</title>"
+curl 192.168.1.50/helloworld -s | grep "<title>.*</title>"
+```
+```text
 <title>Welcome to nginx!</title>
 ```
 
 ### Delete the sidecar configuration to force failure.
 
+As per the moment let's delete the `sidecar` configuration deployed.
 
 ```shell
-$ kubectl delete sidecars.networking.istio.io helloworld-sidecar
+kubectl delete sidecars.networking.istio.io helloworld-sidecar
+```
+```text
 sidecar.networking.istio.io "helloworld-sidecar" deleted
 ```
+
 ### Curl again
 
+After deleting the `sidecar` configuration, which was handling the ingress traffic from port `8080`, we can observe that we are no longer able to handle the incoming requests, raising an error message. 
+
 ```shell
-$ curl 192.168.1.50/helloworld -s
+curl 192.168.1.50/helloworld -s
+```
+```text
 upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: delayed connect error: 111
 ```
 
+## Cleanup
+
+Finally, a cleanup from the resources deployed.
+
+```shell
+kubectl delete -f ./
+```
+```text
+deployment.apps "helloworld-nginx" deleted
+gateway.networking.istio.io "helloworld-gateway" deleted
+service "helloworld" deleted
+virtualservice.networking.istio.io "helloworld-vs" deleted
+Error from server (NotFound): error when deleting "Sidecar.yaml": sidecars.networking.istio.io "helloworld-sidecar" not found
+```
+
+
diff --git a/05-Sidecar/01-ingress-proxy-forwarding/VirtualService.yaml b/05-Sidecar/01-ingress-proxy-forwarding/VirtualService.yaml
new file mode 100644
index 0000000..9dd7345
--- /dev/null
+++ b/05-Sidecar/01-ingress-proxy-forwarding/VirtualService.yaml
@@ -0,0 +1,20 @@
+apiVersion: networking.istio.io/v1alpha3
+kind: VirtualService
+metadata:
+  name: helloworld-vs
+spec:
+  hosts:
+    - "*"
+  gateways:
+    - helloworld-gateway
+  http:
+    - match:
+        - uri:
+            exact: /helloworld
+      route:
+        - destination:
+            host: helloworld.default.svc.cluster.local
+            port:
+              number: 8080
+      rewrite:
+        uri: "/"
\ No newline at end of file