Update README.md

Author: csviri

README.md

@@ -23,7 +23,7 @@ should be reconciled. Supports conditional resources in runtime, ordering of res
 The project introduces two Kubernetes custom resources `Glue` and `GlueOperator`.
 You can use `GlueOperator` to define your own operator.
 Let's take a look at an example, where we define an operator for WebPage custom resource, that represents a static website served from the Cluster. (You can see the
-[full example here](https://github.com/csviri/resource-workflow-operator/blob/main/src/test/resources/sample/webpage)):
+[full example here](https://github.com/csviri/resource-workflow-operator/blob/main/src/test/resources/sample/webpage) ):
 
 ```yaml
 
@@ -45,7 +45,7 @@ spec:
 ```
 
 To create an operator (or more precisely the controller part) with `resource-glue-operator` we have first apply
-the {CRD for WebPage](https://github.com/csviri/resource-workflow-operator/blob/main/src/test/resources/sample/webpage/webpage.crd.yml).
+the [CRD for WebPage](https://github.com/csviri/resource-workflow-operator/blob/main/src/test/resources/sample/webpage/webpage.crd.yml).
 To define how the `WebPage` should be reconciled, thus what resources should be created for
 a `WebPage`, we prepare a `GlueOperator`:
 
@@ -120,7 +120,7 @@ resources are applied, however, there are certain cases when this is needed also
 The following example shows how to deploy a [dynamic admission controller](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/) that mutates 
 all the `Pods`, adding annotation on them. Note that this is a tricky situation since the endpoint for the `MutatingWebhookConfiguration` is also a `Pod`, thus it should be 
 first up and running before the configuration is applied, otherwise, the mutation webhook will block the changes on the pods, which would render the cluster unable to manage `Pods' 
-(irrelevant details are omitted, see the full version [here][https://github.com/csviri/resource-workflow-operator/blob/main/src/test/resources/sample/mutation/mutation.glue.yaml]): 
+(irrelevant details are omitted, see the full version [here](https://github.com/csviri/resource-workflow-operator/blob/main/src/test/resources/sample/mutation/mutation.glue.yaml)): 
 
 ```yaml
 apiVersion: io.csviri.operator.resourceglue/v1beta1
@@ -137,7 +137,7 @@ spec:
           name: pod-mutating-hook
         spec:
           # spec omitted       
-    - name: deployment  # webhook endpoint
+    - name: deployment  # webhook web-service endpoint
       readyPostCondition:
         type: ReadyCondition  # ready post conditions determine when a Deployment is considered "ready", thus up and running.
       resource:
@@ -158,8 +158,10 @@ spec:
                       protocol: TCP
                         
     - name: mutation_hook_config
-      # dependsOn relation means, that the resource will be reconciled only if all the listed resources are already reconciled and ready (if ready post-condition is present).
-      # This resource will be applied, after the service and deployment are applied, and the deployment is ready, thus all the pods are started up and ready.
+      # dependsOn relation means, that the resource will be reconciled only if all
+      # the listed resources are already reconciled and ready (if ready post-condition is present).
+      # This resource will be applied after the service and deployment are applied,
+      # and the deployment is ready, thus all the pods are started up and ready.
       dependsOn:
         - deployment
         - service
@@ -190,5 +192,5 @@ spec:
                   - pods                         
 ```
 
-
+See the full E2E test [here](https://github.com/csviri/resource-workflow-operator/blob/main/src/test/java/io/csviri/operator/resourceglue/sample/mutation/MutationWebhookDeploymentE2E.java).