wip

Author: youngbupark

enhancements/sig-architecture/227-manifestworkreplicaset-rollout-plugin/README.md

@@ -243,9 +243,7 @@ The plugin hook APIs will identify the ManifestWorkReplicaSet being processed wi
 
 #### Error handling
 
-gRPC status codes follow the [standard gRPC status codes](https://grpc.github.io/grpc/core/md_doc_statuscodes.html): 0 = OK, 1 = CANCELLED, 2 = UNKNOWN, 3 = INVALID_ARGUMENT, 4 = DEADLINE_EXCEEDED, etc.
-Work controller will also utilize the [standard gRPC retry](https://grpc.io/docs/guides/retry/) for `UNAVAILABLE` status code.
-
+gRPC status codes follow the [standard gRPC status codes](https://grpc.github.io/grpc/core/md_doc_statuscodes.html): 0 = OK, 1 = CANCELLED, 2 = UNKNOWN, 3 = INVALID_ARGUMENT, 4 = DEADLINE_EXCEEDED, etc. Work controller will also utilize the [standard gRPC retry](https://grpc.io/docs/guides/retry/) for `UNAVAILABLE` status code. 
 When work controller fails to call plugin APIs, the failure reason from plugin server is shown in `PluginLoaded` status condition message for debugging purpose.
 
 ### Register custom plugins for work controller
@@ -338,7 +336,7 @@ spec:
 
 ### Using plugin in MWRS
 
-Plugin is an opt-in feature. User can use the registered plugin by setting `.spec.placementRefs[*].rolloutStrategy.plugin`. 
+Plugin is an opt-in feature. User can use the registered plugin by setting `.spec.placementRefs[*].rolloutStrategy.plugin`. The reconciler makes sure that plugin is available and show its availability or error messages in `PluginLoaded` status condition type.
 
 ```yaml
 apiVersion: work.open-cluster-management.io/v1
@@ -364,7 +362,7 @@ status:
       type: PluginLoaded
 ```
 
-The reconciler makes sure that plugin is available and show its availability or error messages in `PluginLoaded` status condition like below:
+The following example shows `Available` and `Failed` reasons for `PluginLoaded` status condition type
 
 | Reason | Status | Message |
 | --- | --- | --- |