Typos

content/enter-the-matrix.md

@@ -26,7 +26,7 @@ As I mentioned before, Matrix is decentralised and federated. The decentralised
 **Glossary break:**
 
 * There are a few server types in the Matrix specifications. The homeservers (*HS*) are the servers that implement the client-server and federation APIs, i.e. the ones that allows actual messages to be sent from Alice to Bob. In my example, in which I was referring to homeservers as "Matrix servers", `matrix.alice.tld` and `matrix.bob.tld` are homeservers. Among the other server types are the identity servers (*IS*) that allows one to host third-party identifiers (such as an email address or a phone number) so people can reach them using one of them, and application services (*AS*) which are mainly used to bridge an existing system to Matrix (but are not limited to that). In this post, I'm only going to cover the basic use of homeservers, since knowledge about the other types isn't required to understand the bases of how Matrix works.
-* In the Matrix spec, both Alice and Bob are identified by a Matrix ID, which takes the form `@localpart:homeserver`. In our example, their Matrix IDs could respectively be `@Alice:matrix.alice.tld` and `@Bob:matrix.bob.tld`. Matrix IDs' form actually follows a broader one, taken by any Matrix entity, which is `*localpart:homeserver`, where `*` is a "sigil" character which is used to identity the identity's type. Here, the sigil character `@` states that the entity is a Matrix ID.
+* In the Matrix spec, both Alice and Bob are identified by a Matrix ID, which takes the form `@localpart:homeserver`. In our example, their Matrix IDs could respectively be `@Alice:matrix.alice.tld` and `@Bob:matrix.bob.tld`. Matrix IDs' form actually follows a broader one, taken by any Matrix entity, which is `*localpart:homeserver`, where `*` is a "sigil" character which is used to identify the entity's type. Here, the sigil character `@` states that the entity is a Matrix ID.
 
 ## Three roomies on three servers