README.rdoc in certificate_authority-0.1.2 vs README.rdoc in certificate_authority-0.1.3

@@ -209,11 +209,11 @@
 	key_material_in_hardware.pin = "11111111"
 	
 	root.key_material = key_material_in_hardware
 	root.sign!
 	
-You're current version of OpenSSL _must_ include dynamic engine support and you will need to have OpenSSL PKCS#11 engine support.  You will also require the actual PKCS#11 driver from the hardware manufacturer.  As of today the only tokens I've gotten to work are:
+Your current version of OpenSSL _must_ include dynamic engine support and you will need to have OpenSSL PKCS#11 engine support.  You will also require the actual PKCS#11 driver from the hardware manufacturer.  As of today the only tokens I've gotten to work are:
 
 [eTokenPro] Released by Aladdin (now SafeNet Inc.). I have only had success with the version 4 and 5 (32 bit only) copy of the driver. The newer authentication client released by SafeNet appears to be completely broken for interacting with the tokens outside of SafeNet's own tools. If anyone has a different experience I'd like to hear from you.
 
 [ACS CryptoMate] Also a 32-bit only driver. You'll have to jump through some hoops to get the Linux PKCS#11 driver but it works surprisingly well. It also appears to support symmetric key operations in hardware.
 
@@ -232,6 +232,6 @@
 
 Released under the MIT License: http://www.opensource.org/licenses/mit-license.php
 
 Main page: http://github.com/cchandler/certificateauthority
 
-Issue tracking: https://github.com/cchandler/certificateauthority/issues
\ No newline at end of file
+Issue tracking: https://github.com/cchandler/certificateauthority/issues