diff --git a/spring-grpc-docs/README.md b/spring-grpc-docs/README.md
index 0b066cd..4572080 100644
--- a/spring-grpc-docs/README.md
+++ b/spring-grpc-docs/README.md
@@ -2,7 +2,7 @@
 
 ## README
 
-The top level README and CONTRIBUTING guidleines documentation are generated from sources in this module on `mvn package` using [`asciidoctor-reducer`](https://github.com/asciidoctor/asciidoctor-reducer) and [`downdoc`](https://github.com/opendevise/downdoc).
+The top level README and CONTRIBUTING guidelines documentation are generated from sources in this module on `mvn package` using [`asciidoctor-reducer`](https://github.com/asciidoctor/asciidoctor-reducer) and [`downdoc`](https://github.com/opendevise/downdoc).
 
 ## Configuration Properties
 The Spring gRPC configuration properties are automatically documented as follows:
diff --git a/spring-grpc-docs/src/main/antora/modules/ROOT/pages/client.adoc b/spring-grpc-docs/src/main/antora/modules/ROOT/pages/client.adoc
index acc244f..a5693d9 100644
--- a/spring-grpc-docs/src/main/antora/modules/ROOT/pages/client.adoc
+++ b/spring-grpc-docs/src/main/antora/modules/ROOT/pages/client.adoc
@@ -94,7 +94,7 @@ The prefix `secure` is used as a bean definition name prefix, so the resulting b
 This feature is useful when you want to have multiple instances of the same stub class with different configurations.
 
 N.B. The `ClientRegistrationRepository` in the example is injected via an `ObjectProvider` which is not called directly to avoid early instantiation.
-The customizer has to run very early in the application lifecycle, so you always want to follow this pattern if you need to inject depdendencies to build the channel options.
+The customizer has to run very early in the application lifecycle, so you always want to follow this pattern if you need to inject dependencies to build the channel options.
 
 == Create a Client Manually
 
@@ -310,7 +310,7 @@ The rest is the configuration of the SSL bundle itself, in this case using JKS e
 === HTTP Headers
 
 Spring gRPC provides a couple of interceptor that can be used to provide security to your gRPC clients.
-There is one for Basic HHTP authentication and one for OAuth2 (bearer tokens).
+There is one for Basic HTTP authentication and one for OAuth2 (bearer tokens).
 Here's an example of creating a channel that uses Basic HTTP authentication:
 
 [source,java]
diff --git a/spring-grpc-docs/src/main/antora/modules/ROOT/pages/server.adoc b/spring-grpc-docs/src/main/antora/modules/ROOT/pages/server.adoc
index c5c764e..b550edb 100644
--- a/spring-grpc-docs/src/main/antora/modules/ROOT/pages/server.adoc
+++ b/spring-grpc-docs/src/main/antora/modules/ROOT/pages/server.adoc
@@ -8,7 +8,7 @@ The `Server` is the gRPC server that listens for incoming requests and routes th
 == Create a gRPC Service
 
 To create a gRPC server, you need to provide one or more beans of type `BindableService`.
-There are some `BindableServices` available off the shelf that you could include in your application (an example is the reflection service from the `grpc-services` artifact which allows clients to browse the metadata of your services and download the Portobuf files). 
+There are some `BindableServices` available off the shelf that you could include in your application (an example is the reflection service from the `grpc-services` artifact which allows clients to browse the metadata of your services and download the Protobuf files).
 Very commonly, you will create your own `BindableService` by extending the generated service implementation from your Protobuf file.
 The easiest way to activate it is to simply add a Spring `@Service` annotation to the implementation class and have it picked up by the `@ComponentScan` in your Spring Boot application.