diff --git a/draft-ymbk-sidrops-rpki-has-no-identity.xml b/draft-ymbk-sidrops-rpki-has-no-identity.xml
index 056f118..662c88a 100644
--- a/draft-ymbk-sidrops-rpki-has-no-identity.xml
+++ b/draft-ymbk-sidrops-rpki-has-no-identity.xml
@@ -104,7 +104,7 @@
 
     <t>The RPKI was designed and specified to sign certificates for use
     within the RPKI itself and to generate Route Origin Authorizations
-    (ROAs), <xref target="RFC6480"/>, for use in routing.  It's design
+    (ROAs), <xref target="RFC6480"/>, for use in routing.  Its design
     intentionally precluded use for attesting to real world identity as,
     among other issues, it would expose the Certification Authority (CA)
     to liability.</t>
@@ -148,7 +148,7 @@
     and <xref target="I-D.ietf-sidrops-rpki-rsc"/> must go to great
     lengths to extract the supposedly relevant keys from the CA.</t>
 
-    <t>For some particular INR, say Bill's Bait and Sushi's Autonompus
+    <t>For some particular INR, say Bill's Bait and Sushi's Autonomous
     System (AS) number, someone out on the net probably has the
     credentials to the CA account in which BB&amp;S's INRs are
     registered.  That could be the owner of BB&amp;S, Roberto's Taco