docs: Update docs (#1382)

Signed-off-by: Jaeyeon Kim <anencore94@gmail.com>

docs/sensors/triggers/k8s-object-trigger.md

@@ -1,7 +1,8 @@
 # Kubernetes Object Trigger
 
-Apart from Argo workflow objects, the sensor lets you trigger standard Kubernetes objects such as Pod, Deployment, Job, CronJob, etc.
-Having the ability to trigger standard Kubernetes objects is quite powerful as provides an avenue to
+Apart from Argo workflow objects, the sensor lets you trigger any Kubernetes objects including Custom Resources 
+such as Pod, Deployment, Job, CronJob, etc.
+Having the ability to trigger Kubernetes objects is quite powerful as providing an avenue to
 set up event-driven pipelines for existing workloads.
 
 <br/>
@@ -70,8 +71,8 @@ set up event-driven pipelines for existing workloads.
 1. Use either Curl or Postman to send a post request to the `http://localhost:12000/example`.
 
         curl -d '{"message":"ok"}' -H "Content-Type: application/json" -X POST http://localhost:12000/example
-   
-1. Inspect the logs of the pod, you will something similar as below.
+
+1. After the pod was completed, inspect the logs of the pod, you will see something similar as below.
 
         _________________________________________ 
         / {"context":{"type":"webhook","specVersi \

docs/tutorials/04-standard-k8s-resources.md

@@ -50,7 +50,7 @@ provides an avenue to set up pipelines for existing workloads.
 
         kubectl -n argo-events get po
 
-Output
+4.  After the pod was completed, inspect the logs of the pod, you will something similar as below.
 
         _________________________________________
         / {"context":{"type":"webhook","specVersi \
@@ -93,7 +93,7 @@ Output
 
         kubectl -n argo-events get deployments
 
-Output
+4. After the pod was completed, inspect the logs of the pod, you will see something similar as below.
 
         _________________________________________
         / {"context":{"type":"webhook","specVersi \