diff --git a/topics/realms/keys.adoc b/topics/realms/keys.adoc
index 460c46f568..a8c88ea0f7 100644
--- a/topics/realms/keys.adoc
+++ b/topics/realms/keys.adoc
@@ -2,7 +2,7 @@
 === Realm Key Pairs
 
 The authentication protocols that are used by {{book.project.name}} require cryptographic signatures and sometimes even
-encryption.  {{book.project.name}} uses a asymetric keypair, a private and public key to accomplish this.  When a realm
+encryption.  {{book.project.name}} uses a asymmetric key pair, a private and public key to accomplish this.  When a realm
 is created a key pair is automatically generated.  It is recommended that you cycle this key pair occasionally.  How often
 you do this is dependent on your organizational needs and security requirements as you have to make sure every application
 that needs the public or certificate of your realm get this updated.  This can be a lot of work!
diff --git a/topics/realms/ssl.adoc b/topics/realms/ssl.adoc
index c3fcf97249..6e1c00eb0e 100644
--- a/topics/realms/ssl.adoc
+++ b/topics/realms/ssl.adoc
@@ -18,7 +18,7 @@ The `Require SSL` option allows you to pick the SSL Mode you want.  Here is an e
 
 external requests::
   Users can interact with {{book.project.name}} so long as they stick to private IP addresses like `localhost`, `127.0.0.1`, `10.0.x.x`, `192.168.x.x`, and `172..16.x.x`.
-  If you try to access {{book.project.name}} from a non-private IP adress you will get an error.
+  If you try to access {{book.project.name}} from a non-private IP address you will get an error.
 
 none::
   {{book.project.name}} does not require SSL.  This should really only be used in development when you are playing around with things and don't want to bother