diff --git a/docs/src/main/tut/core-concepts.md b/docs/src/main/tut/core-concepts.md
index af4082293..64f5295d5 100644
--- a/docs/src/main/tut/core-concepts.md
+++ b/docs/src/main/tut/core-concepts.md
@@ -191,9 +191,9 @@ We'll see more details about these and other annotations in the following sectio
 
 ## Compression
 
-[frees-rpc] allows you to compress the data whose we are sending in our services. We can enable this compression either on the server or client side.
+[frees-rpc] allows us to compress the data we are sending in our services. We can enable this compression either on the server or the client side.
 
-[frees-rpc] supports only `Gzip` as compression format so far and the usage it's really easy. 
+[frees-rpc] supports `Gzip` as compression format.
 
 On the server side, we only have to add the annotation `Gzip` in our defined services.
 
diff --git a/docs/src/main/tut/ssl-tls.md b/docs/src/main/tut/ssl-tls.md
index c224559e3..1e6063cd3 100644
--- a/docs/src/main/tut/ssl-tls.md
+++ b/docs/src/main/tut/ssl-tls.md
@@ -8,9 +8,9 @@ permalink: /docs/rpc/ssl-tls
 
 > [gRPC](https://grpc.io/docs/guides/auth.html) has SSL/TLS integration and promotes the use of SSL/TLS to authenticate the server, and encrypt all the data exchanged between the client and the server. Optional mechanisms are available for clients to provide certificates for mutual authentication.
 
-[frees-rpc] allows you to encrypt the connection between the server and the client through SSL/TLS. The main goal of use SSL is protect your sensitive information and keeps your data secure between servers and clients.
+[frees-rpc] allows you to encrypt the connection between the server and the client through SSL/TLS. The main goal of using SSL is to protect your sensitive information and keeps your data secure between servers and clients.
 
-As we mentioned in the [Quickstart](/docs/rpc/quickstart) section, we can choose and configure our client with `okhttp` or `netty` but if we want to encrypt our service, it's mandatory to use `Netty`.
+As we mentioned in the [Quickstart](/docs/rpc/quickstart) section, we can choose and configure our client with `OkHttp` or `Netty` but if we want to encrypt our service, it's mandatory to use `Netty`.
 
 [frees-rpc] only supports encryptation over *Netty*.
 
@@ -18,7 +18,7 @@ As we mentioned in the [Quickstart](/docs/rpc/quickstart) section, we can choose
 
 On the server and client side, we will need two files to configure the `SslContext` in `gRPC`:
 
-* Server certificate file: Small data files that digitally bind a cryptographic key to an organization’s details. This file could be generated or get from a third company.
+* Server certificate file: Small data files that digitally bind a cryptographic key to an organization’s details. This file could be generated or obtained from a third company.
 
 * Server private key file: The private key is a separate file that is used in the encryption of data sent between your server and the clients. All SSL certificates require a private key to work.