diff --git a/topics/cache/replication.adoc b/topics/cache/replication.adoc
index 0cd44723bd..f7b6926699 100755
--- a/topics/cache/replication.adoc
+++ b/topics/cache/replication.adoc
@@ -18,7 +18,7 @@ You can change the number of nodes that replicate a piece of data by change the
 ...
 ----
 
-Here's we've changed it so at least two nodes will replicate one specific user login session.
+Here we've changed it so at least two nodes will replicate one specific user login session.
 
 TIP:  The number of owners recommended is really dependent on your deployment.  If you do not care if users are logged
       out when a node goes down, then one owner is good enough and you will avoid replication.
diff --git a/topics/database/datasource.adoc b/topics/database/datasource.adoc
index e7918c659d..46382ba696 100755
--- a/topics/database/datasource.adoc
+++ b/topics/database/datasource.adoc
@@ -4,7 +4,7 @@
 After declaring your JDBC driver, you  have to modify the existing datasource configuration that {{book.project.name}} uses
 to connect it to your new external database.  You'll do
 this within the same configuration file and XML block that you registered your JDBC driver in.  Here's an example
-that set's up the connection to your new database:
+that sets up the connection to your new database:
 
 .Declare Your JDBC Drivers
 [source,xml]