Modify wording based on comments on July 25th

Author: sunnylovestiramisu

csi.proto

@@ -385,7 +385,7 @@ message CreateVolumeRequest {
 
   // Plugin specific parameters to apply, passed in as opaque
   // key-value pairs. This field is OPTIONAL. The Plugin is
-  // responsible for  parsing and validating these parameters. 
+  // responsible for parsing and validating these parameters. 
   // COs will treat these as opaque. Plugins MUST treat these 
   // as if they take precedence over the parameters field.
   // This field SHALL NOT be specified unless the SP has the

lib/go/csi/csi.pb.go

@@ -856,7 +856,7 @@ message CreateVolumeRequest {
 
   // Plugin specific parameters to apply, passed in as opaque
   // key-value pairs. This field is OPTIONAL. The Plugin is
-  // responsible for  parsing and validating these parameters. 
+  // responsible for parsing and validating these parameters. 
   // COs will treat these as opaque. Plugins MUST treat these 
   // as if they take precedence over the parameters field.
   // This field SHALL NOT be specified unless the SP has the
@@ -1647,7 +1647,7 @@ The CO MUST implement the specified error recovery behavior when it encounters t
 
 #### `ControllerModifyVolume`
 
-A Controller plugin MUST implement this RPC call if plugin has MODIFY_VOLUME controller capability.
+A Controller plugin MUST implement this RPC call if the plugin has the MODIFY_VOLUME controller capability.
 This RPC allows the CO to change mutable key attributes of a volume. 
 
 This operation MUST be idempotent. 
@@ -1689,7 +1689,7 @@ message ControllerModifyVolumeResponse {
 |-----------|-----------|-------------|-------------------|
 | Parameters not supported | 3 INVALID_ARGUMENT | Indicates that the CO has specified mutable parameters not supported by the volume. | Caller MAY verify mutable parameters. |
 | Exceeds capabilities | 3 INVALID_ARGUMENT | Indicates that the CO has specified capabilities not supported by the volume. | Caller MAY verify volume capabilities by calling ValidateVolumeCapabilities and retry with matching capabilities. |
-| Volume does not exist | 5 NOT FOUND | Indicates that a volume corresponding to the specified volume_id does not exist. | Caller MUST verify that the volume_id is correct and that the volume is accessible and has not been deleted before retrying with exponential back off. |
+| Volume does not exist | 5 NOT_FOUND | Indicates that a volume corresponding to the specified volume_id does not exist. | Caller MUST verify that the volume_id is correct and that the volume is accessible and has not been deleted before retrying with exponential back off. |
 
 #### `GetCapacity`