fix spelling issues (#2667)

* fix errors CONTRIBUTING.md

Signed-off-by: David Klank <[email protected]>

* fix error README.md

Signed-off-by: David Klank <[email protected]>

* fix error README.md

Signed-off-by: David Klank <[email protected]>

* fix error indy.md

Signed-off-by: David Klank <[email protected]>

* fix error vault.md

Signed-off-by: David Klank <[email protected]>

---------

Signed-off-by: David Klank <[email protected]>
Co-authored-by: Sownak Roy <[email protected]>

Author: davidjsonn

CONTRIBUTING.md

@@ -7,7 +7,7 @@ there's always plenty to do!
 
 First things first, please review the [Hyperledger Code of Conduct](https://wiki.hyperledger.org/display/HYP/Hyperledger+Code+of+Conduct) before participating and please follow it in all your interactions with the project.
 
-You can contibute to Hyperledger Bevel, as a user or/and as a developer.
+You can contribute to Hyperledger Bevel, as a user or/and as a developer.
 
 ##### As a user:
 
@@ -117,7 +117,7 @@ The current directory structure is described as the following:
 
 
 > - automation/ : This folder contains the Jenkinsfile to deploy DLT Platforms supported by Hyperledger Bevel on a demo environment.
->   - hyperledger-fabric/ : ontains network.yaml file and fabric Jenkinsfile
+>   - hyperledger-fabric/ : contains network.yaml file and fabric Jenkinsfile
 >   - r3-corda/ : Contains network.yaml file and Jenkinsfile for doorman,networkmap and entire network deployment file.
 >   - initcontainer.Jenkinsfile : This file is used to initialize a container with basic configuration. This will be used on both hyperledger and r3-corda platforms.
 > - docs/

docs/source/archive/platforms/indy.md

@@ -37,7 +37,7 @@ Hyperledger Bevel creates/provides own Docker images, which are based on Ubuntu
 ## Vault Configuration
 
 Hyperledger Bevel stores their `crypto` immediately within the secret secrets engine.
-The `crypto` is stored by each organization under `/org_name_lowercase` - it contains provate/public keys, dids and seeds.
+The `crypto` is stored by each organization under `/org_name_lowercase` - it contains private/public keys, dids and seeds.
 
 
-The complete key paths in the vault can be referred [here](../certificates/indy.md).
+The complete key paths in the vault can be referred [here](../certificates/indy.md).

docs/source/concepts/vault.md

@@ -48,7 +48,7 @@ There are two approaches to installing Vault:
 Downloading a precompiled binary is easiest and provides downloads over TLS along with SHA256 sums to verify the binary. Hashicorp also distributes a PGP signature with the SHA256 sums that should be verified.
 
 ## Securing RPC Communication with TLS Encryption
-Securing your cluster with TLS encryption is an important step for production deployments. The recomended tool for vault certificate management is Consul. Hashicorp Consul is a networking tool that provides a fully featured service-mesh control plane, service discovery, configuration, and segmentation. 
+Securing your cluster with TLS encryption is an important step for production deployments. The recommended tool for vault certificate management is Consul. Hashicorp Consul is a networking tool that provides a fully featured service-mesh control plane, service discovery, configuration, and segmentation. 
 
 Consul supports using TLS to verify the authenticity of servers and clients. To enable TLS, Consul requires that all servers have certificates that are signed by a single Certificate Authority (CA). Clients should also have certificates that are authenticated with the same CA.
 

platforms/shared/charts/haproxy-ingress/README.md

@@ -4,8 +4,8 @@ The haproxy-ingress folder keeps the helm chart tgz file of haproxy-ingress proj
 
 ## Usage
 
-The values.yaml contains the default values by the helm chart, this file can be modifed to configure the haproxy-ingress deployment.
+The values.yaml contains the default values by the helm chart, this file can be modified to configure the haproxy-ingress deployment.
 
 ## Customizing the chart
 
-If the required customization is specific to Bevel usage of haproxy-ingress then create an issue on Bevel github board. 
+If the required customization is specific to Bevel usage of haproxy-ingress then create an issue on Bevel github board.