diff --git a/docs/src/docs/asciidoc/guides/rest.adoc b/docs/src/docs/asciidoc/guides/rest.adoc
index 4daa4999..d69cd5e2 100644
--- a/docs/src/docs/asciidoc/guides/rest.adoc
+++ b/docs/src/docs/asciidoc/guides/rest.adoc
@@ -80,7 +80,7 @@ include::{samples-dir}rest/src/main/java/sample/HttpSessionConfig.java[]
 
 <1> We import an embedded Redis Server so that there is no need to start up Redis external of our application.
 In a production application this is not necessary since we would point our connection to an external Redis instance.
-<2> The `@EnableRedisHttpSession` annotation creates a Spring Bean with the name of `springSessionRepositoryFilter` that implements Filter.
+<2> The `@EnableRedisHttpSession` annotation creates a Spring Bean with the name of `springSessionRepositoryFilter` that implements `Filter`.
 The filter is what is in charge of replacing the `HttpSession` implementation to be backed by Spring Session.
 In this instance Spring Session is backed by Redis.
 <3> We create a `RedisConnectionFactory` that connects Spring Session to the Redis Server.
@@ -205,4 +205,4 @@ Alternatively, you can also delete the explicit key. Enter the following into yo
 
 We can now use the *x-auth-token* to make another request with the session we deleted and observe we are prompted for a authentication. For example, the following returns an HTTP 401:
 
-    $ curl -v http://localhost:8080/ -H "x-auth-token: 0dc1f6e1-c7f1-41ac-8ce2-32b6b3e57aa3"
\ No newline at end of file
+    $ curl -v http://localhost:8080/ -H "x-auth-token: 0dc1f6e1-c7f1-41ac-8ce2-32b6b3e57aa3"
diff --git a/docs/src/docs/asciidoc/guides/users.adoc b/docs/src/docs/asciidoc/guides/users.adoc
index bdfc482f..bfed16a6 100644
--- a/docs/src/docs/asciidoc/guides/users.adoc
+++ b/docs/src/docs/asciidoc/guides/users.adoc
@@ -103,11 +103,11 @@ include::{samples-dir}users/src/main/java/sample/UserAccountsFilter.java[tags=ad
 ----
 
 <1> We have an existing variable named `unauthenticatedAlias`.
-The value is an alias that points to existing unauthenticated session.
+The value is an alias that points to an existing unauthenticated session.
 If no such session exists, the value is null.
 This ensures if we have an existing unauthenticated session that we use it instead of creating a new session.
 <2> If all of our sessions are already associated to a user, we create a new session alias.
-<3> If a there exists a session that is not associated to a user, we use its session alias.
+<3> If there is an existing session that is not associated to a user, we use its session alias.
 <4> Finally, we create the add account URL.
 The URL contains a session alias that either points to an existing unauthenticated session or is an alias that is unused thus signaling to create a new session associated to that alias.
 
@@ -150,4 +150,4 @@ will output a link of:
 <a id="navLink" href="/link.jsp?_s=1">Link</a>
 ----
 
-end::how-does-it-work[]
\ No newline at end of file
+end::how-does-it-work[]
diff --git a/docs/src/docs/asciidoc/index.adoc b/docs/src/docs/asciidoc/index.adoc
index d068bf4a..ddcb4314 100644
--- a/docs/src/docs/asciidoc/index.adoc
+++ b/docs/src/docs/asciidoc/index.adoc
@@ -87,7 +87,7 @@ We have already mentioned that Spring Session provides transparent integration w
 Using Spring Session with `HttpSession` is enabled by adding a Servlet Filter before anything that uses the `HttpSession`.
 
 NOTE: The <<samples, HttpSession Sample>> provides a working sample on how to integrate Spring Session and `HttpSession`.
-You can the basic steps for integration below, but you are encouraged to follow along with the detailed HttpSession Guide when integrating with your own application.
+You can read the basic steps for integration below, but you are encouraged to follow along with the detailed HttpSession Guide when integrating with your own application.
 
 include::guides/httpsession.adoc[tags=config,leveloffset=+2]
 
@@ -161,7 +161,7 @@ include::guides/users.adoc[tags=how-does-it-work,leveloffset=+1]
 [[httpsession-rest]]
 === HttpSession & RESTful APIs
 
-Spring Session has can work with RESTful APIs by allowing the session to be provided in a header.
+Spring Session can work with RESTful APIs by allowing the session to be provided in a header.
 
 
 NOTE: The <<samples, REST Sample>> provides a working sample on how to use Spring Session in a REST application to support authenticating with a header.