Apply suggestions from code review

Co-authored-by: Mosh <[email protected]>
libp2p · Jan 17, 2025 · a0ee02b · a0ee02b
1 parent 6f925a8
commit a0ee02b
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/src/_blog/aut-tls.md b/src/_blog/aut-tls.md
@@ -84,7 +84,7 @@ The following diagram illustrates the AutoTLS DNS-01 challenge broker in action:
 
 The second part of the AutoTLS service is the authoritative DNS server for `libp2p.direct`.
 
-It's main role is to map DNS names to the libp2p node's IP addresses statelessly. For example, `1-2-3-4.<peerID>.libp2p.direct` resolves to the A record with the IP `1.2.3.4`.
+Its main role is to map DNS names to the libp2p node's IP addresses statelessly. For example, `1-2-3-4.<peerID>.libp2p.direct` resolves to the A record with the IP `1.2.3.4`.
 
 The trick here is that the **IP address is encoded in the DNS name**. Dots are substituted with dashes to ensure the TLS certificate remains valid. The benefit of this approach is that whenever a libp2p node's IP address changes, it's resolvable without coordination. This keeps the DNS server stateless and simple to operate while ensuring that even when a libp2p IP address changes, it's resolvable without coordination.
 
@@ -132,7 +132,7 @@ However, there are a number drawbacks to WebRTC:
 
 ## Origins vs. PeerIDs
 
-The Web secuity model is anchored to domain names (origins). Moreover, browsers require TLS certificates to be signed by a certificate authority (CA) so as to ensure that the entity requesting a certificate owns the domain name. The role of certificate authorities is to verify that the entity requesting a certificate owns the domain name.
+The Web security model is anchored to domain names (origins). Moreover, browsers require TLS certificates to be signed by a certificate authority (CA) so as to ensure that the entity requesting a certificate owns the domain name. The role of certificate authorities is to verify that the entity requesting a certificate owns the domain name.
 
 On the other hand, libp2p's security model is anchored to PeerIDs: unique identifiers derived from public keys generated by the libp2p node. Unlike CA-signed TLS certificates, PeerIDs can permissionlessly be generated.