fixed Grammatical mistakes in barbican-kms-plugin (kubernetes#2289)

* fixed Grammatical mistakes in barbican-kms-plugin

* Fixed the Grammatical mistakes in barbican-kms-plugin

* Fixed the Grammatical mistakes in barbican-kms-plugin

* Fixed the Grammatical mistakes in barbican-kms-plugin

* Fixed the Grammatical mistakes in barbican-kms-plugin

Author: Vikash-8090-Yadav

docs/barbican-kms-plugin/using-barbican-kms-plugin.md

@@ -9,10 +9,10 @@
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
 
 # OpenStack Barbican KMS Plugin
-Kubernetes supports to encrypt etcd data with various providers listed [here](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#providers), one of which is *kms*. The Kubernetes *kms provider* uses envelope encryption scheme. The data is encrypted using *DEK's* by kubernetes *kms provider*, *DEK's* are encrypted by *kms plugin* (e.g. barbican) using *KEK*. *Barbican-kms-plugin* uses *key* from barbican to encrypt/decrypt the *DEK's* as requested by kubernetes api server. 
+Kubernetes supports encrypting etcd data with various providers listed [here](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#providers), one of which is *kms*. The Kubernetes *kms provider* uses an envelope encryption scheme. The data is encrypted using *DEK's* by kubernetes *kms provider*, *DEK's* are encrypted by *kms plugin* (e.g. barbican) using *KEK*. *Barbican-kms-plugin* uses *key* from barbican to encrypt/decrypt the *DEK's* as requested by kubernetes api server. 
 The *KMS provider* uses gRPC to communicate with a specific *KMS plugin*.
 
-It is recommended to read following kubernetes documents  
+It is recommended to read the following kubernetes documents  
 
 * [Encrypting Secret Data at Rest](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#verifying-that-data-is-encrypted)  
 * [Using a KMS provider for data encryption](https://kubernetes.io/docs/tasks/administer-cluster/kms-provider/)
@@ -23,7 +23,7 @@ It is recommended to read following kubernetes documents
 The following installation steps assumes that you have a Kubernetes cluster(v1.10+) running on OpenStack Cloud.
 
 
-### Create 256bit(32 byte) cbc key and store in barbican
+### Create 256-bit (32 bytes) CBC key and store in barbican
 
 ```
 $ openstack secret order create --name k8s_key --algorithm aes --mode cbc --bit-length 256 --payload-content-type=application/octet-stream key
@@ -41,7 +41,7 @@ $ openstack secret order create --name k8s_key --algorithm aes --mode cbc --bit-
 +----------------+----------------------------------------------------------------------+
 ```
 
-### Get the Key ID, It is the **uuid** in *Secret href*
+### Get the key ID, it is the **uuid** in *Secret href*
 
 ```
 $ openstack secret order get http://hostname:9311/v1/orders/e477a578-4a46-4c3f-b071-79e220207b0e
@@ -60,7 +60,7 @@ $ openstack secret order get http://hostname:9311/v1/orders/e477a578-4a46-4c3f-b
 ```
 
 
-### Add the Key ID in your cloud-config file
+### Add the key ID in your cloud-config file
 
 ```toml
 [Global]
@@ -79,18 +79,18 @@ key-id = "<key-id>"
 ### Run the KMS Plugin in your cluster
 
 This will provide a socket at `/var/lib/kms/kms.sock` on each of the control
-plane node
+plane nodes.
 ```
 kubectl apply -f https://raw.githubusercontent.com/kubernetes/cloud-provider-openstack/master/manifests/barbican-kms/ds.yaml
 ```
 *recommendation:* Use the tag corresponding to your Kubernetes release, for
 example `release-1.25` for kubernetes version 1.25.
 
 
-### Create encrytion configuration
+### Create encryption configuration
 
 Create `/etc/kubernetes/encryption-config.yaml` on each of your control plane
-nodes
+nodes.
 ```yaml
 kind: EncryptionConfig
 apiVersion: v1
@@ -108,7 +108,7 @@ resources:
 
 ### Update the API server
 
-On each of your control plane nodes you need to edit the kube-apiserver, the
+On each of your control plane nodes, you need to edit the kube-apiserver, the
 configuration is usually found at
 `/etc/kubernetes/manifests/kube-apiserver.yaml`. You can just edit it and
 kubernetes will eventually restart the pod with the new configuration.
@@ -142,5 +142,5 @@ spec:
 
 
 ### Verify
-[Verify the secret data is encrypted](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#verifying-that-data-is-encrypted
+[Verify that the secret data is encrypted](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#verifying-that-data-is-encrypted
 )