Typo/grameer changes as per review comments.

docs/content/preview/integrations/hashicorp-vault.md

@@ -162,13 +162,13 @@ vault lease revoke <lease-ID>
 
 ## Configure SSL/TLS
 
-To allow YSQL hashicorp vault plugin to communicate securely over SSL with YugabyteDB database, you need the root certificate (`ca.crt`) of the YugabyteDB cluster. To generate these certificates and install them while launching the cluster, follow the instructions in [Create server certificates](../../secure/tls-encryption/server-certificates/).
+To allow YSQL Hashicorp Vault plugin to communicate securely over SSL with YugabyteDB database, you need the root certificate (`ca.crt`) of the YugabyteDB cluster. To generate these certificates and install them while launching the cluster, follow the instructions in [Create server certificates](../../secure/tls-encryption/server-certificates/).
 
-Because a YugabyteDB Aeon cluster is always configured with SSL/TLS, you don't have to generate any certificate but only set the client-side SSL configuration. To fetch your root certificate, refer to [CA certificate](../../yugabyte-cloud/cloud-secure-clusters/cloud-authentication/#download-your-cluster-certificate)
+Because a YugabyteDB Aeon cluster is always configured with SSL/TLS, you don't have to generate any certificate but only set the client-side SSL configuration. To fetch your root certificate, refer to [CA certificate](../../yugabyte-cloud/cloud-secure-clusters/cloud-authentication/#download-your-cluster-certificate).
 
-To start a secure local YugabyteDB cluster using `yugabyted` refer to [Multi-node cluster](../../reference/configuration/yugabyted/#create-a-local-multi-node-cluster) 
+To start a secure local YugabyteDB cluster using `yugabyted`, refer to [Create a local multi-node cluster](../../reference/configuration/yugabyted/#create-a-local-multi-node-cluster).
 
-For a YugabyteDB Aeon cluster, or a YugabyteDB cluster with SSL/TLS enabled, set the SSL-related connection parameters along with other connection information while adding the database by either of the following 2 ways:
+For a YugabyteDB Aeon cluster, or a local YugabyteDB cluster with SSL/TLS enabled, set the SSL-related connection parameters along with other connection information while adding the database by either of the following ways:
 
 - Provide the connection information in DSN format:
 
@@ -203,7 +203,7 @@ The following table summarizes the SSL modes:
 
 | SSL Mode | Client Driver Behavior | YugabyteDB Support |
 | :------- | :--------------------- | ------------------ |
-| disable  | SSL Disabled | Supported
+| disable  | SSL disabled | Supported
 | allow    | SSL enabled only if server requires SSL connection | Supported
 | prefer (default) | SSL enabled only if server requires SSL connection | Supported
 | require | SSL enabled for data encryption and Server identity is not verified | Supported
@@ -222,9 +222,9 @@ ERROR: The catalog snapshot used for this transaction has been invalidated: expe
 
 A DML query in YSQL may touch multiple servers, and each server has a Catalog Version which is used to track schema changes. When a DDL statement runs in the middle of the DML query, the Catalog Version is changed and the query has a mismatch, causing it to fail.
 
-In these cases, the database aborts the query and returns a 40001 error code. Operations failing with this code can be safely retried.
+For such cases, the database aborts the query and returns a 40001 error code. Operations failing with this code can be safely retried.
 
-For more info, refer to [How to troubleshoot Schema or Catalog version mismatch database errors](https://support.yugabyte.com/hc/en-us/articles/4406287763597-How-to-troubleshoot-Schema-or-Catalog-version-mismatch-database-errors)
+For more information, refer to [How to troubleshoot Schema or Catalog version mismatch database errors](https://support.yugabyte.com/hc/en-us/articles/4406287763597-How-to-troubleshoot-Schema-or-Catalog-version-mismatch-database-errors).
 
 ## Learn more